我必须修复旧的 ASP.NET 应用程序的外观，以便它能够符合我的组织的新 Web 视觉标识。旧应用程序没有任何母版页，并使用非常基本的 .include 文件。修改 .include 标头并不会改变应用程序页面的整体外观，而且我仍然需要手动导入新的 css 定义，在 60 个奇怪的 .aspx 页面上用 div 替换 table 标签。
我应该如何进行？我考虑到长期的可维护性，因此母版页是显而易见的解决方案。是否有任何 css 解析器可以简化这种转换？
谢谢。
-德鲁夫
I've to fix an old ASP.NET application's appearance so that it can conform to the new web visual identity of my organization. The old application does not have any master page and uses a very basic .include file. Modifying the .include header does not change the overall look of the app's pages much, and I still have to manually import new css definitions, replace the table tags with divs on the 60 odd .aspx pages.
How should I proceed? I have long term maintainability in mind, so a master page is the obvious solution. Are there any css parsers which can ease this conversion?
Thank you.
-Dhruv
发布评论
评论（1）
我不知道有什么工具可以让你变得非常容易。
我最好的建议是咬紧牙关升级到 ASP.NET 3.5 或 4.0 项目，这样您就可以利用 .NET 自该网站建立以来的进步。
从总体上看，60 页并不是一个很大的数字。创建新的母版页，然后删除这 60 个页面的所有非内容部分，并将它们放在 标记中。
我敢打赌，您会发现这比您现在担心的工作少得多，更重要的是，从现在开始，每次您必须更新网站时，它都会带来红利。
I'm not aware of any tool that's going to make this terribly easy for you.
My best advice would be to bite the bullet and upgrade to an ASP.NET 3.5 or 4.0 project so you can take advantage of the advances in .NET since that web site was built.
In the grand scheme of things, 60 pages isn't a huge amount. Create the new Master Page (s), then just strip out all the non-content sections of those 60 pages and surround them in
<asp:Contenttags.I bet you'll find it's a lot less work than you fear right now, and more importantly, it will pay dividends every time you have to update the site from now on.