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.
Related
I have VS 2017 CE, SQL Server 2016 DE and Microsoft SQL Server Management Studio 13.0.16106.4. About VS is showing Microsoft SQL Server Data Tools as installed.
I would like to install SSDT so that I can do the SSRS/SSIS and SSAS but I don't know which one to install, it's giving few options from here
It reads
Download SQL Server Data Tools 17.1 for Visual Studio 2015
Download Data-Tier Application Framework (DacFx) 17.1
From the same website
It then advises "To use SQL Server Data Tools in Visual Studio 2017 see this section below". When I go to the link provided it takes me to visualstudio.com website. It's not apparent to me what I need to download from there, is it the Community Edition?
Going back to the first link I provided, it advises...
If you are using SSDT with Visual Studio 2017, install the AS and RS components:
Analysis Services
Reporting Services
I also found another link...www.visualstudio.com/vs/ssdt/
Also are there any conflict between sql server 2016 and vs 2017 CE when taking SSRS/SSIS or SSAS tasks?
StackOverFlow is giving me message that I need to have number of reputation before I can give more than 1 website link.
Can someone advise me which one to install?
Thanks.
For Visual Studio 2017, there is not yet a stand alone install of SSIS|AS|RS. However, there are VSIX installs available for RS and AS. See links below.
SSIS is working on creating a standalone install as well as a VSIX package.
https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio
https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftAnalysisServicesModelingProjects
I am using Windows 7 SP1.
I have SQL Server 2012 installed along with Visual Studio Community 2015.
The SQL Server 2012 installation has always forced me to use VS2010 Shell to launch SQL Server Data Tools.
I recently installed an update through the NuGet Package Manager in VS2015 which included SSDT. I was hoping that this would enable me to use SSDT with VS2015. However it still launches with VS2010.
My question is: How do I used SQL Server Data Tools with Visual Studio 2015?
Thanks
The latest release (Feb 2016) is the first release of SSDT that can target different versions of SSIS so you can now target 2012 from visual studio 2015:
https://blogs.msdn.microsoft.com/ssdt/2016/03/07/ssdt-preview-update-feb-2016/
It is still in preview though so you will need to download the pre-release bits:
https://msdn.microsoft.com/en-us/library/mt204009.aspx
or wait a month or so for the RTM release.
I usually use the pre-release builds and they are normally pretty solid but each environment is different :)
ed
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
Microsoft Visual Studio
Could not load file or assembly
'Microsoft.SqlServer.Management.Sdk.Sfc, Version=11.0.0.0,
Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its
dependencies. The system cannot find the file specified.
I cannot "see" the referenced DLL even though it is in the proper spot. I can therefore not bind the datasource to the control. What might I be failing to do?
Please see original question and answer here: Could not load file or assembly Microsoft.SqlServer.management.sdk.sfc version 11.0.0.0
Problem: This issue happens when assembly Microsoft.SqlServer.management.sdk.sfc version 11.0.0.0 not found by visual studio 2012.(Sql server 2012)
Solution: just go to http://www.microsoft.com/en-us/download/details.aspx?id=35580 and download:
ENU\x64\SharedManagementObjects.msi for X64 OS or
ENU\x86\SharedManagementObjects.msi for X86 OS,
then install it, and restart visual studio.
Problem: This issue happens when assembly Microsoft.SqlServer.management.sdk.sfc version 10.0.0.0 not found by visual studio 2010.(Sql server 2008)
Solution: just go to http://www.microsoft.com/en-us/download/details.aspx?id=26728 and download:
1033\x64\SharedManagementObjects.msi for X64 OS or
1033\x86\SharedManagementObjects.msi for X86 OS,
(In most cases downloading this is better http://go.microsoft.com/fwlink/?LinkId=123708&clcid=0x409)
then install it, and restart visual studio.
From here:-
From the error message, we can see there is some missing component in
VS 2012 installation. The assembly in question -
Microsoft.SqlServer.Manangement.Sdk.Sfc version 11 - is a component
DLL for SMO assemblies (even though SFC was originally created for
more ambitious SSMS extension), and it is included in SQL Server 2012
Shared Management Objects.
[SQL 2012 Shared Management Objects] has dependency on [SQL System
CLR types] component, so you have to install SQL Server System CLR
Types first.
[SQL Server 2012 System CLR Types] can be found in the middle of SQL
2012 Feature Pack web page (
http://www.microsoft.com/en-us/download/details.aspx?id=29065 )
Just want to share my experience on this.
I, too, encountered this error. I'm using MS Visual Studio 2013 and I have an MS SQL Server 2008, though I have had MS SQL Server 2012 Installed before.
I was banging my head on this error for a day. I tried installing SharedManagementObject, SQLSysClrTypes and Native Client, but it didn't work. Why? Well I finally figured that I was installing 2008 or 2012 version of the said files, while I'm using Visual Studio 2013!! My idea is since it is a database issue, the version of the files should be the same with the MS SQL Server installed on the laptop, but apparently, I should have installed the 2013 version because the error is from the Visual Studio and not from the SQL Server.
I had this problem after installing SQL Server Express 2014. Apparently 2012 points to some files that are in 2014 and I completely erased all old versions of SQL Server. After much frustration I ended up reloading Visual Studio 2013 and it set up all of the files it needed and now works with SQL Server Express 2014
I had Visual Studio 2008 Professional Edition installed in my computer. When i installed this VS 2008 version, SQL Server 2005 was also automatically installed. I just had to install SQL Management Studio
Because i want to install SQL Server 2008. I un-installed SQL Server 2005 and tried to install SQL Server 2008. But in the "Installation Rules" section in the installing setup, it prompts a message saying "Previous Release of VS 2008 Failed" (see the image below)
When I google it, i came to Microsoft Support where they say the VS Version i have must be Service Pack 1 and must be a release version (not beta version). Now I'm confused with it.
What should I do?
How do I find the Service Pack Version of VS 2008
How do I find if the version is a release or a beta one
I recently installed VS 2010 C# Express and Web Developer 2010 Express. Without going to SQL Server 2008 can I work with VS 2010 with SQL Server 2005?
How do I find the Service Pack Version of VS 2008?
There are service packs for Visual Studio 2008 express that are different to the VS2008 standard / prof etc service packs.
How do I find if the version is a release or a beta one? No idea.
I recently installed VS 2010 C# Express and Web Developer 2010 Express. Without going to SQL Server 2008 can I work with VS 2010 with SQL Server 2005?
Yes you can work with SQL 2005 with both of those to the best of my knowledge.
You can try uninstalling all instances of visual studio and then installing sql 2008 but that would be a last resort i would think. Trying the vs2008 express service packs would be my first step.
Rgds
AJ
See this http://support.microsoft.com/kb/956139 and for a more detailed answer see this
http://blogs.msdn.com/b/psssql/archive/2008/08/11/sql-server-2008-visual-studio-2008-sp1-and-net-framework-3-5-sp1-explained.aspx.
I also had this issue and when I visited Microsoft site, then I found this solution and it worked.