Restructuring of Visual Studio Extensions #71
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…no longer be maintained) and created the first cut of the README.
…ir own build script.
…ly). Final piece of work is to test on VS2013.
…o the 'Seeds' solution.
Closed
|
Hey Dave! Looks good for me! Changing to NuGet and refactor the extensions out is logically. Cool thing! I would strongly suggest, that we support Visual Studio 2015! The Microsoft guys take big steps forward. They released Update 5 CTP 2 these days. So release will be soon. I'll create an issue. We should take it into 2.5. |
|
Hi Robin, Thanks for checking this - the nice thing about using Nuget for the extensions is that we can release updates of SharpGL without having to update the extensions, consumers can just update their packages. Good call on extensions for 2015, I'll update the milestone for #77 to be 2.5 |
dwmkerr
added a commit
that referenced
this pull request
Jan 28, 2015
Restructuring of Visual Studio Extensions
This was referenced Jan 28, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Visual Studio Extensions are not part of the core functionality of SharpGL, but add complexity to the build process and maintenance. To simplify things, everything to do with Visual Studio Extensions now sits in:
A detailed description of the structure of this folder, the software needed to build the extensions and how to build the extensions is in the README.md file in the extensions folder.
Other improvements to extensions:
Fixes #42, #56, #68.