设计人员如何/能够使用 ASP.NET
在我参与过的大多数项目中，设计人员生成 HTML 代码，然后开发人员将其转换为 ASP.NET，包括母版页等，这些都应该真正成为设计的一部分。
当它成为 ASP.NET 后，设计人员无法使用他们的工具来处理代码。
我知道 ASP.NET 的很多设计都是为了将代码和设计分离，原则上设计人员应该能够使用 Visual Web Developer 进行设计方面的工作，但我从未见过设计人员使用VWD。
实践中合作是如何进行的？对设计师的最佳期望是什么？
On most projects I've been one, designers has produced HTML code, then developers turned it into ASP.NET, including master-pages etc that should really be a part of design.
After it has become ASP.NET, designers could not work on the code with their tools.
I know that a lot of the design of ASP.NET is made with the purpose of separating code and design, and in principle designers should be able to work on design aspects with the Visual Web Developer, but I've never seen a designer using VWD.
How is cooperation done in practice, and what is about the best one can expect from a designer?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
来自同时做这两件事的人：
大部分设计应该用 CSS 完成，所以这不是问题。
因此，页面的布局归结为具有 ID 和类的元素（简单地说）。
我尝试按原样保留这些 ID 和类，并根据需要将 ContentPlaceHolders 放置在其中（如果可能），并使用正确的类创建控件或外观。
最理想的是，设计师和程序员应该一起工作，并了解彼此的限制和要求（这并不总是能做到，有时这些是由不同的公司完成的）。我认为这里的大部分责任在于开发人员 - 他们需要正确的控制才能获得预期的输出。
坦率地说，网页设计师应该关心 HTML 和 CSS，而不是使用什么服务器端技术来交付它们。我对 Web 设计师的最好期望是编写灵活的 CSS，它可以在不破坏 HTML 结构的情况下进行视图更改（即额外的 div 或表格，就像 ASP.NET 所做的那样）。
From someone who does both:
Most of the design should be done with CSS, so this isn't a problem.
The layout of the page, therefore, comes down to elements with IDs and classes (simplistically speaking).
I try to keep these IDs and classes as is, and place ContentPlaceHolders inside them as needed, when possible, and create controls or skins with the right classes.
Optimally, designers and programmers should work together, and know each others limitations and requirements (this cannot always be done, sometimes these are done by different companies). I think most of the responsibility here lies on the developers - they need the right controls to get the expected output.
Frankly, a web designer should care about HTML and CSS, not about what server-side technology is used to deliver them. The best I would expect from a web designer is to write flexible CSS, that can take a view changes to the HTML structure without breaking (that is - extra divs or tables, as ASP.NET tends to do).
优秀的 ASP.NET 开发人员会明智地使用可用的控件集。例如，在大多数情况下，ListView 将执行 GridView 可以执行的所有操作，并生成干净、SEO 友好的标记。
在 ASP.NET 环境中，我鼓励设计人员使用 Expression。企业主可以利用微软的新协议，以 100 美元的价格获得 VS、Expression 等，为期三年。
我认为开发人员和设计师都必须拥抱彼此的世界才能发挥作用。
A good ASP.NET developer will intelligently use the set of controls available. For example, in most cases, the ListView will do everything the GridView can, and produce clean, SEO-friendly markup.
In the ASP.NET environment, I would encourage the use of Expression by designers. Business owners can avail of the new deal from Microsoft and obtain VS, Expression, etc., for $100 for three years.
I think both developers and designers have to embrace each others world for anything to work.
我们仍然坚持设计师制作 PSD 文档并希望将其渲染为 HTML 的老式方式。
然后我们接管它们并将它们转换为.Net，然后设计者请求更改，我们兜了一段时间才得出可接受的解决方案。
如果设计器能够更轻松地集成到 .Net 的 HTML 中，那就太好了，但我暂时没有看到这种情况发生，而微软提倡在开发中使用脚本。
We are still stuck with the old fashioned way of the designer producing PSD documents and hopefully rendering them into HTML.
Then we take them over and convert them to .Net, then the designer requests a change and we go in circles for a while before coming to an acceptable solution.
It would be nice if the designer could integrate into the HTML of .Net easier but I don't see that happening for a while, not while Microsoft advocates using scripting in your development..
我发现使用 ASP.NET MVC 将使设计人员的工作变得更加轻松。特别是如果您不使用 HTML.RenderImage 之类的东西，而是在页面上放置一个 IMG 标记，并将
<%= ViewData["MyImage"] %>作为 src。这将允许设计者看到他们喜欢和理解的 html，同时让您灵活地设置源（这是开发人员应该做的所有事情）。目标是远离 ASP.NET 控件，因为这会让设计人员感到困惑，同时仍然保持快速开发的灵活性。I've found that using ASP.NET MVC will make the designer's job much easier. Especially if you stay away from using things like HTML.RenderImage, and instead place an IMG tag on the page with
<%= ViewData["MyImage"] %>as the src. This will allow the designer to see the html they like and understand, while giving you the flexibility to set the source(which is all the developer should be doing). The goal being to stay away from ASP.NET controls, which would confuse a designer, while still keeping their flexibility to develop quickly.