Split MVC project into separate MVC3 and MVC4 projects #2
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
…y.MVC4) and a new one in Chirpy.MVC3. Made changes to MVC3 project to support MVC3, and remove Razor / Web Pages 2 syntax (such as @Html.DisplayNameFor). MVC3 project should now work in a standard installation of MVC3. Two solution files now exist, one for each of the two flavors of MVC.
dotnetcurry
added a commit
that referenced
this pull request
May 10, 2012
Split MVC project into separate MVC3 and MVC4 projects
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.
As well as the existing MVC project (now in renamed folder Chirpy.MVC4), I have implemented an MVC3 project in the folder Chirpy.MVC3.
Made changes to MVC3 project to support MVC3, and remove Razor / Web Pages 2 syntax (such as
@Html.DisplayNameFor) so that the MVC3 project should now work in a standard installation of MVC3.Two solution files now exist, one for each of the two flavors of MVC.
Note: if you decide not to accept this pull request (I know you've been working on this problem yourself), then at least consider adding the change to
.gitignorewhich helps exclude Visual Studio user specific files, and prevents NuGet packages from being accidentally committed.