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

Migrate to the Common Project System #90

Open
sharwell opened this issue May 12, 2015 · 6 comments
Open

Migrate to the Common Project System #90

sharwell opened this issue May 12, 2015 · 6 comments

Comments

@sharwell
Copy link
Contributor

The Common Project System is the de-facto standard way to add support for new project types in recent versions of Visual Studio. With #83 moving us exclusively to Visual Studio 2013+, it should¹ be the cleanest and easiest way to provide a great project system.

¹ Change this to "will" once we test it out! 😉

@EWSoftware
Copy link
Owner

Just to clarify, by "Common Project System", are you referring to your MPFProj10 from NuGet that's an improved version of what's currently in the project or is this something else? If something else, can you provide some references? I can't find anything.

@sharwell
Copy link
Contributor Author

Documentation is virtually non-existent right now, but it's coming.

@EWSoftware
Copy link
Owner

So, not MPFProj10?

@sharwell
Copy link
Contributor Author

That is correct. CPS was originally created for the new C++ project system in Visual Studio 2010, and over time expanded to support a wider range of scenarios internal to Microsoft. Starting with Visual Studio 2015, they are publicly documenting the system. However, an older version of the assemblies is still included in Visual Studio 2013 (stable but not documented), so I plan to craft a solution for SHFB that works in both environments.

@sharwell
Copy link
Contributor Author

The documentation for the new project system is being added here:
https://github.com/Microsoft/VSProjectSystem

I'll give a better overview of the work involved with migrating SHFB to use this after a more extensive review and experimentation.

@EWSoftware
Copy link
Owner

Looks interesting though not yet finished. I'm doubtful about using it yet until the API stabilizes simply because I don't want to maintain separate versions and/or installers for each version of Visual Studio until it does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants