M
Maxim Fridental
It is well advertised .NET allows separate developing of web pages by a web
designer and a web programmer. Where could I find recommendations from
Microsoft about the corresponding development process or tools that really
enable such parallel development? I would also like to read some real world
experiences.
We have particularly the following problems:
1. Our web designer can't use Visual Studio, so a) all HTML code must be
copied by a web programmer manually and b) her HTML pages aren't under
source control.
2. Our web designer knows nothing about modularity, so every HTML page she
creates shares some HTML code, that must be refactored by the web programmer
using user web controls. Even if the web designer knows about and values
modularity, how can she create and test modular HTML pages?
3. Some HTML controls are normally replaced by a web programmer with ASP
controls. That is responsibility of the web programmer, isn't it? But assume
the web designer has created a new, slightly different version of the page.
The web programmer must a) read the complete HTML code of the new page, b)
match it to the existing .aspx and c) add or remove correspoding tags. It is
very time consuming, error prone and unpleasing manual task.
Should our web designer create .aspx pages directly? Or should our designer
and programmer pair? And what should we do if web pages are designed by a
separate company?
designer and a web programmer. Where could I find recommendations from
Microsoft about the corresponding development process or tools that really
enable such parallel development? I would also like to read some real world
experiences.
We have particularly the following problems:
1. Our web designer can't use Visual Studio, so a) all HTML code must be
copied by a web programmer manually and b) her HTML pages aren't under
source control.
2. Our web designer knows nothing about modularity, so every HTML page she
creates shares some HTML code, that must be refactored by the web programmer
using user web controls. Even if the web designer knows about and values
modularity, how can she create and test modular HTML pages?
3. Some HTML controls are normally replaced by a web programmer with ASP
controls. That is responsibility of the web programmer, isn't it? But assume
the web designer has created a new, slightly different version of the page.
The web programmer must a) read the complete HTML code of the new page, b)
match it to the existing .aspx and c) add or remove correspoding tags. It is
very time consuming, error prone and unpleasing manual task.
Should our web designer create .aspx pages directly? Or should our designer
and programmer pair? And what should we do if web pages are designed by a
separate company?