Visual Studio Shell (Isolated Mode) Redistributables - visual-studio

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.

Related

Run an executable in WSL from a Visual Studio launch profile

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.

Debugging .NET Core on WSL by launching directly from Visual Studio

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.

Use Visual Studio for custom script language

We are using a commercial software that has its own scripting language with which you can customize the product. It is very tedious to write code in it without any help from an IDE and it has its own compiler.
Is it possible to use Visual Studio and create an environment for me to write scripts in this language and get the help of intellisense and syntax highlightning and other good things you find in an IDE? Ideally I would like to bind a button in VS to launch the external compiler and compile the code so I don't have to switch windows all the time as well.
If this is possible is it a very hard thing to accomplish?
Yes, this is certainly possible. You need to create a Visual Studio Shell add-in with custom language services and text editors. You need to install the appropriate Visual Studio SDK and then you'd continue to:
Create a custom Editor and/or designer
Add a language service
Add Project and Item templates
You're allowed to ship Visual Studio Isolated Shell with your application (license required and there are some limitations) so that your users don't need to have Visual Studio Professional installed.
There are a number of open-source projects that provide a custom editor, language services etc in Visual Studio, these could provide a nice place to research how things are done, next to teh Visual Studio SDK documentation:
PyTools, which is a Visual Studio editor for IronPython
Phalanger, which contains a Visual Studio editor for PHP
PoShTools, a Visual Studio service for PowerShell editing right inside Visual Studio
You'll probably want to dig into MsBuild as well, since Visual Studio will expect you to create a project file if you want to edit a collection of files and compile them. MsBuild could in turn call your own compiler, like it calls csc to compile C# code for example.
Creating Project Types

Visual Studio 2010 configuration

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?

Command line to start visual studio and disable add ins/Extensions for that instance

I am writing a Visual Studio template wizard. And to debug it I have it start a new instance of Visual Studio 2010.
My Visual Studio 2010 takes a good while to start up. I believe that this is due the the add-ins and extensions that I have installed for visual studio.
I would rather not go disable them all (I really like them). So I was hoping there was a way to disable them via the command line.
Just run a clean Visual Studio instance.
Is there a way to do that?
Try safemode
devenv.exe /safemode
which
Starts Visual Studio in safe mode, and loads only the default environment and services, and shipped versions of third-party packages.
See http://msdn.microsoft.com/en-us/library/xee0c8y7.aspx

Resources