Is MVC Web Application the best workflow for an interface developer?

I work for a web company, and the programmer is working on a web application that is currently being built using the MVC framework. As an interface developer, I will need to do html, jquery and css for this application.

The setup consists of views with cshtml files. My question here is, what is the best way to develop as a guy with this kind of mood?

I am currently opening files in Dreamweaver and editing css and html in this way, saving and uploading the file to our development server. Then I proceed to update the browser and see my changes.

I use bootstrap with less if that matters for anything. Another problem is that the cshtml files are not suitable for Dreamweaver, but I can just use a simple text editor, but the only thing I like about Dreamweaver is to automatically upload to FTP the save function, which saves me a lot of time.

Of course, is there a better way to edit these cshtml files? Or is this the best way for this kind of thing? I am very curious to find out how other people will do this kind of work.

Thanks, any input is welcome.

+4
source share
3 answers

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 ?

+6
source

Typically, I have a website configured to work with IIS on my development computer, manually edit the cshtml and css files in Visual Studio and refresh my browser to see the changes.

For some tweaking of css, I can experiment in the browser using Firebug or the IE Developer toolbar (depending on the browser).

+1
source

Here are some suggestions

  • You can create a sample HTML page and create it on your Mac, layout files can be easily developed based on this later. If you're not interested in server-side stuff at all, that's fine. There are many nuget packages for styles done this way. Easier to use / consume for other people. You do not need it, but you can create a nuget package for easier sharing. If you do not know what nuget is, check this link http://docs.nuget.org/

  • You can use the parallels http://www.parallels.com/products/desktop/ for windows on a Mac and test / develop your application there using visual studio web express and IIS

  • Bootcamp is not that hard. Depending on your net speed, this may take an hour at most.

Hope this helps

0
source

Source: https://habr.com/ru/post/1445997/


All Articles