MVC 3 / Razor views

I understand one of the main reason we probably aren't able to use the Razor view engine in website is due to the fact that we would have to replicate our master pages and maintain two versions of each until we were completely free of web forms style views.

Are there any other barriers to using Razor views in products that use platform website? Are there plans to possibly start chipping away at these?

This is just purely from a curiosity perspective.

Find more posts tagged with

refinitiv-internal

Accepted answers

Andrew Gerber

Hey Josh,
I don't believe there are any technological barriers to using Razor views in Website, as we are using MVC 3. As you stated, we would need to update all of our master pages etc to use Razor if we completely went that route. If you are implementing something that isn't reliant on any of the current Website master pages, I would encourage you to use Razor. If you are planning on using the current Website master pages, I would encourage porting that master page to Razor or contacting Website platform to get the work done.

-Drew

All comments

Andrew Gerber

Joshua Krebs

Great, this was what I was looking to hear. We have some views that are starting to get particularly nasty that we may re-factor soon and ideally we would port them to razor. If/When we get closer to that point, I'll make sure to loop in the platform team.

EXPLORE OUR SITES