-
Notifications
You must be signed in to change notification settings - Fork 21
Support for MVC 5 #11
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
Comments
In order to help me prioritise this - have you tried binding redirects (e.g. If it works then this is way lower priority for me, but it it doesn't work I'm happy to get something out quicker in the next few weeks... |
Add-BindingRedirect doesn't add the correct binding. But you can do it by hand and it does work:
|
I want to add that in the case that you are using an empty test project (as opposed to a scaffolded one) and you bring down the package - you will need to update the outdated ASP package dependencies by using the
Failure to do this will subject you to a compile-time error as soon as you reference the testee project ;-p |
@byteblast as part of cleaning up the project I think we should add a .mvc5 and .mvc4 package. and make the non-.mvc* package have a dependency on the latest mvc package. Thoughts? I've got an idea for how to easily make the .mvc* projects work in a future proof way too... |
Sounds good mate. On 5 September 2014 05:14, Robert Moore [email protected] wrote:
|
@Beton As per the latest pull request there is now support for MVC 5. See the readme for more information. |
cc @mwhelan |
Awesome! Thanks. Sent from my iPad
|
As title says. Would be nice to have a DLL compiled with latest Framework version.
The text was updated successfully, but these errors were encountered: