Hi Jason,

You can't do remote debugging across Windows domains, unless those domains
have two-way trust. This is a DCOM security restriction. You can
use TCP/IP instead of DCOM for the remote debugging transport, but most
firewalls will block the IP ports required for TCP/IP remote debugging.
Note that this restriction effectively prevents standard remote debugging
across the Internet.

One workaround for remote debugging across domains that don't have two-way
trust is to use Terminal Services to log into a machine in the remote
domain. Providing this remote machine has Visual Studio installed, you can
them perform local debugging on that machine or remote debugging on another
machine in the remote domain.

There are also some security restrictions imposed by Visual Studio when
doing remote debugging.

* You can't use Visual Studio to attach to, or launch, a remote process
running in another user's Terminal Services session.
* Unless you're an administrator on a remote machine, you can't attach to a
process started by a console (non-system) user on that machine. This
security restriction doesn't apply if you and the console user have the same
Windows account.
* You can't attach to a Windows service on a remote machine unless you're an
administrator on that machine.
* You can't launch a process on a remote machine unless you're logged into
that machine, either locally or using Terminal Services.

Creating or modifying the following registry key on the remote machine can
overcome these security restrictions:
HKEY_LOCAL_MACHINE \Software\Microsoft\Machine
DebugManager\AllowLaunchAsOtherUser

This registry key should be set to a DWORD value of 1. In addition, for the
last two security restrictions in this list, you need to have an
administrator logged into the remote machine during the debugging session.
This is an added security measure required by the Visual Studio debugger.

HTH,

Mark
--
Author of "Comprehensive VB .NET Debugging"
http://www.apress.com/book/bookDisplay.html?bID=128


[quoted text, click to view]
Hi everyone,

I'm going to start telecommuting soon and i need some advice on how to set
up my home pc for .net. The situation is -- at my job site i have a
workstation with VS installed. My projects work against a Oracle DB located
on the company server. Now that i'm working from home, should i :

a) copy all source code to my home pc AND install Oracle on it in order to
be able to debug and run projects. (NOT PREFERRED!)

b) copy only the source code, and *somehow* hit the Oracle DB on the company
server.

c) keep all code on my workstation at my job site and remotely log in.
(preferred)

In other words, is there a way where i can remotely debug? Perhaps using a
VPN or something? I'd really appreciate any advice. Thank you.

Rafael Z.