You can use 
               		Enterprise Developer installed locally to debug a .NET COBOL application running on a remote Windows machine. 
               	 
            
 
            	 
            Note: The remote application must run on Windows. 
               	 
            
 
            	 
            
               To prepare for debugging
 
               		 
               		
               Ensure that you have the following installed on your local machine: 
                  		
               
 
               		
                
                  		  
                  - Enterprise Developer 
                     		  
                  
- The application's project file or symbols (either .idy or .pdb). You do not need these files if you are going to use 
                     			 Attach to Process. 
                     		  
                  
- Establish a connection between your local machine and the remote one - 
                     			 click here for instructions. 
                     		  
                  
Ensure that you have the following on the remote Windows machine: 
                  		
               
 
               		
                
               	 
              
            	 
            
               To debug a .NET COBOL application remotely
 
               		 
               		
               These are the instructions to debug an application that runs on a remote machine: 
                  		
               
 
               		
                
                  		  
                  - On your local machine, start Visual Studio. 
                     		  
                  
- Either create a new .NET COBOL project or open the one that was used to create the application you want to debug. 
                     		  
                  
- Configure your project for debugging: 
                     			 
                      
                        				
                        - Navigate to the project's properties and click the 
                           				  Debug tab. 
                           				
                        
- Set 
                           				  Launch to 
                           				  Project. 
                           				
                        
- Check 
                           				  Use remote machine and specify the name (or the IP) and the port number of the remote machine as used by the Remote Debugger - such as 
                           				  machinename:4022. 
                           				
                        
- Check 
                           				  Disable Windows authentication for remote debugging if you want to avoid having to provide credentials when connecting to the remote debugger. You need to ensure that the remote
                           debugger is also configured to run without Windows Authentication. This can be useful in scenarios where it is not possible
                           to set up the required credentials. 
                           				  
                           Warning: Enabling this option in the remote debugger makes your remote machine accessible to other users on the network. 
                              				  
                            
 
- On the remote machine, create a folder structure to match the path to the 
                     			 bin\Debug folder of the application on your local machine. 
                     		  
                  
- Copy the application's binary files to that folder. 
                     		  
                  
- Start Microsoft's Remote Debugger application on the remote machine - 
                     			 click here for instructions. 
                     		  
                  
- Start debugging in Visual Studio on your local machine.