What is the recommended approach where you have a NuGet package that targets say MVC3 and then MVC4 is released?
If I understand correctly, leaving the package with a reference to MVC3 will allow both MVC3 and MVC4 users to use the package, as long as MVC4 users keep the binding redirects in place. This does mean that I cannot take advantage of any new
MVC4 features but other than that, are there any more negatives with regard to relying on binding redirects?
If I change the package to reference MVC4 , MVC3 users will no longer be able to use the latest version of the package. Also, NuGet will suggest that anyone with an older version upgrade which will break their project if they are still using MVC3.
Would having two separate packages (one for MVC3 and one for MVC4) make any sense? This at least allows users to install the older version more easily than using the version argument with install-package.