Warning: June CTP of Visual Studio 2005 is not compatible with the June CTP of Sql Server 2005

From the MSDN Download Section:

NOTE: Visual Studio 2005 June CTP is not compatible with the SQL 2005 June CTP, but will work with the included SQL Server 2005 Express Edition. The June CTP of Visual Studio 2005 Team Foundation Server requires the April CTP of SQL Server 2005.

These types of issues are creating confusion for folks.  Be aware that the various groups are at various stages in their development process and during the pre-release times, not everything will work together correctly with everything else. 

5 Comments

  • I am running both on a VPC here at DevTeach and having no problems at all. For example, just this morning in a session I was able to create managed stored procedures and functions in the latest VS 2005 Beta 2 and deploy them toe SQL Server 2005 June CTP with no problems at all. What are the problems everyone is encountering?

  • From your post, you are using the April CTP of VS 2005. I pulled this straight from the MSDN web site for downloads.

  • True -- I am not using VSTS. But, I thought it was the version that just came out.

  • I have visual studio 2005 and sql server 2005 june ctp both running on 2 virtual machine and it installed fine. I had visual studio 2005 installed - then tried to install sql 2005 which complained - I then ran an uninstall exe (sqlbuw.exe) within sql and it uninstalled the .net 2.0 framework and then sql 2005 installed it (different version) and both run fine.



    Cheers

    Gregor

  • The June SQL Server CTP will not install on a Domain controller, which knocks out a TFS install on a single machine, unless you install SQL Server 2005 first. As the MSDN site mentions that you cannot install the June SQL CTP with the June TFS, it is easier to install the June SQL with April VS and June VS with April SQL.



    The main issue I can see between the two is the version of the Framework. The SQL version has incremented beyond just build number. Not sure about the VS version.

Comments have been disabled for this content.