[Home]
[Edit this page]
[Recent Changes]
[Special Pages]
[Help]
ASPNETFAQ_RemoteDebugging
Back to ASP.Net FAQ Main Page.
Here's a few ides on how to get that to work:
On the server enable COM internet services and Distributed COM. You do that by doing the following:
For computers without a domain server, you should make sure that both the server and the local client has the same username and password in the user-database. If you use the user "Administrator" on the client, make sure that is available on the server and that they have the same password.
Make sure the user on the server is a member of the debugger group.
Set full disk/file access for this user to the \WINNT\Microsoft.NET and to the path where the files you try to debug is located.
Do not reference the server from the client using IP Addresses, use the server name instead , like "LocalServer". IP Addresses seems to be less trusted.
Make sure ASP.NET debugging is enabled in your .NET project properties.
[Edit this page] [Page history] [What links here] [Discuss this topic] [Printer Friendly]
ASPNETFAQ_RemoteDebugging
Back to ASP.Net FAQ Main Page.
How to get started using Remote Debugging
Getting remote ASP.NET sourcecode debugging to work between a server and a client using Visual Studio.NET can sometime give you headaches.Here's a few ides on how to get that to work:
On the server enable COM internet services and Distributed COM. You do that by doing the following:
- Open the control panel
- Open Administrative Tools
- Doubleclick on the Component Services to open the Component Services Microsoft Management Console (MMC).
- DoubleClcik on Component Services
- DoubleClcik on "Computers"
- Right Click on the "My Computer" and select properties
- Click on the Default Properties tab
- Make sure both the Enable Distributed COM and Enable COM Internet Services are checked
- Press Apply and restart your computer
For computers without a domain server, you should make sure that both the server and the local client has the same username and password in the user-database. If you use the user "Administrator" on the client, make sure that is available on the server and that they have the same password.
Make sure the user on the server is a member of the debugger group.
Set full disk/file access for this user to the \WINNT\Microsoft.NET and to the path where the files you try to debug is located.
Do not reference the server from the client using IP Addresses, use the server name instead , like "LocalServer". IP Addresses seems to be less trusted.
Make sure ASP.NET debugging is enabled in your .NET project properties.
[Edit this page] [Page history] [What links here] [Discuss this topic] [Printer Friendly]
