ASP.NET - 设计者和开发者之间的协作
我们的组织拥有专门的设计师，他们设计页面并在 Dreamweaver 中进行剪切。 这在过去对于 ASP 和 PHP 网站来说效果很好。 现在，我们正在尝试使其与 .NET 一起工作，但由于 ASP.NET 中的项目结构而陷入困境。 大家如何与开发人员合作？ 我正在寻找的具体要点是：
- 将 Dreamweaver 内容传输到 Visual Studio - 更改服务器控件的 HTML 输入 -让设计人员能够访问已完成的 Visual Studio 产品，以便他们可以调整布局
谢谢！
Our organization has dedicated designers who design the page and cut it up in Dreamweaver. That's worked well in the past with ASP and PHP sites. Now we're trying to make it work with .NET, but are struggling because of the structure of a project in ASP.NET. How does everybody collaborate with developers? The specific points I am looking for are:
-Transferring Dreamweaver content to Visual Studio
-Changing HTML inputs to server controls
-Giving designer access to finished Visual Studio product so they can tweak layout
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
显然，您的设计师将会有一个轻微的学习曲线。 但话虽如此，我经常与 ASP.NET 网站上的设计师合作（顺便说一句，他们都没有使用 Dreamweaver，因此这可能是问题的一部分）。 通常，他们会按照他们想要的方式在服务器上创建 HTML，例如静态 HTML 页面，然后我将进入并使用 ASP.NET 控件手动替换表单字段。
另一方面，我发现使用输出最少 HTML 的控件（例如 Repeaters 而不是 DataGrid）来匹配设计的可能性最大。
一旦网站在服务器上启动并编程，他们就可以根据需要返回进行调整。
另外，就像我们必须稍微适应它们一样（让我们的服务器控件按照他们喜欢的方式吐出 html），它们也必须稍微适应我们，而不是像某些项目 id 属性那样严重依赖样式表中的 id 属性将由 hte .net 运行时控制，因为它们是控件。
通常，刚接触 ASP.NET 的设计师会感到这种新的做事方式非常威胁，特别是使用用户控件而不是包含文件，但它实际上与经典的 ASP/PHP 开发没有什么不同。
Obviously, there will be a slight learning curve for your designers. But with that said, I have worked quite often with designers (none of whom used Dreamweaver, btw, so that may be part of the problem) on asp.net sites. Usually, they will create the HTML exactly how they want it on the server like a static HTML page, then I will go in and replace form fields manually with asp.net controls.
On an aside, I have found that I have the best chance of matching the design using controls that spit out the least HTML, such as Repeaters instead of DataGrids.
Once the site is up on the server and programmed, they can go back in an tweak things if need be.
Also, just like we have to adapt to them a bit (making our server controls spit out html how they like it) they also have to adapt to us a bit and not rely as heavily on id attributes in their stylesheets as some items id attributes will be controlled by hte .net runtime since they are controls.
MOre often than not, a designer new to asp.net will feel very threatened by this new way of doing things, specially with user controls instad of include files, but its really not that different than classic asp/php development is.
解决这件事上所有问题的关键非常简单，但又很难实现：通常称为 语义标记。 如果您可以确保设计人员一开始就制定他们的 html 语义，并且 .Net 程序员保持呈现相同的标记，但在需要的地方使用他们的服务器控件，那么调整将不会成为问题 - 标记是相同的。
那么什么是语义html呢？ 你可能会问。 嗯，事情并不总是像人们希望的那么简单。 一个好的开始是让每个页面通过 XHTML 验证。
The key to the solution of all your problems in this matter is quite simple, and yet so hard to fulfill: it's usually called semantic markup. If you can make sure that the designers to start with make their html semantic, and that the .Net programmers keep rendering the same markup but with their server controls where needed, the tweaking won't be a problem - the markup is the same.
So what is semantic html, then? you may ask. Well, it's not always as simple as one would like it to be. A good start is to make every page pass XHTML validation.
根据我的经验，设计师创建的 HTML 几乎总是需要至少重构（如果不重写的话）。 所以，打开一个浏览器，左边是原始的HTML，并尝试在右边屏幕的VS中尽可能匹配它。
恕我直言，让设计人员访问 ASP 标记并不是一个好主意。 如果您只理解您正在操作的一半标签，太多的事情可能会出错。
In my experience, designer-created HTML almost always needs to be at least refactored, if not rewritten. So, open a browser with the original HTML on the left, and try to match it as closely as possible in VS on the right screen.
Giving designers access to ASP markup is not a good idea, imho. Too much can go wrong if you only understand half of the tags you are manipulating.
使用 Microsoft Expressions 系列产品之一怎么样？ 我听说它们对于 .NET 就像 Dreamweaver 对于 PHP/ASP 一样。
How about using one of Microsoft Expressions line of products? I've heard they are to .NET what dreamweaver is to PHP/ASP.