Can I create HTML code for an ASP.Net or ASP.Net MVC site first?

Question

Does OK work to first encode the HTML for an ASP.Net or ASP.Net MVC site, and then pass this to the coders? If not, what is the best approach to integrate them?

Answer 1

This is absolutely acceptable. This is one of the great features of MVC.

Create your HTML and CSS and give developers code in dynamic bits and worry about all this.

Answer 2

I do not think that something is wrong with this approach. I know the places where web designers html layout to give their developers "starting points" to create their pages.

Answer 3

It works very well. Some of the HTML may be replaced by ASP controls.

Personally, I would prefer to start with an HTML page that mocks quite well, rather than JPEG in a Word Doc.

Answer 4

For ASP.NET MVC, yes, it is certainly possible. In fact, this is one of the benefits of MVC . You can switch your front end on a whim without big changes. Web designers can work independently in the background.

With WebForms (traditional ASP.NET ), this is possible, but not so simple. With things like code by page, is the main problem. Web designers should not worry, but ASP.NET has code attached to the page.

Answer 5

If you are talking about the layout, then it really depends on what you expect from them, in terms of the dynamic content that will be added. Html may not be useful to them, but it will probably be better than a layout in everything, since html will limit you to what is easy to implement in asp.net. where in the layout in a word or photoshop you can do something that is not easy to implement in asp.net. So I would say html mockup is a good idea.

If you do not need to program, i.e. this is just a static hmtl page, then I just bind to it as an html page.

Answer 6

[HttpPost] public ActionResult Image(picture pic) { var path = ""; foreach (var file in pic.Files) { if (file.ContentLength > 0) { var filename = file.FileName; path = Path.Combine(Server.MapPath("~/Content/images"), filename); file.SaveAs(path); } } return RedirectToAction("Index"); }