Possible to set settings default to all project?

[R3uan3]

-Edited-
Is it possible to save default settings to any project?

[3F]

Hello, Regarding to the last your edit, I recommend use vsCommandEvent edition which was based on vsSolutionBuildEvent. There are two types of settings where one of this is a common or a global which affects any VS IDE instances. Means configuration for any events/actions between everything in different instances of Visual Studio, including default options, etc. Pure vsSolutionBuildEvent works only for specific solution and its projects, but you can also try to distribute somehow the .vssbe and .vssbe.user files to apply automatically settings for a new solution too n. I may still be very slow to respond due to many reasons beyond my control, sorry.

…

On 11.10.2022 7:27, R3uan3 wrote: Message ID: ***@***.***>

[3F]

Ah yes, regarding to the dumping of the output, SobaScript provides related component: https://3F.github.io/web.vsSBE/doc/Scripts/SBE-Scripts/Components/OWPComponent/ Or try EnvDTE accessing: https://3F.github.io/web.vsCE/doc/Examples/Overriding/#how-to etc. On 11.10.2022 15:40, Denis Kuzmin wrote:

[R3uan3]

Hello, thank you for such an amazing extension!
I tried vsCommandEvent like this:

But I didn't understand how to save it defaults to all instances.

I'm currently working on a C++ project, does the Processing Mode C# only work if I'm compiling a C# project?

[3F]

"Common context" header already indicates where you are. You can click on it to switch between, or find more using gear menu. Note any configured and activated events/actions should be applied immediately after Apply button. Thus, try to enable debug mode if something does not work as expected. \> "I'm currently working on a C++ project" Any modes can be applied for everything including an unmanaged C++ projects in solution etc. But I recommend to start with Script mode and supported SobaScript + E-MSbuild script engines. Note C# scripts can be either compiled once as module or interpreted as script at runtime. I'm sorry it's hard for me now to help someone with specific solutions as before, but you can start with the documentation (for both plugins). I know they're not very good (and moreover some parts are too old) but they're better than nothing

…

On 11.10.2022 21:13, R3uan3 wrote: Hello, thank you for such an amazing extension! I tried |vsCommandEvent| like this: parsecd_2022-10-11_15-04-25 <https://user-images.githubusercontent.com/103058225/195166881-efd5ab0e-0f50-4624-9f9c-4c38f081fda1.png> But I didn't understand how to save it defaults to all instances. I'm currently working on a |C++| project, does the |Processing Mode| |C#| only work if I'm compiling a |C#| project? Message ID: ***@***.***>