Wrox Programmer Forums
| Search | Today's Posts | Mark Forums Read
Visual Studio 2005 For discussing Visual Studio 2005. Please post code questions about a specific language (C#, VB, ASP.NET, etc) in the correct language forum instead.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Visual Studio 2005 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old June 28th, 2007, 08:48 PM
Registered User
 
Join Date: Jun 2007
Location: , , .
Posts: 2
Thanks: 0
Thanked 1 Time in 1 Post
Default debugging in visual studio.net 2005

 I basically want to 'step through' t-sql 2000 statements and I have tried the several methods. Can you tell me what would you suggest? I have tired the following methods:
 1. I have a question about setting up visual studio.net 2005 professional version to debug with a sql server 2000 database. The visual studio.net 2005 is on my workstation and the sql server 2000 databases are on two separate window server boxes.
  My goal is to debug some t-sql commands. To do this, I have setup a project as a database project. The insturctions on the microsoft website url says that I need to
attach to a process and the process that I need to attach to is 'sqlserver.exe'. However, I can not find this process to connect so. Thus, I can not attach to it if it is not in the drop down list.
  Thus can you tell me what my next step would be?
  Does it make a difference if I select wanting to debug as 'T-sql clr' or with the 'SQL CLR' debugger?
2. I have tried to use query analyzer 2000 from my workstation so that I can debug a stored procedure. I select the stored procedure I want from the object browser and right click to debug. The debug window does show up and the only icons that are not grayed out are the set breakspoints, and start to run. It does not allow me to set through or 'step into'. What is wrong here?

  Thanks!
The Following User Says Thank You to wendy elizabeth For This Useful Post:
 
Old June 28th, 2007, 10:58 PM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

In order to debug you need to be able to attach to a process, typically this process is one running on your local machine. Attaching to another machine's process is going to difficult if not impossible. I know there are ways to do remote debugging for ASP.NET apps, but this requires the installation of remote debugging helpers on the server.

In your case, it would be best if you can run the database on your development machine (i.e. install SQL SERVER) so you can attach to the sqlserver.exe process. I haven't done this myself, but the principals of debugging should be the same as other processes.

-Peter




Similar Threads
Thread Thread Starter Forum Replies Last Post
Deploy CR with Visual Studio 2005 VB.Net clflyer Crystal Reports 0 March 7th, 2007 12:41 PM
Visual Studio Debugging Zeus_Man General .NET 1 November 3rd, 2006 07:49 PM
Visual Studio .net2003 and Visual Studio 2005 Gert Visual C++ 1 January 24th, 2006 05:10 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.