Importing .vsconfig shows an error #60794
Comments
dotnet-issue-labeler
bot
added
the
untriaged
|
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. |
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsDescriptionThe workflow steps for the runtime says to import the When I tried this with VS 2022 Preview 5 and the
Reproduction StepsImport .vsconfig in the Visual Studio 2022 Installer Expected behaviorIt imports the requirements specified in the .vsconfig file Actual behaviorIs shows the message in the attached screenshot Regression?I don't know. I vaguely recall seeing this a while ago (earlier in the .net 6 lifecycle) Known WorkaroundsNo response ConfigurationNo response Other informationNo response
|
|
Thanks for pointing this out @SteveDunn . This file tends to get outdated. It's not the true requirements, but an export from a machine that satisfies the requirements. The second two listed aren't required. The first one we do require but it can be a newer version eg 4.7.2. If you ignore those (or remove from the file) and add 4.7.2 you should then have all that's needed (and more). If you like you could then export an updated file and offer a quick PR to freshen it in this repo. |
|
Thanks Dan. Will do that and create a PR later. |
ghost
added
the
in-pr
These packages are unused as described in #60794 Co-authored-by: Santiago Fernandez Madero <[email protected]>
ghost
removed
the
in-pr
ghost
locked as resolved and limited conversation to collaborators
Description
The workflow steps for the runtime says to import the
.vsconfigfile into the Visual Studio Installer.When I tried this with VS 2022 Preview 5 and the
dotnet/runtimerepo as of 25th October 2021, it shows an error:Reproduction Steps
Import .vsconfig in the Visual Studio 2022 Installer
Expected behavior
It imports the requirements specified in the .vsconfig file
Actual behavior
Is shows the message in the attached screenshot
Regression?
I don't know. I vaguely recall seeing this a while ago (earlier in the .net 6 lifecycle)
Known Workarounds
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: