I have visual studio 2012 and SQL Server 2014 installed in my machine. As a part of my work I require to open and RDL (SSRS) file in design view. When I checked in the google I saw that I need to have SQL Server Report Services in my visual studio and open Report Server Project. But I am not able to create Report Server Project and I doubt that I don't have SQL Server Report Services in my visual studio.
I downloaded and installed Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012 from the location here (if you VS is 2012). Then I created an new report server project Report Server Project and I did "add Existing Item" as my RDL report which need to be opened and go for design view. Then it will open the report in design mode.
I have SharePoint Foundation 2013 installed in the windows server 2012.
Is it possible to develop SharePoint solution/web parts/Apps using Visual Studio 2012 in my local machine(Windows 7 64Bit) without having SharePoint installed in local machine?
if i need to develop SharePoint solution/web parts/Apps in visual studio 2012, do i need to install visual studio in the Server that contain share point Foundation 2013?
Cant i develop in local machine and deploy it to server?
Can someone help me on this issue?
Thanks.
Try this;
• How to Perform SharePoint Development On A Client Workstation
15 Feb 2011 by Bryant Sombke in Guides, Web, Windows 16 Comments
One of the most difficult restrictions for a SharePoint developer to deal with can be the requirement to do development on a SharePoint server. Personally, I prefer doing my development on my local machine, eliminating the need to establish a remote desktop connection to a different machine in order to write code.
Unfortunately, SharePoint development requires many DLL files which are included with an installation of SharePoint on a server. To make matters worse, SharePoint 2010 requires an x64 server, further complicating the issue. Fortunately, there is an easy workaround that can allow a SharePoint developer to be productive, even while using their laptop on the road without an available internet connection.
Copy the SharePoint DLLs
As I mentioned before, SharePoint development requires DLL files that are included with a SharePoint 2007 or 2010 installation. The first step is to grab these off of a SharePoint server. For SharePoint 2007, they are located in the hive at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI\, and for 2010 at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAP\. Copy the DLL files in this directory from the server, and paste them at the exact same file path on your local machine. Since your PC likely does not have SharePoint installed, you may have to create the directory structure yourself.
SharePoint 2007 DLL Directory
Register the Assemblies to the GAC
Now that you have the DLL files on your workstation, you will be able to include them as references in your Visual Studio projects just as you would with any other DLLs. However, if you want them to auto-register with your project when you use a Visual Studio 2010 SharePoint template or a WSPBuilder template, you must register the DLL files in your local Global Assembly Cache. To do this, open the directory on your workstation that contains the SharePoint DLLs and drag them into the C:\Windows\assembly\ directory. This will register them with the GAC on your workstation, and Visual Studio should successfully find the assemblies when a template is loaded up. Although these assemblies may be 64-bit, this will work fine even though your workstation may be 32-bit.
Global Assembly Cache
If you’ve successfully completed the two steps above, you should be able to write your code and successfully compile your project. Once you generate your WSP file, you can then deploy it like any other WSP.
Please Use Caution
If you do development for both 2007 and 2010, you can do this for both on the same workstation; just be sure to complete both steps for each version. Since the 2007 and 2010 assemblies have different Assembly Versions (12.0.0.0 and 14.0.0.0), you don’t have to worry about conflicts in the GAC. Be sure to use caution, however, because in my experience, Visual Studio tends to grab the SharePoint 2010 version of the DLL even for a SharePoint 2007 project if they’re both registered on your workstation. If this happens, remove the incorrect reference, and add a reference to the correct 2007 DLL from your 12\ISAPI directory.
From http://www.techerator.com/2011/02/how-to-perform-sharepoint-development-on-a-client-workstation/
You can develop SharePoint Apps from anywhere -- this is even more convenient when you're using the SharePoint 2013 development site template to do your testing on.
For farm/sandbox solutions things get more complicated...
If you want to develop webparts or other farm/sandbox solutions you need to have visual studio and sharepoint installed on the same machine (visual studio depends on the sharepoint dlls to build and debug properly). You also need to run Visual Studio as an admin for this scenario (so you'll need to be a local administrator for the machine in question).
It's possible to run SharePoint 2010 on Windows7, but this is not supported by SharePoint 2013 -- you'll have to run Windows Server for the development machine.
You can move your files from a development environment to your production SharePoint farm by building a WSP file for your farm solution on the development machine then sending it to your farm admin who can then deploy it to the production sharepoint environment... For a sandbox solution the site collection admin can add the solution file (WSP) to the site collection 'solution gallery' then active it (for more info on sandbox solution installation see the msdn documentation here: http://msdn.microsoft.com/en-us/library/office/gg615450(v=office.14).aspx)
Hope that summary helps, for more info on setting up development environments see: http://msdn.microsoft.com/en-us/library/office/ee554869(v=office.15).aspx
Yes, you can definately develop SharePoint solutions from your local machine where you dont have SharePoint installed.
For doing this you need to follow some steps -
Go to the server where SharePoint 2013 is installed and follow steps from 1 to 3
Go to Run and type "regedit"
Navigate towards HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office
Right click on 15.0 and click Export. Save the exported file
Now go to your machine where sharepoint is not installed and follow below steps:
Now open Registry on your machine
Import the 15 directory which was exported from SharePoint server
Open Powershell
Run this command
Set-ItemProperty -Path "HKLM:\Software\Microsoft\Shared Tools\web server extensions\15.0\" -Name "Location" -Value "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\"
Now open visual studio 2013 and you will be able to create SharePoint 2013 project without error.
I have created a dtsx file to use as an SSIS package template. I want to be able to use the file as a template by clicking on an open Project in Solution Explorer and selecting Add -> New Item
My questions are:
How do I save this as a template file? Its currently a .dtsx file.
Where do I have to place the file so its in my list of options in the Add New Items dialog? I have seen many conflicting paths and none specifically for SQL Server Data Tools for Visual Studio 2012.
I have searched for instructions on how to do this but have now found clear instructions for use with SQL Server Data Tools for Visual Studio 2012. Posts I have found are conflicting and don't clearly explain how convert the dtsx file into a template file. The link here is an example of conflicting info; its posted for vs 2010 and examples are for vs 2005. I have also tried to use the Export Template Wizard but this feature seems to have gone away in SSDT for VS2012.
You need to copy the dtsx package to following location and restart the SSDT for VS2012. Note that the VS installation location may be different in your machine.
First select the package that you want to export as a template and then Select File->Save As..
and save it to
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject\DataTransformationItems
E.g.
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject\DataTransformationItems\MyTemplatePackage.dtsx
Quote: I have also tried to use the Export Template Wizard but this feature seems to have gone away in SSDT for VS2012
SSDT for VS2012 does not have an export template wizard. It's only avaible for VS2012.
When I try to view a .sql file from Source Control Explorer in Visual Studio 2012 (TFS 2012) I get the following error message:
TF10187: Could not open document
FilePath\FileName
User canceled out of save dialog
It's only happening for SQL files. The file does exist in the TFSTemp folder and I can double click and open it from there. What do I need to change to fix this error message?
Install SQL Server Data Tools - September 2013 update things will be fine. http://msdn.microsoft.com/en-us/jj650015
For us, this seems to be linked to a .NET Framework 4.6 upgrade and is not limited to SQL files. Users have issues opening files from Source Control Explorer and Solution Explorer.
Delete the contents from the following folders:
C:\Users\<>\AppData\Local\Microsoft\Team Foundation
C:\Users\<>\AppData\Local\Microsoft\VisualStudio
C:\Users\<>\AppData\Local\Microsoft\VSCommon
The first step fixed it in my case, but you can try this if it doesn't: Navigate to the Visual Studio IDE folder in command prompt or windows explorer and Run the following command "devenv /resetuserdata". Ie: C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE. To minimize the potential loss of the user’s personal environment, you should consider creating a backup using the Export Settings wizard, and the Import Settings wizard to restore the settings if and when needed.
Note: The side effects of running the /resetuserdata option is that any customizations will have to be reconfigured (ie: TFS server and proxy settings) as well as many, if not all, Visual Studio extensions have to be re-installed.
Source: http://blogs.msdn.com/b/willy-peter_schaub/archive/2010/09/15/if-you-have-problems-with-tfs-or-visual-studio-flush-the-user-cache-or-not.aspx
Looks like you need to uninstall Redgate and then re-install the data tools. This is probably because an add-in was trying to grab the .SQL files and do something with them that VS wasn't expecting.
I installed Visual Studio 2012 and at a later date Update 2. After installing Update 2, when I load any project, I get the following error:
---------------------------
Microsoft Visual Studio
---------------------------
The 'ProviderPackage' package did not load correctly.
The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file 'C:\Users\username\AppData\Roaming\Microsoft\VisualStudio\11.0\ActivityLog.xml'.
Continue to show this error message?
---------------------------
Yes No
---------------------------
After locating the ActivityLog.xml, I see the following set of errors:
<entry>
<record>300</record>
<time>2013/04/23 18:32:54.002</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Begin package load [ProviderPackage]</description>
<guid>{5F2E5E42-4192-4D79-A0D8-1D881E808829}</guid>
</entry>
<entry>
<record>301</record>
<time>2013/04/23 18:32:54.012</time>
<type>Error</type>
<source>VisualStudio</source>
<description>SetSite failed for package [ProviderPackage]</description>
<guid>{5F2E5E42-4192-4D79-A0D8-1D881E808829}</guid>
<hr>80131522</hr>
<errorinfo>Method 'GetHostedIntellisenseTypes' in type 'Microsoft.VisualStudio.Progression.DTEWrapperCached' from assembly 'Microsoft.VisualStudio.GraphProviderPackage, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' does not have an implementation.</errorinfo>
</entry>
<entry>
<record>302</record>
<time>2013/04/23 18:32:54.012</time>
<type>Error</type>
<source>VisualStudio</source>
<description>End package load [ProviderPackage]</description>
<guid>{5F2E5E42-4192-4D79-A0D8-1D881E808829}</guid>
<hr>80131522</hr>
<errorinfo>Method 'GetHostedIntellisenseTypes' in type 'Microsoft.VisualStudio.Progression.DTEWrapperCached' from assembly 'Microsoft.VisualStudio.GraphProviderPackage, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' does not have an implementation.</errorinfo>
Google searches do not reveal an exact match on my issue. I've tried searching the packages on the install ISO and cannot locate a package that needs to be repaired...
F:\packages>dir /s *provider*
Volume in drive F is VS2012_ULT_MSDN_ENU
Volume Serial Number is 4A21-C8BD
Directory of F:\packages\SSDT
07/26/2012 11:30 AM 780,288 DbSqlPackageProvider.msi
1 File(s) 780,288 bytes
Total Files Listed:
1 File(s) 780,288 bytes
0 Dir(s) 0 bytes free
Any other ideas?
Close Visual Studio.
Open a Developer Command Prompt for Visual Studio 2012 (as administrator).
Type devenv /setup.
Restart Visual Studio.
Possible duplicate of Visual Studio 2012 error: Package 'Visual C++ package' failed to load
See Visual C++ package: failed to load?????
This is Aaron's (Aaron Reed) answer from above, just copied as an answer instead of part of the question:
Fixed it... Fixed it... Fixed it...
Opened Programs and Features (run: appwiz.cpl)
Sorted list of installed apps by: Install Date
Filtered list by adding "SQL" to the upper right search filter
List item
I installed VS2012 on 4/1/13, so I went through each listed SQL item in the list, and right click --> Repair
From there I ran VS2012 and opened the target Solution file without issue.
My list:
Microsoft SQL Server 2012 Data-Tier App Framework
Microsoft SQL Server Data Tools - enu (11.1.20627.00)
Microsoft SQL Server 2012 Management Objects (x64)
Microsoft System CLR Types for SQL Server 2012 (x64)
Microsoft System CLR Types for SQL Server 2012
Microsoft SQL Server 2012 Management Objects
Microsoft SQL Server 2012 Transact-SQL Compiler Service
Microsoft SQL Server 2012 Command Line Utilities
Microsoft SQL Server Data Tools Build Utilities - enu (11.1.206...
Microsoft SQL Server Compact 4.0 SP1 x64 ENU
Microsoft SQL Server 2012 T-SQL Language Service
Microsoft SQL Server 2012 Native Client
Microsoft SQL Server 2012 Data-Tier App Framework
Microsoft SQL Server 2012 Express LocalDB
Microsoft SQL Server 2012 Transact-SQL SpriptDom
This worked for me -
In order to fix the issue one needs to clear the Visual Studio cache under:
%LOCALAPPDATA%\Microsoft\VisualStudio\11.0\ComponentModelCache
Thanks go to blog post SetSite failed for package [Microsoft.VisualStudio.Editor.Implementation.EditorPackage].
Usually this can be fixed by clearing the Visual Studio cache under:
Visual Studio 2012: %LOCALAPPDATA%\Microsoft\VisualStudio\11.0\ComponentModelCache
Visual Studio 2013: %LOCALAPPDATA%\Microsoft\VisualStudio\12.0\ComponentModelCache
I fixed this by uninstalling or removing:
Microsoft SQL Server Data Tools - enu (14.0.50325.0)
I hope this helps :)
Worked for me.
Window7 SP1 + VS 2013
Open a Developer Command Propmpt for VS 2012 (as administrator).
Run devenv /setup.
An even quicker fix is to simply repair the Microsoft SQL Server in the list. That fixed my problem.
Uninstalling/Repairing SQL Server Data tools is the only thing which worked for me, thanks to wayne.blackmon comment.
Picture below
For me the ActivityLog.xml stated
<errorinfo>Access to the path 'C:\Users\Klas\Documents\Visual Studio
2015\ArchitectureExplorer' is denied.</errorinfo>
When I examined this folder I realized that the entire folder structure here
C:\Users\Klas\Documents\Visual Studio 2015
had permission set so that my user had no write permissions. I added Full Control rights to my user for this folder and everything below.
After that, the message went away. Also, when I started Visual Studio it created lots of subfolders to this folder.
I had the same issue in Visual Studio 2013 for Windows 8.1.
The previous answers didn't work for me. I had to repair Visual Studio and then reboot my machine.
I was getting this error on Visual Studio start up:
the 'visual studio component model host package' did not load correctly...
After that bunch of other The '' package did not load correctly... error messages.
I realized I don't have enough free space on my C drive, where the Visual Studio were installed.
I opened up some space and restarted the Visual Studio, solved the problem.
Not sure if it has anything to do with the free space on disk though.
In my case the problem appeared after I installed Visual Studio 2015. From that point nor 2015, nor previous versions of Visual Studio would load.
The problem was the PATH environment variable exceeding the MAX length.
I shortened it to less than 2048 and restarted the machine. Visual Studio started loading, but with some errors still. Lastly run the devenv /setup, and all is back to normal.
I just had a similar error (on Windows 7. I installed Visual Studio 2015 Professional and then after that, several "...package did not load correctly" messages started showing up when I ran Visual Studio 2012).
What fixed my issue was to repair "Microsoft Studio Tools for Applications 2012".
Run "appwiz.cpl" (Control Panel → Programs → Uninstall a program
Right-click on "Microsoft Studio Tools for Applications 2012. Select "Change", then click "Repair".
After this, I can open up Visual Studio 2012 without those error messages.
I had a similar error. After I updated to VS2012.U2, the problem went away. TFS 2012 update 2 can't be removed without removing TFS. While I had an issue with upgrading from TFS2012.U1 to U2, I have found TFS2012.U2 to be worthwhile.
It was the problem with access rights to my %USERPROFILE% directory (because of the failure with the PC). Setting permissions to full access fixed it.
Another suggestion,
Run as admin, and restart the VS application.
Apply package update.
Reboot.
Hope this helps!
From MSDN forums:
Please open Windows Explorer, and navigate to <Visual Studio Installation Path>\Common7\IDE
Devenv.exe /SafeMode: Launches the IDE in safe mode loading minimal windows.
Devenv.exe /ResetSettings: Restores the IDE's default settings, optionally resets to the specified VSSettings file.
Devenv.exe /ResetAddin: Removes commands and command UI associated with the specified Add-in.
Devenv.exe /ResetSkipPkgs: Clears all SkipLoading tags added to VSPackages.
If still no help, I suggest you try repairing your Visual Studio installation or uninstall it and then reinstall it. If you want to reinstall it, I am afraid that you need a DVD or a fine Internet.
Doing the first three steps works for me.
I got "lucky" and restarted Visual Studio 2013 and it worked. I have had other errors in which deleting the temp cache items cleared it up.
Side note. While Visual Studio 2015 is not perfect as of yet, and NuGet has become less friendly to use IMO, if my computer is restarted by the company domain network administrators OR especially when there is a computer losing power with a brown-out of some loss of power Visual Studio 2013 becomes a bit a "fun" to fix while Visual Studio 2015 projects for months seem to just open just fine as if nothing happened when I login.
In my case, I solve this problem by removing the Read-only attribute of the folder "Visual Studio 2015" in <C:\Users\myuser\Documents>.