Skip to content

Releases: MBulli/SmartCommandlineArgs

v3.3

21 Jul 19:36

Choose a tag to compare

Features:

  • Option to enable/disable the automatic update of the launch profile
  • Themed dialog windows
  • arm64 support for vs2022

Bugfixes:

  • Fixed missing *.args.json file after initial scan for project arguments
  • Fixed crash when reading *.args.json containing multiple items with the same id

v3.2 - Bugfix #1

05 Feb 23:21

Choose a tag to compare

After fixing the scanning of C++ projects in the last release several users experienced very long hangs and even out of memory exceptions on Visual Studio startup. This is because loading the config of every C++ project can take a very long time and for some reason Visual Studio keeps the memory for those configs allocated.

To solve this issue this version introduces a option to configure the scanning behavior for C++ projects. There are three modes to choose from:

  • Ignore C++ projects (behavior before v3.2)
  • Gather args only from startup projects (new default)
  • Gather args from all projects (behavior of v3.2)

This default should serve as a good middle ground between usefulness and performance.

v3.2

04 Dec 22:44

Choose a tag to compare

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

29 Jul 21:35

Choose a tag to compare

v3.0.3.1 Beta Release Pre-release
Pre-release

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

v3.0 - Bugfix #3

03 Apr 21:06

Choose a tag to compare

v3.0 - Bugfix #3 Pre-release
Pre-release

Bugfixes:

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

v3.0 - Bugfix #2

02 Apr 20:38

Choose a tag to compare

v3.0 - Bugfix #2 Pre-release
Pre-release

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

01 Apr 17:16

Choose a tag to compare

v3.0 Pre-release
Pre-release

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)

15 Mar 11:42

Choose a tag to compare

Beta v2.6.0.4 (RC) Pre-release
Pre-release

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

25 Feb 17:18

Choose a tag to compare

Beta v2.6.0.3 Pre-release
Pre-release

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

25 Feb 11:32

Choose a tag to compare

Beta v2.6.0.2 Pre-release
Pre-release

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.