You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Activity
PureKrome commentedon Apr 2, 2014
So how do you create one nuget package that supports mvc 3/4/5 or just 4/5?
phillip-haydon commentedon Apr 2, 2014
Talking about the namespace/assembly name, not the package name.
The Assembly says
.MVC3instead of.MVCPureKrome commentedon Apr 2, 2014
ooooooOOOOOHHhhhhhhhh..
👍 👍
PureKrome commentedon Jun 8, 2014
Ok. so the namespace for the assemblies should be
SimpleAuthentication.Mvc?And for version 2.0, we should only target v5 IMO.
leave 3/4 support for v1 (when that gets released) ?
phillip-haydon commentedon Jun 8, 2014
Sure, but we should version the V5 project, just need to make the assembly un-versioned.