Sign in
 
Team System Developer Center > Visual Studio Team System Forums > Getting Started With Visual Studio Team System > Needed Features In Visual Studio 2008 Server Explorer ( MVP Submission )
Ask a questionAsk a question
Search Forums:
 

General DiscussionNeeded Features In Visual Studio 2008 Server Explorer ( MVP Submission )

  • Friday, May 02, 2008 9:04 PMkarl140.6 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I’ve been trying to utilize the Server Explorer in Visual Studio 2008 for my SQL Server programming tasks like table maintenance and stored procedure authoring.  However this new workflow is not as productive as using SQL Server Management Studio.

     

    I have posted this same article on my blog that also has images.

    http://karlshifflett.wordpress.com/2008/05/02/needed-features-in-visual-studio-2008-server-explorer/

     

    I have posted this problem on Microsoft Connect here: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=341791.  Please rate this issue on Microsoft Connect so that it will get corrected.  VS2005 had the same issue and I wish I would have known how to report problems like this long ago.

     

    Viewing Table Columns

    When viewing column information in SQL Server Management Studio you view the column name, if it is part of the primary key, data type, length and if it is nullable.

     

    When viewing column information in VS2008 you view the column name.

     

    Yes, when you click on a column, the Visual Studio 2008 Properties Window displays this and more data.  However, when you click back to the code window or anywhere else, the Properties Window data changes.  Also, having to click on a column to see its information slows the developers workflow down.  Please display at least the same information that SSMS does for a column.

    Copying Column Name(s)

    Another very missed piece of functionality is the ability to copy one or more column names from the above displayed list into either a stored procedure or code window. 

    In SSMS the developer can drag the Columns folder into a code window and all column names are copied into the code window separated by commas.  Visual Studio 2008 does not have this.

    In SSMS the developer can drag the column name into a code window and the column name is copied into the code window.  Visual Studio 2008 does not have this.

    This is an invaluable time saver and ensures accurate copying of column names into code or stored procedures.

    Viewing Stored Procedure Declarations

    Stored procedure parameters haver the same problem that the table column names do.

     

    Close

    I do like the fact that many features have been moved into Visual Studio (STRONGLY wish SSMS could debug stored procedures) but if I’m being asked to alter my workflow, then I should at least have the same features that the other tool does.

     

    Microsoft, please update Visual Studio 2008 with these features

     

    Thank you!