ASP. NET MVC 4.0 upgrade to 5.0 problems encountered and solutions

Let's talk about the project.

This project is an official website of the company, previously written by colleagues, using. NET and ASP. 4.0. The new development environment I used was VS2015, and I couldn't create a new controller on the basis of the original project. I can customize a controller class, integrate a controller, or create a view. Debugging can be run. Later I wanted to try out the local area network environment, with the release function of VS comes with. For other colleagues in the company to browse, found a problem: The new controller-related pages and the original controller created in the creation of the page is not generated, is not published successfully. At first did not pay attention to the problem of not generating the corresponding page, find a lot of other ideas to solve. Later see the online similar case, only to see, found that there is no page.

The release tool is definitely no problem, that is the problem with the project itself. When I first took over the project, I found that it was too low to create a controller problem. In the current development environment, the controller can only be created in a customized manner. So I just went to the update to ASP 5.0 Road, the specific configuration is as follows, English search is still easy to use AH.

http://world.episerver.com/documentation/Items/Upgrading/EPiServer-CMS/8/upgrading-from-mvc-4-to-5/

If you say that the problem is solved, then it is really a face-beating. After the upgrade, I can't wait to publish, eyes full of anticipation to stare at the publishing interface, found that there is no page I created. Debugging runs as well as before without any problems. It's a bit of a blindfold ....

After a while to think calmly, I think I can try to create a new controller to see if it works. (PS: You can create a controller now) to create a new controller, a new view, a release, that's how miracles happen ...

Simply use this stupid method, delete the original, from the new establishment. OK, Fix it.

Now I wonder where the nature of the problem is.?? My initial understanding is that the custom new page is not accepted by the project. Understanding is not deep enough, but also hope you give guidance twos, younger brother not very grateful. First write, not where, more care ^_^

ASP. NET MVC 4.0 upgrade to 5.0 problems encountered and solutions