After updating to RazorGenerator extension 1.6.3, RazorGenerator.Mvc package 2.2.1 and ASP.NET MVC 5.0 some stuff stopped working.
We have a custom WebViewPage defined in web.config using <pages pageBaseType=""/>. Previously this worked like a charm and the .generated.cs files inherited from our custom WebViewPage with the model as a generic type.
This has changed, however. Now, no matter what we put in web.config the generated class inherits from the default WebViewPage which breaks a lot of code.
It seems that downgrading the Mvc version is not enough to make our application work again, which leads us to believe RazorGenerator is (at least partly) to blame. Is this a known issue? Should this work?
Comments: Posting back as a final update. It turns out my issue was related to the others posted in another thread. The short story why I was getting different results than others because even tho I thought my referencing/target project was an MVC project type, it indeed was not, despite having all the artifacts. Once switching to a true MVC-type project, everything worked as expected, including base types. Again, this is in VS 2013, MVC 5,0, 1.6.3 VSIX and RazorGenerator.MVC 2.2.1. On another note, I have finally completed my plugin solution where these precompiled MVC projects are discovered and loaded at runtime. Everything works and tons of thanks to DAVID (et al)!!! So sorry for the runarounds earlier with it all being due to my project type. Cheers, Mike
We have a custom WebViewPage defined in web.config using <pages pageBaseType=""/>. Previously this worked like a charm and the .generated.cs files inherited from our custom WebViewPage with the model as a generic type.
This has changed, however. Now, no matter what we put in web.config the generated class inherits from the default WebViewPage which breaks a lot of code.
It seems that downgrading the Mvc version is not enough to make our application work again, which leads us to believe RazorGenerator is (at least partly) to blame. Is this a known issue? Should this work?
Comments: Posting back as a final update. It turns out my issue was related to the others posted in another thread. The short story why I was getting different results than others because even tho I thought my referencing/target project was an MVC project type, it indeed was not, despite having all the artifacts. Once switching to a true MVC-type project, everything worked as expected, including base types. Again, this is in VS 2013, MVC 5,0, 1.6.3 VSIX and RazorGenerator.MVC 2.2.1. On another note, I have finally completed my plugin solution where these precompiled MVC projects are discovered and loaded at runtime. Everything works and tons of thanks to DAVID (et al)!!! So sorry for the runarounds earlier with it all being due to my project type. Cheers, Mike