-
Notifications
You must be signed in to change notification settings - Fork 679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ignore or Specify Properties/launchSettings.json setting #3121
Comments
To make sure I understand the request: you would like a launch.json setting to explicitly indicate a launchSettings.json profile, and if specified, environment variables from the lauchSettings profile would trump even launch.json. Do I have that correct? |
Yes.This distinguishes the impact of VS configuration. |
Is this in the pipeline, or is there some other approach that might resolve the following? Working together where some are using VS and others VSCode, we have our local run options defined via various profiles in I'm really missing the ability to be able to specificy |
This is annoying when used in combination with docker-compose. I don't want |
Recognized the behaviour which @MikaelElkiaer described today when opening a vs2019 project in vs code. Colleagues are using launchSettings.json to have env variable sets for different environments & a local debug stack. If ran in VScode, the first profile is used. But I'd also be fine with an Option to fully ignore the launchSettings.json (so I would be able to create the profiles I need myself in launch.json) My current workaround: |
I am in the same world here, have a webpack proxy setup as part of a launchSetting.json profile and want to be fit to debug as part of VSCode with cross team on VS and VS code. Is there any update on this feature |
+1 |
I see omnisharp-vscode ignore Properties/launchSettings.json config.it 's new feture in omnisharp-vscode? |
Have you tried to edit |
@Smoovsky that would not work. That is just going to pass that arg to your app. |
Any news on this? My team is a mixed environment when some people use VS 2019 and others use VSCode + devcontainers, which requires differences in some environment variables. Having the ability to ignore |
This PR updates the debugger to 1.23.17. This includes: * All the bug fixes that went into Visual Studio 17 GA * Updating the debugger to run on .NET 6 RC2 * Enhanced support for launchSettings.json ([dotnet#3121](dotnet#3121)) * Now that most users will not need to download the debugger themselves (it comes pre-packaged in a platform specific), this changes back to the Azure CDN instead of https://download.visualstudio.microsoft.com This also updates `gulp updatePackageDependencies` to support updating packages when the primary URL just has a simple version number.
This PR updates the debugger to 1.23.17. This includes: * All the bug fixes that went into Visual Studio 17 GA * Updating the debugger to run on .NET 6 RC2 * Enhanced support for launchSettings.json ([dotnet#3121](dotnet#3121)) * Now that most users will not need to download the debugger themselves (it comes pre-packaged in a platform specific), this changes back to the Azure CDN instead of https://download.visualstudio.microsoft.com This also updates `gulp updatePackageDependencies` to support updating packages when the primary URL just has a simple version number.
This PR updates the debugger to 1.23.17. This includes: * All the bug fixes that went into Visual Studio 17 GA * Updating the debugger to run on .NET 6 RC2 * Enhanced support for launchSettings.json ([#3121](#3121)) * Now that most users will not need to download the debugger themselves (it comes pre-packaged in a platform specific .vsix), this changes back to the Azure CDN instead of https://download.visualstudio.microsoft.com This also updates `gulp updatePackageDependencies` to support updating packages when the primary URL just has a simple version number.
Environment data
dotnet --info
output:VS Code version:
C# Extension version:
Steps to reproduce
.vscode/launch.json‘s setting below:
my host project Properties/launchSettings.json‘s setting below:
Expected behavior
Project uses environment variables to change application configuration.when I start debug app, I hope the Properties/launchSettings.json setting can't not be use, because my colleagues use multiple configurations to distinguish between local and test environments on VS2017. there are two project setting in the profiles node. I can ignore Properties/launchSettings.json setting or Specify which configuration to use?
Actual behavior
Properties/launchSettings.json's node
SplitPackage.Web.Host_local
is applied.The text was updated successfully, but these errors were encountered: