-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
Visual Studio 2022 Support #99
Comments
This would be a great addition - I didn't realise that File Nesting in 2022 is only supported on ASP.NET Web projects. |
@madskristensen any plans to port this extension to VS2022? |
it would be great if someone could at least extract the manual nesting feature into a new extension for VS 2022. Hopefully that would be quick. I wish I had time to do it! |
Even if there is file nesting for Core projects and automatic file nesting, I would appreciate if there would be some manual nestung feature like this extension in VS2022 because I have needs where automatic file nesting is not working in non Core project. |
In VS2022 adding a In projects where file nesting is not enabled by default, we've had luck adding this to the proj file: <ItemGroup>
<ProjectCapability Include="ConfigurableFileNesting" />
<ProjectCapability Include="ConfigurableFileNestingFeatureEnabled" />
</ItemGroup> |
I really would appreciate to have a choice in the GUI as with this extension to nest files, instead of adding and editing new files. I can do that in .csproj file also, but I would like the comfort of GUI. |
Installed product versions
Description
Make the extension available in Visual Studio 2022.
Steps to recreate
Current behavior
Message that it is already installed to all applicable products appears even though it is not installed in Visual Studio 2022.
It is also not listed in Online Extensions in Manage Extensions Visual Studio 2022.
Expected behavior
Installs and works in Visual Studio 2022.
Note: Sorry for the all the extra details. I probably could have stopped with the title on this one.
The text was updated successfully, but these errors were encountered: