Most design firms I have worked with required some hand holding on what they can and cannot do with regards to designing for an ASP.Net app. You hit all the big ones, the ID thing being the biggest issue.
In terms of building blocks, collaboration early and often did the trick for us. Once we established how we needed the design to be implemented to work easily within an ASP.Net context, things went smooth. Of course, the better the designer on the other end, the easier its going to be.
I am not one for having developers chop up PSD files. With the right designer or firm, you should be able to save time and money and get it done right from the outset. Most developers I know can tweak and extend css and markup, but are much less efficient when starting from a PSD, or from scratch.
每当我与设计公司合作构建 ASP.NET 页面时，我总是让他们设计它应该是什么样子。 与标记或 CSS 无关。 这给开发人员留下了很多工作要做，但避免了您刚才提到的所有错误。 我总是让设计师提供 PSD 文件并自己将其切碎。
如果这不能满足您的需求，您可以随时尝试 ASP.NET MVC。 它使您可以更好地控制放置在页面上的标记。
Any time I've worked with design firms building asp.net pages I've always just had them design what it should look like. Nothing to do with the markup or css. This leaves a lot of work to be done by the developers, but avoids all the mistakes you just mentioned. I've always had designers deliver a PSD file and chopped it up myself.
If this doesn't suit your needs you can always try ASP.NET MVC. It gives you a lot more control over the markup you put on the page.
一般来说，以设计师为生的人对 ASP.Net 的了解不够深入，无法避免它的怪癖。 期望他们生成考虑 ASP.Net 规则的 HTML 和 CSS 是不合理的。 标准实际上是在设计者这边。
对于未来的集成，您可能希望与一家拥有自己的 .Net 开发人员并与其设计师合作的公司合作，或者，如果您可以选择 .Net 3.5，您可以与拥有 MS Expressions Web 可供他们使用。
In general, people who make their living as designers do not know ASP.Net well enough to avoid it's, ahem, quirks. It's not reasonable to expect them to produce HTML and CSS which take ASP.Net's rules into consideration. The standards are actually on the designers side in this one.
For future integration, you may want to go with a firm that has their own .Net devs who work with their designers or, if you have the option of .Net 3.5, you could work with a design shop that has MS Expressions Web at their disposal.
发布评论
评论（3）
我合作过的大多数设计公司都需要有人掌握他们在设计 ASP.Net 应用程序时能做什么和不能做什么。 你遇到了所有大问题，ID 问题是最大的问题。
就构建模块而言，早期合作常常为我们带来好处。 一旦我们确定了如何实现设计以便在 ASP.Net 环境中轻松工作，事情就进展顺利了。 当然，另一端的设计师越好，事情就越容易。
我不是那种让开发者砍掉 PSD 文件的人。 有了合适的设计师或公司，您应该能够节省时间和金钱，并从一开始就完成它。 我认识的大多数开发人员都可以调整和扩展 css 和标记，但从 PSD 或从头开始时效率要低得多。
HTH。
Most design firms I have worked with required some hand holding on what they can and cannot do with regards to designing for an ASP.Net app. You hit all the big ones, the ID thing being the biggest issue.
In terms of building blocks, collaboration early and often did the trick for us. Once we established how we needed the design to be implemented to work easily within an ASP.Net context, things went smooth. Of course, the better the designer on the other end, the easier its going to be.
I am not one for having developers chop up PSD files. With the right designer or firm, you should be able to save time and money and get it done right from the outset. Most developers I know can tweak and extend css and markup, but are much less efficient when starting from a PSD, or from scratch.
HTH.
每当我与设计公司合作构建 ASP.NET 页面时，我总是让他们设计它应该是什么样子。 与标记或 CSS 无关。 这给开发人员留下了很多工作要做，但避免了您刚才提到的所有错误。 我总是让设计师提供 PSD 文件并自己将其切碎。
如果这不能满足您的需求，您可以随时尝试 ASP.NET MVC。 它使您可以更好地控制放置在页面上的标记。
Any time I've worked with design firms building asp.net pages I've always just had them design what it should look like. Nothing to do with the markup or css. This leaves a lot of work to be done by the developers, but avoids all the mistakes you just mentioned. I've always had designers deliver a PSD file and chopped it up myself.
If this doesn't suit your needs you can always try ASP.NET MVC. It gives you a lot more control over the markup you put on the page.
一般来说，以设计师为生的人对 ASP.Net 的了解不够深入，无法避免它的怪癖。 期望他们生成考虑 ASP.Net 规则的 HTML 和 CSS 是不合理的。 标准实际上是在设计者这边。
对于未来的集成，您可能希望与一家拥有自己的 .Net 开发人员并与其设计师合作的公司合作，或者，如果您可以选择 .Net 3.5，您可以与拥有 MS Expressions Web 可供他们使用。
In general, people who make their living as designers do not know ASP.Net well enough to avoid it's, ahem, quirks. It's not reasonable to expect them to produce HTML and CSS which take ASP.Net's rules into consideration. The standards are actually on the designers side in this one.
For future integration, you may want to go with a firm that has their own .Net devs who work with their designers or, if you have the option of .Net 3.5, you could work with a design shop that has MS Expressions Web at their disposal.