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

dotnet new sln should be consistent with VS for new solutions and have only Debug and Release configurations for Any CPU as the default.... #2980

Closed
StingyJack opened this issue Mar 28, 2021 · 1 comment · Fixed by #3205
Assignees
Labels
area: template-content The issue is related to content of template packages managed in this repo (/template_feed) breaking-change Things that should be mentioned as breaking change in release notes. good first issue easy issue, good for first-time contribution to the repo triaged The issue was evaluated by the triage team, placed on correct area, next action defined.
Milestone

Comments

@StingyJack
Copy link

... or via some command switch (-vsdefault?). The projects I'm adding use the VS defaults, there is no need for any x86 or x64 platforms. If I dont remove the x86 and x64 platform records prior to opening the solution in VS, VS may add permutations for them to all of the projects in the solution. I dont want to do the former, but I really dont want to have to clean up the latter.

This is not the same need as this issue, which is far more complex and wants a more complete management of build configurations and platforms.

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@marcpopMSFT marcpopMSFT self-assigned this Mar 31, 2021
@marcpopMSFT marcpopMSFT transferred this issue from dotnet/sdk Mar 31, 2021
@marcpopMSFT marcpopMSFT removed their assignment Mar 31, 2021
@bekir-ozturk bekir-ozturk added need-pm-discussion Need agreement from PM that the issue aligns to targeted stories for any of the next 2 releases triaged The issue was evaluated by the triage team, placed on correct area, next action defined. labels Apr 6, 2021
@DavidKarlas DavidKarlas added good first issue easy issue, good for first-time contribution to the repo and removed need-pm-discussion Need agreement from PM that the issue aligns to targeted stories for any of the next 2 releases labels Apr 6, 2021
@DavidKarlas DavidKarlas added this to the April Sprint milestone Apr 6, 2021
@DavidKarlas DavidKarlas added the breaking-change Things that should be mentioned as breaking change in release notes. label Apr 6, 2021
@vlada-shubina vlada-shubina added the area: template-content The issue is related to content of template packages managed in this repo (/template_feed) label Apr 21, 2021
vlada-shubina added a commit to vlada-shubina/templating that referenced this issue May 25, 2021
vlada-shubina added a commit that referenced this issue May 26, 2021
GangWang01 pushed a commit to GangWang01/sdk that referenced this issue Jun 7, 2022
…4, Release|x86 configurations from sln template
GangWang01 pushed a commit to GangWang01/sdk that referenced this issue Jun 21, 2022
…4, Release|x86 configurations from sln template
GangWang01 pushed a commit to GangWang01/sdk that referenced this issue Jul 11, 2022
…4, Release|x86 configurations from sln template
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: template-content The issue is related to content of template packages managed in this repo (/template_feed) breaking-change Things that should be mentioned as breaking change in release notes. good first issue easy issue, good for first-time contribution to the repo triaged The issue was evaluated by the triage team, placed on correct area, next action defined.
Projects
None yet
5 participants