I've been struggling for some time now to be able to use the built-in functions in Visual Studio 2008 to handle *.mdf
database files with SQL Server 2008 Express. I'm running on an x64-based system, and I've read that there is a known problem with this setup, but the hotfix has not solved my problems.
Basically, what happens is that when I try to add a new *.mdf
file to the App_Data
folder of a project, I get an error message saying:
Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to function properly. Please verify the installation of the component or download from the URL: http://go.microsoft.com/fwlink/?LinkId=49251
My (unsuccessful) steps to solve this:
When I look in the Help/About
dialog, the hotfix shows up among applied updates. I have also checked and double-checked that the SQL Server instance name is correctly set in Visual Studio (I copy-pasted the instance name from the login screen in SSMS).
Why does the hotfix not solve my problems? Am I doing things in the wrong order, or do I have the wrong software versions somewhere?
According to the KB article, the problem is that Visual Studio doesn't correctly detect "some registry keys" - but nothing is said about which keys. Does anyone know how to fix this manually?
Oh, and yes - I've seen this post. I know I could just "downgrade" to the x86 version of SQL Server, but I really want to make this work with the x64 version (if nothing else, just because it's supposed to work...), so that solution doesn't really solve my problems. Please don't close this as a duplicate.
Generally, It is required to install sql server database with visual studio setup. Here are the steps to install sql server database with setup using custom action. 1. In Solution Explorer, select the project.
I had this same error, VS 2008 SP 1 on Vista Ultimate 64 bit with SQL 2008 Express 64 bit. Downloaded the hotfix and rebooted, started up SQLEXPRESS and still got the error.
Then I changed my "SQL Server Instance Name" (under VS 2008 -> Tools -> Options -> Data Connections), which was blank, to "SQLEXPRESS" (versus ".\SQLEXPRESS", which is what I use in my login screen under SSMS.) and now it works like a charm!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With