Just "upgraded" SQL Server Express 2008 to 2008 R2. Now Visual Studio 2010 does not run; it tries to open the welcome screen and just sits there consuming resources (CPU and RAM), but nothing every happens. I'm removing R2 and repairing VS 2010 install (Ultimate version, Windows 7 Professional 32 bit). Is this a lost cause?
Found the problem and it had nothing to do with SQL Server 2008 Express R2 or VS 2010 corruption. This is running in Virtualbox and I had set 3D Acceleration on FORGETTING that doing this KILLS VS 2010. I don't know why it does, but it does. Turned it off and everything runs fine. Just wasted a day uninstalling and reinstalling, all for naught.
Related
I installed Visual Studio 2010 on my home computer so I could do a little work from home. After having some issues with SQL Server Express, which got installed by VS2010, I got a copy of SQL Server 2008 R2 from my company. Let me openly admit I know jack about DBA in SQL Server.
At first it sort of worked, but seemed like I needed to rename the database name every time I opened it. Now VS2010 won't even open the connection at all. I keep getting an error stating one is version 661 and the other is 655 and they're not compatible. To make matters worse, I can't even attach the database in SQL Server 2008 R2 anymore.
Any ideas on how to rectify this? Please oversimplify and assume I'm an idiot, because in this case I am.
OK, well apparently VS2010 installs SQL Server 2008 Express on your computer, with which it will happily communicate. Since I then installed SQL Server 2008 R2 after that, 2008 R2 is considered an upgrade and SQL databases are not backwards compatible.
In order to fix this, I installed SQL Server Express 2008 R2 (specifically the SQLEXPRWT_x86_ENU.exe file as that one comes with additional tools) and after a reboot I was able to successfully add the database to my VS project.
NOTE: I did not remove SQL Server 2008 R2, I merely upgraded SQL Server 2008 **Express*.
As an aside, before doing this I could never have VS and SQL Server 2008 R2 open simultaneously. After this upgrade, I can have them both open at the same time which is how it should work.
I am preparing to do some web development against a SQL Server 2012 server on a fresh install of win 7 x64 development VM.
What should I install first, visual studio or SSMS?
This is my favorite order:
Windows update before installing anything.
SQL Server 2012
If you have SP1 integrated with you ISO file, skip to step 4.
If you have both SP1 and U5 integrated with your ISO file, skip to step 5
Unselect SQL Server Data Tools during installation (step 8 will install the VS 2012 templates instead of these old 2010 ones)
SQL Server 2012 SP1
SQL Server 2012 SP1 U5
Visual Studio 2012
If you have U3 integrated with you ISO file, skip to step 7.
Unselect SQL Server Data Tools during installation because we'll install the updated bits in step 7
Visual Studio 2012 U3
SQL Server Data Tools - BI (adds BI project templates to Visual Studio 2012)
SQL Server Data Tools (allows you to manage SQL Server 2012 from within visual Studio 2012)
Windows Update
ReSharper
StyleCop
SQL ToolBelt
Neither - you can install them in any order. While you do get the occasional question about it in various different forums, I have done this and never had an issue.
SQL does have a Visual Studio dependency (formerly) called BIDS, but Visual Studio can install over/around this no problem.
Note that this answer is correct when using the initial SQL 2012 release (as that was the latest edition when this question was asked). Subsequent releases may have changed things. I have made this answer CW to encourage others to edit it as necessary to include info about later versions.
I don't know if there is a different way for VMs but on Windows we used to install SQL Server first, as some of the configurations of Visual studio conflict with SQL Server configurations if it was installed before
No direct dependencies found between the two components, installing Visual Studio first then ensure that .NET Framework installed properly is my approach, then installing SQL Server, but in all cases the SQL Server installation installs the following software components - 2008:
NET Framework 3.5
SQL Server Native Client
SQL Server Setup support files
My approach:
Visual Studio 2008.
Visual Studio SP1.
SQL Server 2008.
Run Windows updates.
Useful question here
I am currently working on a long-term project for which I need Visual Studio 2005, 2008, 2012 (2010 not necessary). Right now I have Windows 7, but I would really like to upgrade. Is it possible to install all of those versions of Visual Studio on Windows 8?
2012 can obviously installed (and takes away the need for 2010). I already found reports that 2008 is also possible if the 3.5 framework is enabled through Windows Features, but I'm unsure about Visual Studio 2005.
Is it possible and does anybody have any experience with this?
PS: Do not come with solutions as "Why still use 2005, 2008, ...", I really need it.
After installing it on VMWare (Virtualbox gives errors) I've enabled framework 3.5 (which indeed contains 2.0 and 2.5). After that I've installed Visual Studio C# Express Edition. During installation and startup of VS it gives a lot of "This program has been known for comptability problems" warnings and they offer to search help online or to run it as usual. I've always opted to let it run as usual. It installed fine and I could compile and run a Visual C# Windows application.
Visual Studio 2005 Standard installed mostly fine for me. I installed it on Windows 8 on an x64 CPU. It complained a bunch about "known compatibility issues," but if I told it to carry on everything seemed to go fine. The only catch was that "Microsoft SQL Server 2005 Express Edition x64" failed to install. Also, I had to run Visual Studio as administrator the first time so it could finish its setup, but after that I've just run it with my normal account.
Download Windows 8 Enterprise Evaluation and install to VMWare or Virtual Box. It's a 3 month trial and would allow you to test VS2005 plus the others. Once downloaded, it's a fast install. You can download from here: http://msdn.microsoft.com/en-us/evalcenter/jj554510.aspx
For an install of Visual Studio 2005 on Windows 7 as well as Windows 8 I install three things: (1) Visual Studio 2005, (2) Visual Studio 2005 Service Pack 1, and (3) Visual Studio 2005 Service Pack 1 Update for Windows Vista.
The Visual Studio 2005 service packs can be a bit difficult to locate on Microsoft's web site since everything is really about Visual Studio 2012 and later.
When installing Visual Studio 2005, there will be a number of Incompatible warnings displayed. I just click through them to get to the end.
Also I do a custom install and do not install some components: (1) Crystal Reports and (2) SQL Server 2005 Express Edition.
Microsoft Visual Studio 2005 Team Suite Service Pack 1 which seems to be for all editions of Visual Studio 2005 including Professional Edition which I use.
Microsoft Visual Studio 2005 Service Pack 1 Update for Windows Vista is required to update Service Pack 1 to work with Windows Vista and later.
Visual Studio 2005 / 2008 won't install by default on Windows versions later than 7.
In Windows 8.1, go to:
Control Panel > Programs and Features > Turn Windows features on or off
Check the box labeled ".NET 3.5 (Includes 1.0 and 2.0)" and press OK / Apply.
My system has issues with trying to download the files for such programs, and thus there is a way to bypass this error by running a script which installs the files from a Windows installation disc.
Here is the script (for error 0x800F0906, at least):
Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccess
You can replace /Source:D: with whatever drive letter you may be using for your optical / virtual drive, if needed.
I'm using SQL Server Management Studio 2008 and SQL Server 2008.
Currently, I cannot create new database diagram from the SSMS 2008 on an SQL Server 2008 instance.
Has anyone ever experienced this ?
The problem started after I tried to install Visual Studio 11 Beta, and apparently the Beta also installs SQL Server 2012 RC0. Now I have uninstalled the Visual Studio 11 Beta and the SQL Server 2012 that goes along with it.
EDIT :
Error message that shows when I tried to create new database diagrams is : "The specified module could not be found (MS Visual Database Tools)"
I had the same problem but never found an explanation of what was wrong. I ended up uninstalling SQL Server 2012, uninstalling Visual Studio 11 Beta, and then reinstalling the Visual Studio 11 Beta (keeping SQL Server 2008). I can now create DB diagrams from SSMS 2008, but not from within Visual Studio 11 Beta (I don't think Visual Studio 11 Beta supports the feature, at least not for SQL Server 2008).
I am at a total loss when it comes to WPI and the continous reinstallation of Visual Studio 2010 SP1. I have even went as far as creating a virgin machine and installed VS2010 and then immediatly installed the tools from WPI. After completion (which shows success) I reboot the machine and then load the WPI again to add on secondary tools. At which point, the WPI triggers an installation of the SP1 -- 90 minutes later, the list shows up as successful, and other tools are listed for installation.
Every time you run WPI, it wants to go through the VS2010 setup over and over. Is there any way to fix this behaviour?
Thanks in advance.