remote debugger for .NET? Should i install something on the remote server?

Hi;

I need to do remote debugging on a server that I am not admin. The owners of the server don't want me to install Visual Studio on that server. Any painless way to handle this?

Best regards.
LVL 12
jazzIIIloveAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MlandaTCommented:
An efficient and less invasive way to do remote debugging is to improve your logging. You don't really need to connect Visual Studio to the remote machine. Add enough logging to your application and it will help you to get a very good view into what is going on there.

A good logger for .NET is log4net (http://www.beefycode.com/post/log4net-tutorial-pt-1-getting-started.aspx)

1 - It's easy to add to your solution (via Nuget)
2 - It will log a lot of details about the exception
3 - It can write to a text file OR send the logs to a UDP port
4 - You can use a tool like Log2Console to vierw the logs and see what is happening internally in the system in real time (https://log2console.codeplex.com/)
5 - Log2Console gives you a really nice view into your application with excellent filters and stuff.
log2console-logfiles.png
0
jazzIIIloveAuthor Commented:
Hi;

I have extensive logging on the server. My question is about rather live debugging.

Br.
0
MlandaTCommented:
Ah I see. Though with the right logging, you generally reduce the need to attach the debugger to a remote process. Anyways, there are restrictions listed here Remote Debugging Under Another User Account. The page lists the different security related constraints applied to remote debugging and suggests a registry change (HKEY_LOCAL_MACHINE \Software\Microsoft\Machine Debug Manager\AllowLaunchAsOtherUser) that one can make to enable the debugging.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET App Servers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.