Saturday, October 19, 2013

Setting Sharepoint 2013 in Visual Studio 2012

Dear Readers,

I have started to learn sharepoint 2013 and while doing so, first hurdle was that Visual Studio 2012 was not displaying me sharepoint 2013 controls. So, I have to setup that manually and for that I follow below steps.

clip_image002
In order to get the templates into VS, you need to install Microsoft Office Developer Tools for Visual Studio 2012 which can be found here: http://www.microsoft.com/visualstudio/eng/office-dev-tools-for-visual-studio (direct install : http://aka.ms/OfficeDevToolsForVS2012).
Unfortunately, this leverages the Microsoft Web Platform Installer which does not play well in closed environments. The Microsoft Web Platform Installer will install the following items:
Microsoft Identity Extensions
Workflow Manager Client 1.0
Microsoft Exchange Web Services 2.0
Microsoft Windows Identity Foundation SDK 4.0
Microsoft SharePoint Client Components
Microsoft Workflow Manger Tools
Cumulative Update 1.0 for Microsoft Workflow Manager Tools

Open XML SDK 2.5
Microsoft Visual Studio Tools for Office Runtime
Microsoft Office Developer Tools for Visual Studio 2012 - RTM

Once these items have been downloaded and installed on your development machine and double-click to install them, you will see that there is the option to create Apps and other items for Office and SharePoint 2013.
clip_image004
Unfortunately, if you try to create a project for any of these new fun items, you will get the following error:
An error occurred whilst trying to load some required components, Please ensure the following prerequisite components are installed.
Microsoft Web Developer Tools
Microsoft Exchange Web Services"
The problem is that the Microsoft Web Platform Installer adds parameters when installing the Microsoft Exchange Web Services that must be used in order to get around the error. If you have already installed the Microsoft Exchange Web Services, uninstall it from Control Panel and then open up a command prompt. Navigate to the location of EwsManagedApi32.msi. In the command prompt, run
EwsManagedApi32.msi addlocal="ExchangeWebServicesApi_Feature,ExchangeWebServicesApi_Gac"
clip_image006
Once that has finished installing, open up Visual Studio 2012 and enjoy creating apps for Microsoft SharePoint Server 2013.
Kindly provide your valuable comments in case if the above solution works for you too.
Please note that the content was copied from below URL 

Monday, September 23, 2013

The sign-in method you're trying to use isn't allowed. For more info, contact your network administrator

Above problem occur when you have not added a group (of which User try to login)  in your local policy login. To resolve the issue, follow the steps,

Log in as the administrator on the server, then start the Group Policy Management Editor by running the  gpmc.msc command from PowerShell or the Command Line window.
1. In the Group Policy Management window on the left hand side, select Group Policy Management.
Pic1
2. Click to expand the  Forest tree node.
3. Click Domains.
4. Select your domain name.
5. Click Group Policy Objects.
Pic2
6. In the right-hand window, double-click Default Domain Controllers Policy.
7. Right-click Default Domain Controllers Policy and Select Edit.
8. In the Group Policy Management Editor window, click Default Domain Controllers Policy.
9. Click Computer Configuration, and then click Policies.
10. Click Windows Settings, and then click Security Settings.
Pic3
11. Click Local Policies and then click User Rights Assignments.
12. In the right pane, click Allow log on locally.
Pic4
12. Click the Add User or Group button.
13. In the Add User or Group dialog,  enter the name to be added or click Browse.. to search for a name.
Pic5
14. Click OK .
15. Repeat steps 12-14 if you want to add more users.
16. Click OK to Close the Allow log on locally Properties dialog, and then click Close several times to Close the remaining open Windows.
17. Run the following command in the Command Window to activate the policy changes:
gpupdate /force.
Kindly note that above content is originally copied from http://www.sharepointviking.com/the-signin-method-youre-trying-to-use-isnt-allowed-windows-server-2012/

In case if above solution resolve your problem then please comment on it to increase its credibility.

Tuesday, July 23, 2013

The type 'System.Data.Entity.DbContext' is defined in an assembly that is not referenced. You must add a reference to assembly 'EntityFramework, Version=4.4.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

Dear Readers,

I face subjected problem while trying to learn ADO.Net Entity Framework in visual studio. After a bit of searching, I come to know that I have not included EntityFramework.dll reference in my project. Just add the DLL reference and I hope that your will out of this problem.

Please note that in case if you don't find EntityFramework.dll in references then you can locate it in the project bin (Debug\Release) folder where you add ADO.Net Entity Data Model.

I hope that this will work for you as it worked for me. So please leave a comment if this post help you so other visitors can also trust on this solution.

Thanks.



Sunday, January 27, 2013

Saving changes is not permitted. The changes you have made require the following tables to be dropped and re-created. You have either made changes to a table that can't be re-created or enabled the option Prevent saving changes that require the table to be re-created

 You receive this message in SQL Server 2008 when you alter a table and after modification in table, you want to save this modification.

To allow saving the modification they suggested that first drop the table and then recreate it which is not suitable when you have important data/information, and it also causes increase in rework.

To save yourself from this rework, we have another way which is mentioned below.

Step 1:- Open your SQL Server Management Studio.

Step 2:- Goto Tools -> Options -> Designers.

Step 3:- Uncheck checkbox "Prevent saving changes that require table re-creation".

Step 4:- Save your changes.

Now, attempt to save your modification changes which you have done in your table.

I hope that this will work for you as it worked for me. So please leave a comment if this post help you so other visitors can also trust on this solution.

Thanks.