-
Notifications
You must be signed in to change notification settings - Fork 98
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
Has the VSProjectSystem been abandoned? #372
Comments
I would appreciate any feedback. Thanks for opening... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Everything seems to be broken into pieces, especially documentation and tooling.
It took me several days to make sense of all the different information available at different places, which has almost been like a forensic investigation: Finding out which information has been written at which time, which parts are outdated, which are still valid, which different ways exist for building a project system and how they relate together, which information applies to which way, why the official VSSDK documentation does not mention the VSPS nor tooling for it, but gives just a minimal description for the old way (MPF), why this repo is called VSPS but the the dotnet/project system calls it CPS while the docs here are talking about CPS Core and CPS VS, why the new AppDesigner is part of the C#/VB/F# project system rather than being a common component available to custom project systems (to provide consistent appearance in VS for all project types), how SDK projects are related to the CPS and whether they can or should be used together with a custom CPS-based project system and how, or whether they can or should be used only with dotnet/project-system, questions questions questions....for some of which it has been quite a task to find the answers.
And finally, the most important question: Why is everything about it, so badly outdated?
(I have created a PR to update the samples here)
(I had to patch it to get it working with VS 2022)
Is this a dead end or still the way to go?
The text was updated successfully, but these errors were encountered: