Remote Transact-SQL Debugging on Windows Vista
This topic applies to:
Edition |
Visual Basic |
C# |
C++ |
Web Developer |
|---|---|---|---|---|
Express |
.gif "Topic does not apply") |
|
|
|
Standard |
|
|
|
|
Pro and Team |
.gif "Topic applies") |
|
|
|
Table legend:
|
Applies |
|
Does not apply |
.gif "Topic applies but command hidden by default") |
Command or commands hidden by default. |
When you do T-SQL debugging or T-SQL application debugging against a remote SQL server, Visual Studio must configure the Windows Firewall before remote debugging can begin. Normally, this configuration occurs when you try to step into a T-SQL stored procedure on a remote computer.
On Windows XP, the Windows Firewall configuration starts automatically. On Windows Vista, the new security model requires that you grant permission before the software can configure the Firewall. As a result, a Visual Studio dialog box appears, informing you that the Firewall has to be configured, followed by the Windows Vista User Access Control dialog box. If you grant permission in the UAC dialog box, the Configure Firewall for Remote Debugging wizard appears.
See Also
Tasks
How to: Set Up Remote Debugging
Concepts
The Windows Vista Security Model