I worked on this problem for weeks, I reformated my computer at lease 5x and re-installed everything.
There is a bug some where that Microsoft doesn't know about. There are two ways installing Visual Studio 2008 Pro and MS-SQL 2008 Developers Edition. I did install both ways and follow the install procedures that Microsoft SQlL help fiiles says to the
letter.
The problem steems from MS-SQL 2005 Shared files. The upgrade to 2008 Shared files will cause the database connection error in VS 2008. And only in VS 2008. MSSQL Server is up and running in every other program.. It even works in VS 2008 Reporting Service,
SQL Server Business Intelligence Development Studio, Microsoft SQL Server Integration Services, and Microsoft SQL Server Analysis Services. But it will not create a database or the ASPNETDB.MDF from the ASP.NET configuration tool or from the add new item
menu.
The work around solution I came up with is to install SQL Server 2005 Express with Advance Tools. Then Install MSSQL 2008 Developers Server and I didn't upgrade the SQLExpress instance to a 2008 instance
MSummers
Member
105 Points
28 Posts
Re: connection to SQL Server files (*.mdf) require SQL server express 2005 to function properly.
Dec 02, 2009 01:23 AM|LINK
I worked on this problem for weeks, I reformated my computer at lease 5x and re-installed everything.
There is a bug some where that Microsoft doesn't know about. There are two ways installing Visual Studio 2008 Pro and MS-SQL 2008 Developers Edition. I did install both ways and follow the install procedures that Microsoft SQlL help fiiles says to the letter.
The problem steems from MS-SQL 2005 Shared files. The upgrade to 2008 Shared files will cause the database connection error in VS 2008. And only in VS 2008. MSSQL Server is up and running in every other program.. It even works in VS 2008 Reporting Service, SQL Server Business Intelligence Development Studio, Microsoft SQL Server Integration Services, and Microsoft SQL Server Analysis Services. But it will not create a database or the ASPNETDB.MDF from the ASP.NET configuration tool or from the add new item menu.
The work around solution I came up with is to install SQL Server 2005 Express with Advance Tools. Then Install MSSQL 2008 Developers Server and I didn't upgrade the SQLExpress instance to a 2008 instance
Visual Studio 2008