<div>
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.<br />
<br />
A good logger for .NET is log4net (<a href="http://www.beefycode.com/post/log4net-tutorial-pt-1-getting-started.aspx" rel="ugc">http://www.beefycode.com/post/log4net-tutorial-pt-1-getting-started.aspx</a>)<br />
<br />
1 - It's easy to add to your solution (via Nuget)<br />
2 - It will log a lot of details about the exception<br />
3 - It can write to a text file OR send the logs to a UDP port<br />
4 - You can use a tool like Log2Console to vierw the logs and see what is happening internally in the system in real time (<a href="https://log2console.codeplex.com/" rel="ugc">https://log2console.codeplex.com/</a>)<br />
5 - Log2Console gives you a really nice view into your application with excellent filters and stuff.<br />
<a href="https://filedb.experts-exchange.com/incoming/2015/08_w35/931984/log2console-logfiles.png" target="_blank" class="file-inline" title="Borrowed from https://sitecore.unic.com/-/media/images/vibes/reh/log2console_logfiles.png?h=373&w=619&la=de (221 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>log2console-logfiles.png</a>
</div>


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 [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/ [https://log2console.codeplex.com/])
5 - Log2Console gives you a really nice view into your application with excellent filters and stuff.
log2console-logfiles.png [https://filedb.experts-exchange.com/incoming/2015/08_w35/931984/log2console-logfiles.png]

Borrowed from https://sitecore.unic.com/-/media/images/vibes/reh/log2console_logfiles.png?h=373&w=619&la=de

log2console-logfiles.png

<div>
Hi;<br />
<br />
I have extensive logging on the server. My question is about rather live debugging.<br />
<br />
Br.
</div>


Hi;

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

Br.

<div>
<div class="content wysiwyg-content">
Hi;<br />
<br />
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?<br />
<br />
Best regards.
</div>
</div>


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.

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

.NET application servers, a Windows Server role in an application role, includes Internet Information Services (IIS) to provide web server support, the .NET Framework to provide application support, ASP.NET to provide server side scripting, COM+ for application component communication, Message Queuing for multithreaded processing, and the Windows Communication Foundation (WCF) for application communication. There are also third party server systems that provide .NET support, including Mono, Base4, TNAPS and cc Devnet Data Access Server.

.NET App Servers

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.

Microsoft IIS Web Server

The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications