I'm trying to install Entity Framework 5.0 into a Visual Studio 2012 Pro project. Part way through the install it fails and crashes Visual Studio. I suspect that it is trying to figure out which SQL server edition to use when it fails. I have SQL 2008 R2, SQL 2012 and SQL 2012 Localdb installed. No connection string gets added to the config file before it crashes. I've been searching the forums and trying many things but no luck yet. Any help would be appreciated. Same failure when using Visual Studio 2010 Pro.
I found that the EF installer can't handle multiple versions of SQL installed side by side. After removing all but one the program runs fine.
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.
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
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
When installing SQL Server Express Edition 2008, checklist says
"Previous version of Visual Studio 2008"
and asked me to upgrade to sp1. Unfortunately sp1 for some reason refuses to install on my brand new pc (Windows 7).
So why can't I just bypass this ? Why would SQL Server Express needs VS2008 to install that's insane.
SQL Server install used to be as easy as 123, now it has become a nightmare like installing Oracle.
Will I have to go back to Windows XP ?
Because Sql Server Management Studio is built upon the Visual Studio standalone Shell.
You will find that if you choose not to install the SSMS this requirement will vanish, but this is probably not what you want to do.
Normally you won't need Visual Studio 2008 in order to install SQL Server. This can be caused by some previous versions that you had installed, beside the SSMS problem. Take a look here for required actions before installing SQL Server 2008.
I have to agree that SQL Server 2008 install is probably the worst SQL install ever.
Having said that, 2008 R2 is out now, perhaps the new management studio is built on VS2010? Alternatively, don't install Management studio and use something else like VS2008, or VS2010 express to access the database.
I just installed SQL Server 2005 and it installed Visual Studio 2005 too. What's the point of this? Is there an option in the SQL Server installation that can prevent this. If I uninstall Visual Studio now will it mess anything up? What if I now install Visual Studio 2008 too?
The visual studio that you get is a shell called Business Intelligence Development studio and it allows you to create Analysis Services, Integration Services, and Reporting Services projects. Also it allows you to deploy those projects to your SQL Server. If you already have Visual Studio installed, it will add those project types to it.
With the Development Studio you can add .Net projects such as C# or VB to your Analysis Services or Reporting Services projects to create custom components for them. There are additional benefits, but you should just do a search for Business Intelligence Development Studio to see what else can be done.
EDIT:
I just noticed that you were asking about what happens if you uninstall Visual Studio 2008. There should be a listing under your installed Programs called Visual Studio Shell or something of that nature, which is the Business Intelligence Development Studio and is independent of the main Visual Studio 2008 install. Both of them will allow you to create the Ms SQl Projects that I listed above. When you uninstall Visual Studio 2008 it won't uninstall this application and vice verse. If you do accidentally delete it, you can always install it again using your MS SQL CDs. There are instructions on the web to do so.
The version of Visual Studio that gets installed is necessary for doing the work you need to do in SQL Server. The old tools are going away, and this is part of the new.
Personally, I miss the Enterprise manager and SQL Query Analyzer from the SQL Server 2000 days, but they aren't likely to come back.
Edit - added
OK. The above was a bit flippant for an answer.
But to answer your comment, Management Studio IS Visual Studio, configured and modified to work with SQL Server.