We have moved to GitHub Issues
You are viewing the read-only archive of Umbraco's issue tracker. To create new issues, please head over to GitHub Issues.
Make sure to read the blog posts announcing the move for more information.
Created by Asbjørn Riis-Knudsen 02 Nov 2012, 21:50:43 Updated by Sebastiaan Janssen 10 Jan 2013, 09:46:59
Relates to: U4-18
Now that Umbraco finally supports MVC, shouldn't the MVC dll for for ClientDependency be included as well? This would seem quite logical, as ClientDependency is supposed to fully support MVC as well.
@Shannon I removed the MVC version as it was built against MVC2 and required me to add a assembly redirect to the web.config file to make it work with MVC3. I wasn't sure if that would actually work and didn't have time to test this. Besides, it makes the upgrade experience better to not have to do config merging for a change.
Let's see if we can make CD.MVC independent of the MVC version or create a build for MVC3 and/or MVC4 (6.x should be upgrading to MVC4 at some point anyway).
Sure thing, i think i only have mvc3 installed so maybe that is why i didn't get any YSODs. I can't remember exactly if CDF is built to a specific version of MVC or not, but yeah, it should just try to use the latest version. I think people might find that they will have to put the assembly redirects in for the MVC stuff anyways for some code that they use.
I also only have MVC3 installed, and Per was getting the error as well, so it can't be just my machine. I didn't have time to look at the CDF source though, so I just left it out for this release.
Fixed in changeset 1b76c077d898
Type: Feature (planned)
Backwards Compatible: True
Affected versions: 4.10.0
Due in version: 6.0.0