Using “run as” with Visual Studio debugger?

The first two options that come to mind are Log onto the machine as the user (simplest approach) Right-click on the Visual Studio executable and run as that user I think that you could edit the . Config file to use impoersonation, but I'm not sure if that will result in the app running truly the way it would for the user Although with good error handling, the error message itself should be enough to tell you where in the code the problem is... At the very worst, you could compile it in debug mode (so you have all the symbols) and add some global error hanlding and get the exact stack trace.

The first two options that come to mind are... Log onto the machine as the user (simplest approach) Right-click on the Visual Studio executable and run as that user. I think that you could edit the . Config file to use impoersonation, but I'm not sure if that will result in the app running truly the way it would for the user.

Although with good error handling, the error message itself should be enough to tell you where in the code the problem is... At the very worst, you could compile it in debug mode (so you have all the symbols) and add some global error hanlding and get the exact stack trace...

I will try running VS as the user in question – Tony Peterson Jun 7 '10 at 19:16.

I use David Strattons second solution (run as Administrator) because my application requires administrator privileges (-> elevated). Another solution could be to start the application as the user and use "Debug | Attach to process...

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.