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: Glad you got it 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: Glad you got it working!