Skip to content
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

[BUG/FEATURE REQUEST] MSIX packaging extension for Azure DevOps release - Configuration combo should not be restricted to 2 values #626

Open
elvince opened this issue Apr 23, 2024 · 2 comments
Labels
Needs-Triage Issue needs to be triaged by a member of the core team

Comments

@elvince
Copy link

elvince commented Apr 23, 2024

Project
MSIX SDK or Win7Msix

Describe the bug
On Azure DevOps extension, the configuration option had only 2 values 'Debug' and 'Release'.

To Reproduce
Install the devops extenstion, create a package task

Expected behavior
Configuration should allow to set any value. Configuration can't be standard accross company and now, you tend to have development/staging/production instead of Debug/Release as default configuration

Is this something you can fix?

Thanks,

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue needs to be triaged by a member of the core team label Apr 23, 2024
@psycorp
Copy link

psycorp commented Jan 6, 2025

Can you expand on why you need more than Debug/Release?

How many different build types are you producing?

Configuration is a Visual Studio variable that has historically had only the two main options.
https://learn.microsoft.com/en-us/visualstudio/ide/understanding-build-configurations?view=vs-2022

@elvince
Copy link
Author

elvince commented Jan 7, 2025

Hi,

I need one configuration per environment. like, dev, staging, production.
On previous company they were using, dev, uat, buat, production.
On .net core, we are talking with dev/staging/production whereas on .net framework it used to be debug/xxx/release.

In all case, configuration is something that you can create and change in any project. As a consequence, we should be able to set out value in the task that match our configurations setup and not a "closed list".

As you point out, historically you have 2 options.
From the doc you mentionned: You can create your own build configurations at the solution and project level. so how do you deal with this in this tasks?

thanks,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Triage Issue needs to be triaged by a member of the core team
Projects
None yet
Development

No branches or pull requests

2 participants