R
RobGSCL
I'm having a twofold problem with the emulator in Visual Studio 2003.
When my IP address changes (typically when I move from my work network
to home), the studio loses the ability to launch an application. Oddly
enough it can still deploy. It must use a different mechanism for
deployment than it does for debug. The only way to fix it is to close
the studio and reopen it. Closing the emulator doesn't fix it and is
not needed.
The other half of the issue is that when I am not connected to a
network, I can't debug in the emulator. I considered making a cat5
loopback connector to trick media sense, but I was hoping there was a
way to fix this more gracefully.
Any input would be appreciated.
Thanks
Rob
When my IP address changes (typically when I move from my work network
to home), the studio loses the ability to launch an application. Oddly
enough it can still deploy. It must use a different mechanism for
deployment than it does for debug. The only way to fix it is to close
the studio and reopen it. Closing the emulator doesn't fix it and is
not needed.
The other half of the issue is that when I am not connected to a
network, I can't debug in the emulator. I considered making a cat5
loopback connector to trick media sense, but I was hoping there was a
way to fix this more gracefully.
Any input would be appreciated.
Thanks
Rob