I have the following installed on my machine:
SQL Server 2012 developer edition
VS Express 2013 for Web
VS Express 2013 For Desktop
TFS Express 2013
I can check in/out my projects through both VS Express 2013 installs, I am wanting to make my Stored Procs encrypted so need to keep unencrypted copies within a solution in TFS so have this setup but whenever I try to check in via SSMS I get the error:
Could not load file or assembly
"Microsoft.TeamFoundation.VersionControl.ControlAdapter"
Version=12.0.0.0
Has anyone experienced this before or have a solution how to resolve it as the file does exist on my machine.
Have you installed the latest MSSCCI Provider found on visual studio gallery? And have you checked the SSMS options under source control provider, that it is set to Team Foundation Server. Remember that MSSCCI Provider requires Team Explorer 2013 to be installed as well.
Related
I have some SQL CLR projects I created with VS 2012. I want to open them with VS 2013, so I installed SSDT 16.5 for VS 2013.
Now, I am getting this error opening the SQL CLR projects:
Could not load file or assembly 'Microsoft.SqlServer.Management.SqlParser, Version=13.0.0.0
Thanks for any ideas
I also faced this issue, Installing SQL Server 2017 broke SSDT. I have fixed the issue, Here is how I was able to fix it
Steps
Uninstall Microsoft SQL Server 2017 TSQL Language Service.
Install TSqlLanguageService.msi from SQL Server 2016. Part of Microsoft® SQL
Server® 2016 Feature Pack - https://www.microsoft.com/en-us/download/details.aspx?id=52676 (Version:13.0.1601.5 File: ENU\x64\TSqlLanguageService.msi)
then restart visual studio and reload the project
Installing a newer version of SQL Server Management Studio can break SQL Server Data Tools. You need to downgrade the TSQL Language service to 2016 (13.0.0.0) level.
Originally from here:
https://www.sqlservercentral.com/Forums/1921984/Microsoft-Visual-Studio-Could-not-load-file-or-assembly-MicrosoftSqlServerManagementSqlParser-Versio
Installing SQL Server 2017 broke SSDT. I have fixed the issue, but
just wanted to post this because I couldn't find the solution at
first. Steps
Uninstall Microsoft SQL Server 2017 TSQL Language Service.
Install TSqlLanguageService.msi from SQL Server 2016.
Part of Microsoft® SQL Server® 2016 Feature Pack - https://www.microsoft.com/en-us/download/details.aspx?id=52676
Version:13.0.1601.5
File: ENU\x64\TSqlLanguageService.msi
I hope this helps someone.
https://connect.microsoft.com/SQLServer/feedback/details/3106613/net-exception-could-not-load-file-or-assembly-microsoft-sqlserver-sqlclrprovider-13-100-0-0-after-installing-sql-server-2016
Client applications should not be using the assemblies from the Program Files folders unless they are from the specific SDK folders (such as "C:\Program Files (x86)\Microsoft SQL Server\130\SDK")
The 13.100.* version of assemblies you are seeing are currently only for use by Microsoft tools and so are not placed with all needed dependencies being in the same place. The DTS folder especially has only a subset of SMO assemblies since that code does not need things such as SqlClrProvider.
Please use either the assemblies from the SDK folders or from SharedManagementObjects.msi to use as references for your applications.
Continuous Build Database Project fails when building on TFS server. We have Visual Studio 2013 Shell (Integrated) installed. There does not appear to be a way to install SQL Server Data Tools 2013 thru' Tools > Extensions and Updates... menu.
The redacted error is below...
C:\TFSBuild\XXX\XXX\Database_CI\Sources\Database\XXX\XXX.sqlproj (126): The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
Has anyone experienced this? Is there a solution or work-around? Is SSDT available for VS 2013 Shell for SQL Server 2014?
I have recently installed the Visual Studio Shell (Isolated) and (Integrated) on our build server and it does not include the SQL Server tooling components. I found out that SQL Server tooling is built in to the following versions of Visual Studio (see here):
Express for Web,
Express for Windows Desktop,
Professional,
Premium, and
Ultimate
I would recommend installing at least the Professional version and then you should get the SQL Server Data Tools components that are required for building.
SQL Server Tooling is now built into the above listed versions of Visual Studio 2013 (SSDT and Visual Studio versions) and the latest March update of Visual Studio 2013 now includes SQL Server 2014 support (SQL Server Data Tools for SQL Server 2014 is available.)
To force your build to use the correct version of MSBuild set the Process - Advanced - MSBuild arguments = "/p:VisualStudioVersion=12.0" (without the quotes) as shown.
You can download SSDT for VS2012 here and that should get the database pre-reqs on your build server.
I do see mention of "Sql Server Tooling in Visual Studio 2013" on this landing page, and I think it implies these tools should be available with the shell, so if you could, check to see if you have that targets file somewhere on your build server.
Go into C:\Program Files(x86)\ and do a "dir Microsoft.Data.Tools.Schema.SqlTasks.targets /s /b" and see if something comes up.
Right now it's hard-coded to this location:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets
You might want to see if the file already exists, but in another location, like in an "v12.0" folder instead of the "v11.0" subfolder.
EDIT
Actually, what's the value on line 126 of your .sqlproj?
If it says this:
<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" />
Change it to read:
<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v$(VisualStudioVersion)\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" />
Then have everyone test it using diagnostic logging, then gather the logs and compare them to make sure that version is consistent so you can start phasing out the legacy bits.
I had the same issue and fixed it by downloading and installing the following
dacframework.msi
SQLDOM.MSI
SQLLS.MSI
SQLSysClrTypes.msi
from here:
https://www.microsoft.com/en-au/download/details.aspx?id=42295
I am getting the following error when I am trying to add SQL Server Compact 4.0 Local Database in the Visual Studio 2012 Express for Web:
The data provider required to connect to the local data file could not be found. The file will be added to the project but the typed DataSet associated with the file will not be generated.`
I tried reinstalling the CompactDB and I installed the Microsoft SQL Server Compact 4.0 SP1 x64 ENU.
Please note: I have Visual Studio 2012 Express for Desktop and everything there works fine. I can add SQL Server Compact 4.0 Local Database item.
OS: Windows 7 SP1 Home Premium x64.
Would you be so kind how to fix it?
Thank you very much for your help in advance!
Fix by repairing the VS installation
I keep getting this error whenever I try to open a local DB .sdf file in VS 2010 SP1 Ultimate
Data provider required to connect to local data file could not be found.The file will be added to project but the typed dataset associated with the file will not be generated.
I have the VS 2010 SP1 Tools for SQL Server Compact 4.0 already installed.
Basically I had VS 2010 Express installed and that worked just fine, I have since uninstalled it and installed VS 2010 SP1 Ultimate.
How can I fix this annoying error?
You must install the SQL Server Compact 4.0 Tools for VS 2010 SP1 as well, I have a direct link here: http://erikej.blogspot.dk/2011/01/sql-server-compact-40-released.html
If you are not able to connect to TFS VS2010 from VS2008. This might save you some time.
Connecting from VS2008 to TFS VS2010
Step:1 Make sure that Service Pack 1 is installed with Sql Server 2008
Step:2 Make sure that Service Pack 1 is installed with VS2008
Step:3 Make sure that Team Explorer is installed in VS 2008
Step:4 Make sure that Service pack 1 is updated for Team Explorer
Step:5 After all these Service Packs are installed on your machine, follow the below path
CmdPrompt> regedit
Hkey_Current_User>Software>Microsoft>VisualStudio>9.0>TeamFoundation> Right Click Servers>New>String Value
Give the complete URL path which look like ‘http://swstfs:8080/tfs/DefaultCollection’
Step:6 Close everything and open VS2008
File>Open>TeamProject
Step: 7 Connect.
I connected to TFS, but the problem is while I am trying to open the solution through VS2008 into TFS it is showing me an error
"This project (fmPilot.SSIS.ClientIntegrations.sln) cannot be opened from source control because it was created by a version of Microsoft Visual Studio that is incompatible with this one.
If this is the case, you may be able to open it from source control using that version of Microsoft Visual Studio, and then use Microsoft Visual Studio to open the local copy."
I also tried it through VS2010 but it is showing me an error
"Cannot be openned because its project type(/dtproj) is not supported bby this version of the application."
Can somebody help me on that..... I google it some says that permission might be the reason.. Please help me...
Thanks,
Karthik
Make sure that you have Business Intelligence Development Studio (BIDS) installed on your machine. Having just Visual Studio 2008 doesn't mean that you can open SSIS packages.
To verify whether you have BIDS installed:
Open Visual Studio 2008 IDE. Click Help and About Microsoft Visual Studio.
Make sure that you see SQL Server Integration Service.
Another way to verify is by trying to create a new project in VS 2008. You should see Business Intelligence Projects under Project types.
If you do not see this, then it means you don't have BIDS installed on your local machine. You can install BIDS by installing SQL Server 2008 client tools.
Following link shows how to install SQL Server 2008 client tools.
SQL Server 2008 Client Tools Installation