Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We’ve got a couple of projects here at work. One uses MVC4 Beta and the other MVC4 RC.
I have MVC4 RC Installed on my local machine.
I need to be able to build both projects locally however the project using MVC4 Beta makes reference to System.Web.Http.SelfHost which has at least one method in beta that is not longer in RC.
How can I force the project using MVC4 Beta to use the dll we require rather than the MVC4 RC version in the GAC?
You’re playing with fire doing this but you would use a binding redirect in your web.config to specify the full version number you want to use in your web.config. The RC version and the Beta (depending which) Version have different version tags. YOu can specify which assembly to use that way.
http://msdn.microsoft.com/en-us/library/eftw1fys.aspx
HOWEVER, this is dangerous using the Beta version and I would even dare say dangerous using the RC version in a production environment. I hope that this is a QA environment and you are planning to wait for RTM to go to production. Beta code should never be used in a production environment, read the EULA you agreed to when installing 😉