We are developing an ASP.NET application. We retained an outside UI design firm, and for the most part have been very pleased with their work. Their "deliverable" to us was clickable screens -- Visual Studio solutions with ASPX files, images, master pages, etc. The screens were not connected to any data source. They had dummy data so that we could see how the UI worked.
我们正在开发一个ASP.NET应用程序。我们聘请了一家外部UI设计公司,并且在很大程度上对他们的工作非常满意。他们向我们提供的“可交付成果”是可点击屏幕 - 带有ASPX文件,图像,母版页等的Visual Studio解决方案。屏幕未连接到任何数据源。他们有虚拟数据,以便我们可以看到用户界面如何工作。
One problem we've run into is that our developers are used to using Visual Studio design mode. The pages we receive from the UI firm have problems sometimes when we pull them up into design mode. The consultant's developers coded these screens without using design mode.
我们遇到的一个问题是我们的开发人员习惯使用Visual Studio设计模式。当我们将它们提升到设计模式时,我们从UI公司收到的页面有时会出现问题。顾问的开发人员在不使用设计模式的情况下编码这些屏幕。
We assumed they'd be using design mode, but this wasn't specified in the contract. Was this too much to assume? Is there a lot of ASP.NET development work that never goes through VS design mode?
我们假设他们正在使用设计模式,但合同中没有规定。这太难以承担了吗?是否有很多ASP.NET开发工作从未经历过VS设计模式?
Third party edit:
Suggestion: people responding to this question should specify which version of Visual Studio they're using, as Microsoft trashed the code base that was in the VS2005 and earlier designers, and replaced it with the one they purchased when they purchased the Expression products. The two are totally unrelated, and the new one is far better. - John Saunders
建议:响应此问题的人应该指定他们使用的Visual Studio版本,因为Microsoft破坏了VS2005和早期设计人员中的代码库,并将其替换为购买Expression产品时购买的代码库。这两者完全不相关,而新的则更好。 - 约翰桑德斯
18 个解决方案
#1
The more and more you work with Visual Studio, the less and less you rely on Design Mode. Complicated UIs tend to make the design view look atrocious.
您越来越多地使用Visual Studio,您越来越依赖于设计模式。复杂的UI往往使设计视图看起来很残酷。
#2
I (and peers) never use Design Mode, for two reasons:
我(和同行)从不使用设计模式,原因有两个:
-
I learnt in VS 2003 not to touch Design Mode because your HTML was managled by VS. (Not anymore though since 2008, but once bitten ...)
我在VS 2003中学到了不要触摸设计模式,因为你的HTML是由VS管理的。 (虽然自2008年以来不再存在,但曾经被咬过......)
-
It can take ages to render.
渲染可能需要很长时间。
Much quicker to drag-drop from toolbox and hand-code.
从工具箱和手动代码拖放更快。
#3
I actually find that ASP.NET developers that do use the designer to be quite rare. The Visual Studio designer is notoriously bad at generating clean markup.
我实际上发现使用设计器的ASP.NET开发人员非常少见。 Visual Studio设计器在生成干净标记方面非常糟糕。
#4
I never use design mode, probably because it used to mess my markup so much. Plus I do a lot of dynamic rendering, so there is no point. And I use exclusively CSS for formatting, I don't want VS messing around.
我从不使用设计模式,可能是因为它过去常常弄乱我的标记。另外我做了很多动态渲染,所以没有意义。我只使用CSS进行格式化,我不希望VS搞乱。
#5
Many never use it, because of bad past experiences. I have found little trouble with Design mode in VS2008, when using modern controls, which are up to date and have good designer support.
许多人从不使用它,因为过去经历不好。在使用现代控件时,我发现VS2008中的设计模式没什么问题,这些控件是最新的并且具有良好的设计器支持。
On the other hand, because of the earlier problems, a lot of custom server controls do not have good designer support, so are much less useful in design mode now that the earlier designer code base has been replaced with a good one.
另一方面,由于早期的问题,许多自定义服务器控件没有良好的设计器支持,因此在设计模式下使用较少,因为早期的设计器代码库已被替换为良好的设计器代码库。
#6
I almost never use design mode. It typically creates ugly HTML, and call me anal, but I really like to have clean HTML. If that means hand-coding it, so be it.
我几乎从不使用设计模式。它通常会创建丑陋的HTML,并称我为肛门,但我真的很想拥有干净的HTML。如果这意味着手工编码,那就这样吧。
#7
I prefer doing it manually, I like to have control.
我更喜欢手动操作,我喜欢控制。
If I want to look at the result, F5.
如果我想看看结果,F5。
#8
I almost never use design mode. For me, the biggest reason is because I learned web design/development in Notepad, so I was used to (and comfortable) working with code. Design mode makes me uncomfortable because I'm never sure exactly what decisions VS will make with regard to HTML, etc. Additionally, I can't imagine that a developer would learn nearly as much about ASP.NET and VB/C# using design mode.
我几乎从不使用设计模式。对我来说,最大的原因是因为我在记事本中学习了网页设计/开发,所以我习惯(并且很舒服)使用代码。设计模式让我感到不舒服,因为我无法确定VS将在HTML等方面做出什么样的决定。此外,我无法想象开发人员会使用设计模式学习几乎所有关于ASP.NET和VB / C#的知识。
The only time I use design mode is to automatically configure a GridView or something like that like.
我使用设计模式的唯一一次是自动配置GridView或类似的东西。
#9
Design Mode is taking quite a beating here, but let me point out that it is great for learning about new controls. When you are new to ASP.NET, or are using a new library of controls, Design Mode is a godsend for two reasons:
设计模式在这里受到了很大影响,但我要指出,它非常适合学习新的控件。当您是ASP.NET新手,或正在使用新的控件库时,设计模式是一个天赐之物,原因有两个:
- You can modify properties on the Property Editor and see them reflected immediately. This is particularly true for list-container type controls, where the entire layout may depend on one property. Running your application five times to see all five layouts is very tedious.
- Controls with complex behavior (and lets face it, thats why you're using a control, right?) often have a lot of configuration built into their Smart Tags. Notice the little [>] arrow in the top right of the control? Click it. It'll probably help you out big time. This is particularly true for configuring DataSources, whose syntax is very meticulous.
您可以在属性编辑器上修改属性,并立即查看它们。对于列表容器类型控件尤其如此,其中整个布局可能依赖于一个属性。运行应用程序五次以查看所有五个布局非常繁琐。
具有复杂行为的控件(让我们面对它,这就是你使用控件的原因,对吧?),他们的智能标签中经常会有很多配置。注意控件右上角的小[>]箭头?点击它。这可能会帮助你度过难关。对于配置DataSources尤其如此,DataSources的语法非常细致。
When I was first learning to use Telerik controls, I relied heavily on the Smart Tags they provide, which are very robust and complete. From that, you can see what kind of ASPX markup is generated and learn to work outside of Design Mode. I am a learn-by-doing kind of guy, so I much prefer this approach to looking at the documentation when using something for the first time.
当我第一次学习使用Telerik控件时,我非常依赖他们提供的智能标签,这些标签非常强大且完整。从那里,您可以看到生成了什么样的ASPX标记,并学习在设计模式之外工作。我是一个边做边学的人,所以我更喜欢这种方法在第一次使用东西时查看文档。
#10
I'm using VS2008, and I never use the design view. I find the code view to just be easier and more responsive than the designer.
我正在使用VS2008,我从不使用设计视图。我发现代码视图比设计者更容易,响应更快。
#11
Y'know, I never even realised I use the source screens 100% of the time. I usually develop in VS2005.
你知道,我从来没有意识到我100%使用源屏幕。我通常在VS2005中开发。
Whenever I do actually open the design mode, it's by accident, and I try and hit the source view before it renders. I've never been impressed with the design mode, and find it slow as well as adding a lot of unnecessary markup. I also find that intellisense and the properties window mean that I don't need a GUI to develop.
每当我真正打开设计模式时,它都是偶然的,我尝试在渲染之前点击源视图。我从来没有对设计模式印象深刻,发现它很慢,并添加了许多不必要的标记。我还发现intellisense和属性窗口意味着我不需要GUI来开发。
The design mode can also be a nightmare when you're trying to add any nested items. Because we've been developing for a customer using IE6 we've been using tables for formatting so we don't need different DIV definitions. Just clicking in an empty cell can be difficult, and resizing a column can take far too long.
当您尝试添加任何嵌套项时,设计模式也可能是一场噩梦。因为我们一直在为使用IE6的客户开发,所以我们一直在使用表格进行格式化,因此我们不需要不同的DIV定义。只需单击一个空单元格就很困难,调整列的大小可能需要太长时间。
For things like Template Fields in grids, I don't even know how I'd go about setting this up in design view!
对于像网格中的模板字段这样的东西,我甚至不知道如何在设计视图中进行设置!
Having said that, design mode every time for windows apps!
话虽如此,每次为windows应用程序设计模式!
#12
Design mode is getting better and I'd say that it's likely to become more prevalent as time goes on and the design mode tools continue to improve. I design all my components for design mode, but I still do the large majority of my code by hand - it allows greater control of code layout and doesn't end up creating an auto-formatted mess that I then have to dig through to figure out what changes need making. I know that in future my components are likely going to be used by developers that do most of their design by drag/drop and it's easier to cater for that now than have to come back and do it after the event.
设计模式越来越好,我会说随着时间的推移,它可能会变得更加普遍,设计模式工具也会不断改进。我为设计模式设计了所有组件,但我仍然手工完成大部分代码 - 它允许更好地控制代码布局,并且最终不会创建自动格式化的混乱,然后我必须深入研究需要做出哪些改变。我知道将来我的组件可能会被那些通过拖放操作完成大部分设计的开发人员使用,现在更容易满足这一要求,而不是必须在事件发生后再回来做。
#13
Granted I'm doing MVC stuff, but I never use it - I "grew up" with PHP and code editors, and it still does me just fine.
虽然我正在做MVC的东西,但我从来没有使用过它 - 我在PHP和代码编辑器“长大”,它仍然让我很好。
#14
I'm using two different versions of .NET (2003 & 2005). Some of the forms that were written in 2003 can no longer be edited in 2003 and the installation requires that they be maintained in 2003, so I use KEDIT to edit those forms. Some of the forms in one application are too big for the .NET editor and I prefer a strong editor anyway.
我正在使用两个不同版本的.NET(2003和2005)。 2003年编写的某些表单在2003年无法再编辑,安装需要在2003年进行维护,因此我使用KEDIT编辑这些表单。一个应用程序中的某些表单对于.NET编辑器来说太大了,我更喜欢强大的编辑器。
#15
I have no problem working in design mode. One exception is asp:Repeaters, which are not supported, or GridViews which tend to override my manual column definitions.
在设计模式下工作没问题。一个例外是asp:不支持的Repeater,或者倾向于覆盖我的手动列定义的GridView。
The other is if VS tries to do a full project scan if I rename a control, and then fails.
另一种情况是,如果我重命名控件,VS会尝试执行完整的项目扫描,然后失败。
#16
We primarily use the code view. The design mode is quite buggy we've found in VS 2008. XML controls tend to barf random character sets out for some reason, and VS will generally run slow whilst trying to render everything on screen. I mainly use the code-view.
我们主要使用代码视图。我们在VS 2008中发现了设计模式非常错误。由于某些原因,XML控件往往会出现随机字符集,并且在尝试在屏幕上呈现所有内容时,VS通常会运行缓慢。我主要使用代码视图。
#17
Traditionally WYSIWYG designers produced poor code and render CSS and #INCLUDEd files poorly so they were of limited use, so developers tended to code by hand. In addition, these tools allowed you to go a certain distance without real knowledge of what you were doing, which was fine for web tutorials and personal homepages, but as soon as you wanted an extra degree of control you became unstuck - when meant you had to resort to looking 'under the hood' anyway.
传统上WYSIWYG设计人员生成的代码很差,并且CSS和#INCLUDEd文件的渲染效果很差,因此它们的使用受到限制,因此开发人员倾向于手动编写代码。此外,这些工具允许你在没有真正了解自己正在做的事情的情况下走一段距离,这对于网络教程和个人主页来说很好,但是只要你想要一个额外的控制程度,你就会失败 - 当你意味着你有了无论如何都要求“引擎盖”。
Although tools have improved over time, many developers are so comfortable with hand-coding that they all but forget about the Design View - I certainly can't remember last time I used it. I'm sure there are a number of situations where such tools could be genuinely useful, but we are doing fine without and don't want to be bothered with figuring when & where such features can best be used.
虽然工具随着时间的推移而有所改进,但许多开发人员对手动编码非常熟悉,他们都忘记了设计视图 - 我上次使用时肯定记不起来了。我确信在很多情况下这些工具可能真的很有用,但我们没有做好,也不想在计算何时何地可以最好地使用这些功能时感到困扰。
#18
Our UI is complicated and it is impossible for us to use design mode with VS2005.
我们的UI很复杂,我们不可能在VS2005中使用设计模式。
The only time I have touched design mode is to do a quick and dirty prototype or an internal app.
我接触设计模式的唯一一次是做一个快速而肮脏的原型或内部应用程序。
How often do I not use design mode? 99% of the time.
我多久不使用一次设计模式? 99%的时间。
#1
The more and more you work with Visual Studio, the less and less you rely on Design Mode. Complicated UIs tend to make the design view look atrocious.
您越来越多地使用Visual Studio,您越来越依赖于设计模式。复杂的UI往往使设计视图看起来很残酷。
#2
I (and peers) never use Design Mode, for two reasons:
我(和同行)从不使用设计模式,原因有两个:
-
I learnt in VS 2003 not to touch Design Mode because your HTML was managled by VS. (Not anymore though since 2008, but once bitten ...)
我在VS 2003中学到了不要触摸设计模式,因为你的HTML是由VS管理的。 (虽然自2008年以来不再存在,但曾经被咬过......)
-
It can take ages to render.
渲染可能需要很长时间。
Much quicker to drag-drop from toolbox and hand-code.
从工具箱和手动代码拖放更快。
#3
I actually find that ASP.NET developers that do use the designer to be quite rare. The Visual Studio designer is notoriously bad at generating clean markup.
我实际上发现使用设计器的ASP.NET开发人员非常少见。 Visual Studio设计器在生成干净标记方面非常糟糕。
#4
I never use design mode, probably because it used to mess my markup so much. Plus I do a lot of dynamic rendering, so there is no point. And I use exclusively CSS for formatting, I don't want VS messing around.
我从不使用设计模式,可能是因为它过去常常弄乱我的标记。另外我做了很多动态渲染,所以没有意义。我只使用CSS进行格式化,我不希望VS搞乱。
#5
Many never use it, because of bad past experiences. I have found little trouble with Design mode in VS2008, when using modern controls, which are up to date and have good designer support.
许多人从不使用它,因为过去经历不好。在使用现代控件时,我发现VS2008中的设计模式没什么问题,这些控件是最新的并且具有良好的设计器支持。
On the other hand, because of the earlier problems, a lot of custom server controls do not have good designer support, so are much less useful in design mode now that the earlier designer code base has been replaced with a good one.
另一方面,由于早期的问题,许多自定义服务器控件没有良好的设计器支持,因此在设计模式下使用较少,因为早期的设计器代码库已被替换为良好的设计器代码库。
#6
I almost never use design mode. It typically creates ugly HTML, and call me anal, but I really like to have clean HTML. If that means hand-coding it, so be it.
我几乎从不使用设计模式。它通常会创建丑陋的HTML,并称我为肛门,但我真的很想拥有干净的HTML。如果这意味着手工编码,那就这样吧。
#7
I prefer doing it manually, I like to have control.
我更喜欢手动操作,我喜欢控制。
If I want to look at the result, F5.
如果我想看看结果,F5。
#8
I almost never use design mode. For me, the biggest reason is because I learned web design/development in Notepad, so I was used to (and comfortable) working with code. Design mode makes me uncomfortable because I'm never sure exactly what decisions VS will make with regard to HTML, etc. Additionally, I can't imagine that a developer would learn nearly as much about ASP.NET and VB/C# using design mode.
我几乎从不使用设计模式。对我来说,最大的原因是因为我在记事本中学习了网页设计/开发,所以我习惯(并且很舒服)使用代码。设计模式让我感到不舒服,因为我无法确定VS将在HTML等方面做出什么样的决定。此外,我无法想象开发人员会使用设计模式学习几乎所有关于ASP.NET和VB / C#的知识。
The only time I use design mode is to automatically configure a GridView or something like that like.
我使用设计模式的唯一一次是自动配置GridView或类似的东西。
#9
Design Mode is taking quite a beating here, but let me point out that it is great for learning about new controls. When you are new to ASP.NET, or are using a new library of controls, Design Mode is a godsend for two reasons:
设计模式在这里受到了很大影响,但我要指出,它非常适合学习新的控件。当您是ASP.NET新手,或正在使用新的控件库时,设计模式是一个天赐之物,原因有两个:
- You can modify properties on the Property Editor and see them reflected immediately. This is particularly true for list-container type controls, where the entire layout may depend on one property. Running your application five times to see all five layouts is very tedious.
- Controls with complex behavior (and lets face it, thats why you're using a control, right?) often have a lot of configuration built into their Smart Tags. Notice the little [>] arrow in the top right of the control? Click it. It'll probably help you out big time. This is particularly true for configuring DataSources, whose syntax is very meticulous.
您可以在属性编辑器上修改属性,并立即查看它们。对于列表容器类型控件尤其如此,其中整个布局可能依赖于一个属性。运行应用程序五次以查看所有五个布局非常繁琐。
具有复杂行为的控件(让我们面对它,这就是你使用控件的原因,对吧?),他们的智能标签中经常会有很多配置。注意控件右上角的小[>]箭头?点击它。这可能会帮助你度过难关。对于配置DataSources尤其如此,DataSources的语法非常细致。
When I was first learning to use Telerik controls, I relied heavily on the Smart Tags they provide, which are very robust and complete. From that, you can see what kind of ASPX markup is generated and learn to work outside of Design Mode. I am a learn-by-doing kind of guy, so I much prefer this approach to looking at the documentation when using something for the first time.
当我第一次学习使用Telerik控件时,我非常依赖他们提供的智能标签,这些标签非常强大且完整。从那里,您可以看到生成了什么样的ASPX标记,并学习在设计模式之外工作。我是一个边做边学的人,所以我更喜欢这种方法在第一次使用东西时查看文档。
#10
I'm using VS2008, and I never use the design view. I find the code view to just be easier and more responsive than the designer.
我正在使用VS2008,我从不使用设计视图。我发现代码视图比设计者更容易,响应更快。
#11
Y'know, I never even realised I use the source screens 100% of the time. I usually develop in VS2005.
你知道,我从来没有意识到我100%使用源屏幕。我通常在VS2005中开发。
Whenever I do actually open the design mode, it's by accident, and I try and hit the source view before it renders. I've never been impressed with the design mode, and find it slow as well as adding a lot of unnecessary markup. I also find that intellisense and the properties window mean that I don't need a GUI to develop.
每当我真正打开设计模式时,它都是偶然的,我尝试在渲染之前点击源视图。我从来没有对设计模式印象深刻,发现它很慢,并添加了许多不必要的标记。我还发现intellisense和属性窗口意味着我不需要GUI来开发。
The design mode can also be a nightmare when you're trying to add any nested items. Because we've been developing for a customer using IE6 we've been using tables for formatting so we don't need different DIV definitions. Just clicking in an empty cell can be difficult, and resizing a column can take far too long.
当您尝试添加任何嵌套项时,设计模式也可能是一场噩梦。因为我们一直在为使用IE6的客户开发,所以我们一直在使用表格进行格式化,因此我们不需要不同的DIV定义。只需单击一个空单元格就很困难,调整列的大小可能需要太长时间。
For things like Template Fields in grids, I don't even know how I'd go about setting this up in design view!
对于像网格中的模板字段这样的东西,我甚至不知道如何在设计视图中进行设置!
Having said that, design mode every time for windows apps!
话虽如此,每次为windows应用程序设计模式!
#12
Design mode is getting better and I'd say that it's likely to become more prevalent as time goes on and the design mode tools continue to improve. I design all my components for design mode, but I still do the large majority of my code by hand - it allows greater control of code layout and doesn't end up creating an auto-formatted mess that I then have to dig through to figure out what changes need making. I know that in future my components are likely going to be used by developers that do most of their design by drag/drop and it's easier to cater for that now than have to come back and do it after the event.
设计模式越来越好,我会说随着时间的推移,它可能会变得更加普遍,设计模式工具也会不断改进。我为设计模式设计了所有组件,但我仍然手工完成大部分代码 - 它允许更好地控制代码布局,并且最终不会创建自动格式化的混乱,然后我必须深入研究需要做出哪些改变。我知道将来我的组件可能会被那些通过拖放操作完成大部分设计的开发人员使用,现在更容易满足这一要求,而不是必须在事件发生后再回来做。
#13
Granted I'm doing MVC stuff, but I never use it - I "grew up" with PHP and code editors, and it still does me just fine.
虽然我正在做MVC的东西,但我从来没有使用过它 - 我在PHP和代码编辑器“长大”,它仍然让我很好。
#14
I'm using two different versions of .NET (2003 & 2005). Some of the forms that were written in 2003 can no longer be edited in 2003 and the installation requires that they be maintained in 2003, so I use KEDIT to edit those forms. Some of the forms in one application are too big for the .NET editor and I prefer a strong editor anyway.
我正在使用两个不同版本的.NET(2003和2005)。 2003年编写的某些表单在2003年无法再编辑,安装需要在2003年进行维护,因此我使用KEDIT编辑这些表单。一个应用程序中的某些表单对于.NET编辑器来说太大了,我更喜欢强大的编辑器。
#15
I have no problem working in design mode. One exception is asp:Repeaters, which are not supported, or GridViews which tend to override my manual column definitions.
在设计模式下工作没问题。一个例外是asp:不支持的Repeater,或者倾向于覆盖我的手动列定义的GridView。
The other is if VS tries to do a full project scan if I rename a control, and then fails.
另一种情况是,如果我重命名控件,VS会尝试执行完整的项目扫描,然后失败。
#16
We primarily use the code view. The design mode is quite buggy we've found in VS 2008. XML controls tend to barf random character sets out for some reason, and VS will generally run slow whilst trying to render everything on screen. I mainly use the code-view.
我们主要使用代码视图。我们在VS 2008中发现了设计模式非常错误。由于某些原因,XML控件往往会出现随机字符集,并且在尝试在屏幕上呈现所有内容时,VS通常会运行缓慢。我主要使用代码视图。
#17
Traditionally WYSIWYG designers produced poor code and render CSS and #INCLUDEd files poorly so they were of limited use, so developers tended to code by hand. In addition, these tools allowed you to go a certain distance without real knowledge of what you were doing, which was fine for web tutorials and personal homepages, but as soon as you wanted an extra degree of control you became unstuck - when meant you had to resort to looking 'under the hood' anyway.
传统上WYSIWYG设计人员生成的代码很差,并且CSS和#INCLUDEd文件的渲染效果很差,因此它们的使用受到限制,因此开发人员倾向于手动编写代码。此外,这些工具允许你在没有真正了解自己正在做的事情的情况下走一段距离,这对于网络教程和个人主页来说很好,但是只要你想要一个额外的控制程度,你就会失败 - 当你意味着你有了无论如何都要求“引擎盖”。
Although tools have improved over time, many developers are so comfortable with hand-coding that they all but forget about the Design View - I certainly can't remember last time I used it. I'm sure there are a number of situations where such tools could be genuinely useful, but we are doing fine without and don't want to be bothered with figuring when & where such features can best be used.
虽然工具随着时间的推移而有所改进,但许多开发人员对手动编码非常熟悉,他们都忘记了设计视图 - 我上次使用时肯定记不起来了。我确信在很多情况下这些工具可能真的很有用,但我们没有做好,也不想在计算何时何地可以最好地使用这些功能时感到困扰。
#18
Our UI is complicated and it is impossible for us to use design mode with VS2005.
我们的UI很复杂,我们不可能在VS2005中使用设计模式。
The only time I have touched design mode is to do a quick and dirty prototype or an internal app.
我接触设计模式的唯一一次是做一个快速而肮脏的原型或内部应用程序。
How often do I not use design mode? 99% of the time.
我多久不使用一次设计模式? 99%的时间。