AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() Everything from the bin\Debug folder of the application must be copied to the test machine.I ran the application instead of setting it up as a service, so I needed to make sure it ran as an administrator.Use the setup program that matches the OS (x86, 圆4, ia64).The Visual Studio 2010 Remote Debugging Monitor needed to be installed on the test machine.This is the username that the remote application is run under. ![]() The machine username on the test machine (TestMachine\travis).The machine username on my machine (MyMachine\travis).This is the username that Visual Studio is run under. The domain username on my machine (domain\travis).3 instances of the same username needed to exist as administrators (and have been logged into at least once).Here are the main points that I gathered from it: I started off using Danny Warren’s Remote Debugging post to get both my machine(on domain) and the test machine(off domain) enabled so that I could Attach to Process ( Ctrl+Alt+P) from VS 2010 on my machine. I was almost to the point of taking the time to install Visual Studio 2010 on the test machine, when my coworker, Bryan Coon, reminded me of the Remote Debugging capabilities of VS and recommended trying that first. In my latest project I was running into an issue where running my installed application on a test machine was crashing before it could even startup, but it ran perfectly when installed on my machine.
0 Comments
Read More
Leave a Reply. |