v3.2

Due to some major bugs, we had to roll back v3.0 by rereleasing v2.6 as v3.1. This was necessary because of the missing option to unpublish a specific version of an extension on the Visual Studio Marketplace.

This release is basically a rerelease of v3.0 with some bugfixes.

Features:

• Working Directory/Launch Application Management: You can now manage the working directory and launch application the same way you can manage the Environment variables, which was added in the last release. (Thanks to belkiss #98 and abizeauMaxon #162)
• Show active Entries: Inactive Items can now be grayed out. An Item is considered inactive is one of the following is true:
  • It is not checked.
  • It is part of a group which has conditions that are not met (like configuration or platform).
  • The setting to manage the type of items is disabled (like Manage Environment Variables)
• Disable Extension: The extension is now disabled by default and only enables itself if it finds a *.args.json file or an entry in the *.suo file. When disabled the extension can be enabled by clicking the button in the extension window. This enables the extension for the current solution, with a flag saved to the *.suo file. If this behavior is not desired it can be modified in the Options with one of four modes:
  • Enable if a *.arg.json file or an entry in the *.suo file is found (this is the default)
  • Enable if a *.arg.json file is found
  • Always ask for new Solutions
  • Enable by default (old behavior)
• Auto Update: The parameters inside the active project configuration are now updated whenever they are modified in the extension window.
• Better support for generated Projects: The saved CLI-Arguments are now also associated with a project based on the name not only the project GUID. This helps to keep the arguments even if the GUID changes which often happens when projects/solutions are generated. #170

Bugfixes:

• Settings wiped: Fixed a bug that wiped the settings after restarting Visual Studio.
• Load JSON from Custom Path: Fixed a bug where the custom JSON path was ignored for loading.
• Start with "Step Into": Fixed a bug where the configuration was not updated when using "Step Into" to launch an application.
• Apply Default Checked correctly: "Default Checked" will now be applied when a item is first loaded. (In other words when they are not found in the *.suo file.)
• Microsoft.Bcl.AsyncInterfaces not found: Fixed crash due to missing Microsoft.Bcl.AsyncInterfaces assembly.
• GetDialogPage crash: Fixed crash due to call of GetDialogPage on non UI thread.
• Microsoft.VisualStudio.ProjectSystem.Managed not found: Fixed crash due to missing Microsoft.VisualStudio.ProjectSystem.Managed assembly.

v3.0.3.1 Beta Release

This is a beta release to test the fix for issue #170.

v3.0 - Bugfix #3

Bugfixes:

• Microsoft.VisualStudio.ProjectSystem.Managed not found: Fixed crash due to missing Microsoft.VisualStudio.ProjectSystem.Managed assembly.

v3.0 - Bugfix #2

Bugfixes:

• Microsoft.Bcl.AsyncInterfaces not found: Fixed crash due to missing Microsoft.Bcl.AsyncInterfaces assembly.
• GetDialogPage crash: Fixed crash due to call of GetDialogPage on non UI thread.

v3.0

With this release we reorganized a lot of the code for better maintainability and testability.

Features:

• Working Directory/Launch Application Management: You can now manage the working directory and launch application the same way you can manage the Environment variables, which was added in the last release. (Thanks to belkiss #98 and abizeauMaxon #162)
• Show active Entries: Inactive Items can now be grayed out. An Item is considered inactive is one of the following is true:
  • It is not checked.
  • It is part of a group which has conditions that are not met (like configuration or platform).
  • The setting to manage the type of items is disabled (like Manage Environment Variables)
• Disable Extension: The extension is now disabled by default and only enables itself if it finds a *.args.json file or an entry in the *.suo file. When disabled the extension can be enabled by clicking the button in the extension window. This enables the extension for the current solution, with a flag saved to the *.suo file. If this behavior is not desired it can be modified in the Options with one of four modes:
  • Enable if a *.arg.json file or an entry in the *.suo file is found (this is the default)
  • Enable if a *.arg.json file is found
  • Always ask for new Solutions
  • Enable by default (old behavior)
• Auto Update: The parameters inside the active project configuration are now updated whenever they are modified in the extension window.

Bugfixes:

• Settings wiped: Fixed a bug that wiped the settings after restarting Visual Studio.
• Load JSON from Custom Path: Fixed a bug where the custom JSON path was ignored for loading.
• Start with "Step Into": Fixed a bug where the configuration was not updated when using "Step Into" to launch an application.
• Apply Default Checked correctly: "Default Checked" will now be applied when a item is first loaded. (In other words when they are not found in the *.suo file.)

Beta v2.6.0.4 (RC)

With this release I reorganized a lot of the code.

Features:

• Working Directory/Launch Application Management: You can now manage the working directory and launch application the same way you can manage the Environment variables, which was added in the last release. (Thanks to belkiss #98 and abizeauMaxon #162)
• Show active Entries: Inactive Items can now be grayed out. An Item is considered inactive is one of the following is true:
  • It is not checked.
  • It is part of a group which has conditions that are not met (like configuration or platform).
  • The setting to manage the type of items is disabled (like Manage Environment Variables)
• Disable Extension: The extension is now disabled by default and only enables itself if it finds a *.args.json file or an entry in the *.suo file. When disabled the extension can be enabled by clicking the button in the extension window. This enables the extension for the current solution, with a flag saved to the *.suo file. If this behavior is not desired it can be modified in the Options with one of four modes:
  • Enable if a *.arg.json file or an entry in the *.suo file is found (this is the default)
  • Enable if a *.arg.json file is found
  • Always ask for new Solutions
  • Enable by default (old behavior)
• Auto Update: The parameters inside the active project configuration are now updated whenever they are modified in the extension window.

Bugfixes:

• Settings wiped: Fixed a bug that wiped the settings after restarting Visual Studio.
• Load JSON from Custom Path: Fixed a bug where the custom JSON path was ignored for loading.
• Start with "Step Into": Fixed a bug where the configuration was not updated when using "Step Into" to launch an application.
• Apply Default Checked correctly: "Default Checked" will now be applied when a item is first loaded. (In other words when they are not found in the *.suo file.)
• Error in VS2017: Fixed a crash when starting the extension in Visual Studio 2017

Beta v2.6.0.3

With this release I reorganized a lot of the code.

Features:

• Working Directory/Launch Application Management: You can now manage the working directory and launch application the same way you can manage the Environment variables, which was added in the last release. (Thanks to belkiss #98 and abizeauMaxon #162)
• Show active Entries: Inactive Items can now be grayed out. An Item is considered inactive is one of the following is true:
  • It is not checked.
  • It is part of a group which has conditions that are not met (like configuration or platform).
  • The setting to manage the type of items is disabled (like Manage Environment Variables)
• Disable Extension: The extension is now disabled by default and only enables itself if it finds a *.args.json file or an entry in the *.suo file. When disabled the extension can be enabled by clicking the button in the extension window. This enables the extension for the current solution, with a flag saved to the *.suo file. If this behavior is not desired it can be modified in the Options with one of four modes:
  • Enable if a *.arg.json file or an entry in the *.suo file is found (this is the default)
  • Enable if a *.arg.json file is found
  • Always ask for new Solutions
  • Enable by default (old behavior)
• Auto Update: The parameters inside the active project configuration are now updated whenever they are modified in the extension window.

Bugfixes:

• Settings wiped: Fixed a bug that wiped the settings after restarting Visual Studio.
• Load JSON from Custom Path: Fixed a bug where the custom JSON path was ignored for loading.
• Start with "Step Into": Fixed a bug where the configuration was not updated when using "Step Into" to launch an application.

Beta v2.6.0.2

With this release I reorganized a lot of the code.

Features:

• Working Directory Management: You can now manage the working directory the same way you can manage the Environment variables, which was added in the last release. (Thanks to belkiss)
• Disable Extension: The extension is now disabled by default and only enables itself if it finds a *.args.json file or an entry in the *.suo file. When disabled the extension can be enabled by clicking the button in the extension window. This enables the extension for the current solution, with a flag saved to the *.suo file. If this behavior is not desired it can be modified in the Options with one of four modes:
  • Enable if a *.arg.json file or an entry in the *.suo file is found (this is the default)
  • Enable if a *.arg.json file is found
  • Always ask for new Solutions
  • Enable by default (old behavior)

Bugfixes:

• Settings wiped: Fixed a bug that wiped the settings after restarting Visual Studio.

v2.6

Features

• Environment Variable Management: Users can now manage environment variables directly from the extension. This feature is disabled by default, but can be enabled globally for the current Visual Studio installation through the options panel or on a per-solution basis in the solution-specific settings. (#136)
  • To add environment variables, click the small arrow next to the "Add" button in the toolbar.
  • Environment variables are marked with an "ENV" tag.
  • To be valid, environment variables must contain an "=".
  • Invalid variables are highlighted with a red border.
• Configurable Extension Scope: Users now have the ability to specify whether the extension should be in charge of setting environment variables, command-line arguments, or both, by enabling or disabling these options as needed.
• Custom ".args.json" File Location: You can now specify a custom location for the ".args.json" file in the solution-specific settings. This option requires "Use Solution Dir" to be enabled in order to save a single JSON file containing all arguments. (Thanks to orbikm #146)
• Improved "Open/Reveal File/Directory" Functionality: This feature now supports macros and relative paths, with the base path configurable as either the project directory or the target directory (e.g., where the compiled binary is located) in the Options.
• Default Setting Values: Unset settings now display their default values for easier reference. (Thanks to mitchcapper #150)
• Delimiter, Prefix, and Postfix: It is now possible to customize the delimiter as well as a pre- and postfix for groups. (The pre- and postfix isn't fully fleshed out yet. They can be configured in the same dialog as the custom delimiter.)

Bug Fixes

• "Show All Projects" Toggle Button: The state of the "Show All Projects" toggle button is now correctly saved across sessions.

v2.5

Important Notice for Users of VS2019 and VS2017

If you have previously downloaded and installed version 2.4.x for VS2019 or any version before 2.4.0 for VS2017, please note that you must first uninstall this version before installing the latest version.

To ensure that all users receive automatic updates, the VSIX ID of the latest version has been changed. As a result, Visual Studio treats version 2.5.0 and 2.4.x (or any version before 2.4.0 for VS2017) as separate extensions. If you install version 2.5.0 without first uninstalling the previous version, both versions may be installed, and the consequences of this are unknown.

---

Features

• Added a option to the context menu to open/reveal files and folders. (#128)