TL DR
- I would suggest creating web design first, at least in prototype format (your results will be html and css, and maybe some js)
- The .net dev team does the
cshtml work integrating your design - Then you need to participate during the review and correct the result.
More details
AFAIK there is still no WYSIWYG editor for Razor .cshtml files, so they must be manually processed .
I would recommend that you (as a web designer) provide the developer with the html + css prototype command for each web page as simple html as possible (i.e. all html elements with the necessary classes + id and possibly also at least for first pass in js / jquery ). Also specify the common page bits so that the developer can extract Layouts / master pages and Partial Views , etc.
The rationale here is that it makes no sense to try to encode .cshtml if you do not have .net experience, or IIS or Cassini at hand, since the code needs to be debugged. The disadvantages of an FTP connection to your server will be obvious if you break the razor code when changing html.
It then becomes the task of the dev command to ensure that the html generated by .cshtml matches your html layouts.
Remember to keep your html as clean as possible, with all the styles in css.
With time and experience, you should also be able to handle the razor syntax, and then you and the development team can transfer responsibilities so that you accept the data transfer from MVC controllers (ViewModels, ViewBags, TempData and Post data / Json, etc. .) And then you can put html in cshtml ?
source share