Read Me for Visual Studio 2005 Beta 1 for VS DATA Tools (by Mairead)

If you are having any problems with Visual Studio 2005 Beta1 in regards to VS DATA tools or in general let us know so that we can try and help you guys out.

For VS DATA features take a look at the following

Visual Data Tools Read Me Items for Visual Studio Beta1 2005


Using Visual Studio 2005 and SQL Server 2005

Connection from Visual Studio 2005 to SQL Server 2005 Beta 2 is supported within this Beta release however connection to SQL Server 2005 Beta 1 is not available and will render the following message

“This build of Yukon is not supported. You must have build 736 or later.”


Visual Studio 2005 and SQL Server 2005 can be installed and run on the same machine however if you uninstall SQL Server 2005 you will have to run the repair of Visual Studio from the Visual Studio 2005 CDROM only to ensure you maintain the same Visual Studio functionality. In the case of any of the Express SKUs installation, you would need to reinstall that respective Express SKU.


SQLCLR Written Routines

The timeout value for deploying routines onto the SQL Server is currently non configurable and will time out after 15 seconds. During the Build and Deploy process of these routines the output messages appear to be truncated within Database Output Window. SQLCLR debugging is not fully supported in this release of Visual Studio in that only the first call to the SQL Server is supported, for subsequent calls to the same server only TSQL debugging is enabled.


TSQL Debugging of Stored Procedures with SQL Server Express 2005

When making connections to SQL Server Express please specify the full server instance name(i.e. avoid using "." or "localhost"). By using "." or "localhost" as the server name you will lose the ability to debug Stored Procedures.


Database Projects and Scripting

Database Projects functionality is available and stable to use in this release. The opening of a saved Database Project on a different machine is not supported in this release. The creation of SQL Scripts such as store procedure, triggers(except View Triggers), database query is stable. Scripting of tables is supported provided you do not have a computed column within that table. Scripting of synonyms and object permissions is not supported in this release.


Data Designer\Builders\Editors Tools

View Designer, Table Designer and Query Builder are stable to use. The Table Valued, Scalar, Inline, Stored Procedure and Triggers Editors are also stable to use. The Design SQL Block also works within Triggers, Stored Procedures and Functions(however your Editor will switch to READ-ONLY while you are designing your SQL within the Query Designer, you must close the Query Designer to enable the editor again). The Verify SQL command is currently only available for queries which do not contain a parameter and are using the SQL managed provider.


Server Explorer/Database Explorer

The Server Explorer is working well. Enumeration of stored procedures can be slow at times; the opening of group stored procedures is not supported in Visual Studio Beta1 release. For Express SKUs C#, J# and Web Developer Express within the Create New SQL Server Database dialog, creation of a SQL Server Express database or MSDE database is not supported in this Beta release. Other points to note for an Oracle connection expanding the Synonyms node causes an unhandled exception and Oracle triggers are not displayed within the Server Explorer.

Comments (9)

  1. Nathan says:

    Any help with the following error would be helpfull. When using Web Developer 2005 Express to try and create a new database in SQL 2005 Express I get the following error:


    Visual Web Developer 2005 Express Edition Beta


    This feature is not supported by Microsoft Visual Web Developer Express




  2. Lance Delano says:

    Hmmm. It may be how you’re adding it. Try the following:

    1.) In your solution, choose "add new item" or "add existing item" to your project.

    2.) Choose the database (or point at the database file (if SQL, it must be first detached if you’re not using SSE).

    => Your database should be added to your project and a connection should be added directly in Server Explorer.

    Then, you should be able to directly use Server Explorer to add tables, etc.

  3. Mairead says:

    In addition to Lance’s comment you currently cannot create a SQL Server Express database wihtin the Web Developers Express Sku via right clicking on the Data Connections node in Server Explorer<Database Explorer> and then bringing up the Add New SQL Database. This is a bug which will be fixed for the next release of Visual Studio.

  4. Nathan says:

    Thanks for your help, after reading your article more carefully I discovered your mention of the database explorer limitation. Also, thank you Lance for the tip on adding a mdf file using "add new item", as I was able to establish a connection to this just fine.

  5. DavidC says:

    I removed .NET 2.0 first and now SQL 2005 Express won’t uninstall without .NET 2.0 installed. Is there a way around this? It shouldn’t be looking for the framework on a Remove command.

  6. Jeffrey Baker [MS - SQL] says:

    SQL setup needs the .NET 2.0 Framework to display UI during some Add/Remove Programs operations. We also need the framework to remove assemblies that were installed in the GAC.

    Therefore it is a requirement that it still be installed prior to removing SQL.

  7. Anthony Williams says:

    SQL setup needs the .NET 2.0 Framework to uninstall?

    Surely then, .NET 2.0 should not be allowed to uninstall if there are components that depend on it. Bad design, surely?

  8. Nicholas says:

    This is sort of off-topic, but I’m having problems with Whidbey and "Add New Item".. if I create a brand new project or web site, and go to "Add New Item", it shows all the items properly. But if I shutdown Whidbey, open it back up and load the project I just created, bringing up "Add New Item" shows an empty list. Any help at all would be appreciated, as this bug makes Visual Studio semi-worthless right now :-/

  9. The best thing you can do is enter a bug at (Look under the Top Bugs section). This will put it on the VS Team’s radar and they will investigate.


    Mike Bundschuh

    Windows Platform & Tools Team


Skip to main content