-
Notifications
You must be signed in to change notification settings - Fork 82
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
MVC Support #138
Comments
So how do you create one nuget package that supports mvc 3/4/5 or just 4/5? |
Talking about the namespace/assembly name, not the package name. The Assembly says |
ooooooOOOOOHHhhhhhhhh.. 👍 👍 |
Ok. so the namespace for the assemblies should be
And for version 2.0, we should only target v5 IMO. leave 3/4 support for v1 (when that gets released) ? |
Sure, but we should version the V5 project, just need to make the assembly un-versioned. |
First of all we need to rename the assemblies because the naming is retarded.
The output assemblies and namespaces should be identical across all versions of MVC regardless of the target framework.
Having said that, which MVC versions are we going to support?
3, 4, and 5?
At the moment we only officially support 3/4, most people have moved away from 3 so is it worth still trying to support that? Should we only support 4/5?
Those who are on 3, are probably still targeting .NET 3.5, i would assume.
The text was updated successfully, but these errors were encountered: