Skip to main content

Remote debug of an application that is on Windows Azure using VPN

One cool thing that I like when working with Azure is the way how you can do remotely debug. In a classic system is not very easily to do something like this. Azure facilitate this using Visual Studio and attached to process mechanism.
Theoretically you should not need to do remote debug, but in practice you need to do this from time to time.
To be able to do something like this you will need to create a virtual network. Using the virtual network you will be able to establish a VPN connection between the cloud machines (network) and you. Using this feature you can do more complicated stuff, for example integrate your cloud network with the one from your premise, but we don’t needs something like this if we want remote debugging.
Creating the virtual network is pretty simple. You need to go to New-> Network -> Virtual Network and create a new one. For this purpose you don’t need to make any kind of custom configurations. Don’t forget to select your affinity group – this should represent the cloud machines that you want to access remotely using VPN.
After this step you should create a custom certificate on your machine and upload to the certificates tab of your private network.
Now we are ready for the last step. Download the VPN configuration from the dashboard tab and run it. From now, you will be connect to your private network using the VPN connection. Based on the machine name you can connect to any machine or …
you can do remote debug of your application very easily. Using Visual Studio you can attach to any process of your machines and do real time debugging.
Until now I didn’t needed this feature, but it is pretty cool how easily you can do something like this. No custom configuration, no custom tools, no IT department from the on premise network.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too