May 20, 2012 at 6:50 PM
Edited May 20, 2012 at 6:51 PM
I've built a NuGet Package for MVC 3 applications. Now with MVC 4 some of the views break because HTML Helpers have an additional parameter necessary. It also needs a new assembly dependency section for MVC 4 added to the web.config in order
Is there a way of creating a NuGet package without PowerShell, that can detect which version of MVC is installed in the host application, so I can add the correct versions of the Views and the web.config.transform?
I'm hoping there is some solution similar to detecting which .Net version by simply putting files in that .Net version folder.
Is this possible and if so, what is the NuGet configuration steps to get this to work? I've looked at the docs and there doesn't seem to be information on how to do this.
If not, then is it possible via PowerShell? I have never written anything in PowerShell and if this is the only way to handle this issue, I could use a push in the right direction.
Any help with this is appreciated.