In Visual Studio in Windows I can create a launchSettings.json profile which starts up an executable I specify and then attaches to it. Is it possible to do the same with an executable in WSL?
I'm writing an extension to a Linux program. The extension is a .Net 6 class library, so in order to debug it I need to start up the Linux program and then immediately attach. I could start up the program manually and then attach to the process from Visual Studio, but the extension loads first thing and I can't hop over to Visual Studio and attach fast enough to catch it.
I've found instructions for debugging .Net ASP and console apps in WSL from Visual Studio, but those instructions always assume that the project I'm debugging is itself executable.
Related
Everything I've read about debugging C# programs on Windows Subsystem for Linux either uses Visual Studio Code, or tells you to launch the program through bash then attach the debugger to the process.
This method works, but it's slow to initiate every time I'd like to debug a change. Is there a way to setup Visual Studio to start remote debugging from the IDE similar to how it's done in C++?
You can debug the .Net Core application on WSL2 from Visual Studio 2019 now.
You need to install/update to version Visual Studio 2019 v16.9.1.
There are the Prerequisites, You can refer to Start debugging with WSL 2.
Hello I have created a DLL file using visual C++ 2010, that runs a C script that i have written.
I have then created a user interface using visual C# 2010 and linked everything together.
On my machine the resulting exe application runs perfectly.
However when i try to put the folder, containing BOTH the exe and the dll, on other computers.. it runs on some computers, but on others it does not.
the error i receive has to do with "Cant find dll file or assembly".
All computers have windows 7 64bit installed.
My question is: Is there a requirement for the application to run? (files or something that should be installed on all machines???)
I have noticed the following (after alot of looking) that:
the computers that run the application HAVE visual studio 2010 installed
the computers that do not run the application DO NOT have visual studio 2010 but have visual studio 2008 installed..
all computers have .NET framework 4.5 installed.
Do you think the visual studio has anything to do with this?!!? isnt the point having a stand alone application is to make the app run on any machine?
Is there a way to fix it so that the app will run on any computer regarding having visual installed or not?
thank you all..
You can use Dependency Walker to check what dll the program can't find.
Just load the .exe into the program.
You might also find that you will need to install the Visual Studio 2010 Redistributable on those computers that you are deploying to.
I have a Windows 32-bit project designed in Visual Studio 2010 using C++. When I build and compile it on one computer, I get the GUI and the project works. However, on a different computer it only shows me a command prompt and then exits. What configuration changes do I need to make to see the GUI on this computer?
What I'd really like to do is debug an executable using the Visual Studio debugger. It comes with an Attach to Process feature. Unfortunately, the target executable only lasts for a short period- much too short for me to launch the executable and then navigate through Visual Studio and attach to it. How can I command Visual Studio to launch the executable and immediately attach the debugger?
AttachToLazy VS add-in can wait for a process to start and then attach to it.
This add-in was written for VS2008 and it looks like some people were able to get it to work with 2010 by adjusting some of the properties (info under the Discussions tab).
I want to use the Isolated Shell as a front-end for a custom debugger.
If I understand correctly, the Visual Studio Debug Package implements the 'User Interface Parts' of the Visual Studio Debugger system, that is, among other things, all the debugger windows (stack, watch, breakpoints etc).
Is the VS Debug Package a part of the Isolated Mode redistributable? In other words, can I reuse the existing Visual Studio debug-related windows in my Isolated Shell application?
SIS
Some of the windows may be disabled in the default config options in the template, but the debug-related windows are available.