怎样用Microsoft Visual Studio 2005创建一个网站
2个回答
展开全部
内容提要：
简介
待开发控件的背景介绍
使用Visual Studio 2003开发该自定义控件
使用Visual Studio 2005开发该自定义控件
如何将Visual Studio 2003开发的自定义控件移植到Visual Studio 2005
结论
简介
到目前为止，所有的软件开发者，都应该能够明显的感受到现代的快速应用开发环境给我们的生产效率带来的显著提升。开发者们基于自己的不同目的，使用着不同的开发环境来开发应用。一些是基于Internet的商业应用，一些仅仅是为了牟利，还有一些则是开发者完全免费提供给社区的。但不论开发动机如何，所有这些应用的用户界面的基本组成都是一个个被称为控件的元素。
通过使用在Microsoft Visual Studio称为Windows Forms Designer的窗体设计器，控件可以被快速的对齐、移动、调整大小等等，总而言之，就是开发者能够在设计时即所见即所得的完成他们的开发。应用的用户界面设计完全成了一件艺术，而再不需要过多的技术。窗体设计器提供了一块画布，鼠标就像一把刷子，而控件则成了一个像点、线这样的基本绘图元素。
When a developer uses Microsoft Visual Studio .NET 2003 to create custom controls for smart device applications the process is tedious and error-prone. Creating a custom control that functions solely at run time almost seems trivial. Unfortunately, getting that custom control to properly integrate with the designer can be frustrating for Visual C# developers, and it is not possible for Visual Basic developers. But that was then; now, Visual Studio 2005 has changed the way that developers build design-time support for custom controls.
当一个开发者使用Microsoft Visual Studio .NET 2003为智能设备程序创建自定义控件时，创建过程非常的繁琐且容易出错。不幸的是，要让自定义控件与设计器很好的集成对于C#开发者来说更是一件让人痛苦的事情，而对于VB开发者来说则干脆就是件不可能的事情。不过这都是过去的事了，现在Visual Studio 2005已经改变了为自定义控件开发设计时支持的方式。
待开发控件的背景介绍
Throughout this article, you're going to develop a custom control for Contoso, Ltd. that targets the Pocket PC platform. The general purpose of the control is to display text to the end user and to provide a strong design-time experience for the end developer. The result will be two versions of your control—one compiled against the Microsoft .NET Compact Framework version 1.0 and another compiled against version 2.0. However, because you want the maximum number of Pocket PC developers to be able to use this control, you'll also need to ensure that you have the expected design-time experience in both Visual Studio .NET 2003 and Visual Studio 2005.
This is one of the more complicated scenarios that a custom control developer may encounter because Visual Studio 2005 enables developers to target Windows Mobile 2003–based Pocket PCs with .NET Compact Framework 1.0 and 2.0 project types. What this means to you is that the control needs to support both the old and the new design-time paradigms because Visual Studio 2005 offers the same design-time support to .NET Compact Framework 1.0 project types as it does to the 2.0 project types. The challenge is to provide seamless support to end developers for the versions of the .NET Compact Framework and Visual Studio that are currently on the market.
When developing a custom control or class library, following the Design Guidelines for Class Library Developersis important for the discoverability of types and members in addition to the consistency of fitting in with the .NET Compact Framework.
You should name the control BasicLabel; you should define an AutoSize property that automatically sizes the control to the displayed text at both design time and run time; and you should also define a BorderStyleproperty that allows the border of the control to be modified at both design time and run time. Following the design guidelines that state that a namespace should be constructed from the company name and the technology name, you should use "Contoso.Windows.Forms" as the primary namespace in which the control is defined and use "Contoso.Windows.Forms.Design" as the associated design namespace when you should define any design-time–specific types. With this information, the fully qualified name of the control should beContoso.Windows.Forms.BasicLabel. This name implies that the company (Contoso) is building upon a technology (Windows Forms) by providing a class named BasicLabel that defines a custom control. The basic code definition for your BasicLabel class looks like the following.
简介
待开发控件的背景介绍
使用Visual Studio 2003开发该自定义控件
使用Visual Studio 2005开发该自定义控件
如何将Visual Studio 2003开发的自定义控件移植到Visual Studio 2005
结论
简介
到目前为止，所有的软件开发者，都应该能够明显的感受到现代的快速应用开发环境给我们的生产效率带来的显著提升。开发者们基于自己的不同目的，使用着不同的开发环境来开发应用。一些是基于Internet的商业应用，一些仅仅是为了牟利，还有一些则是开发者完全免费提供给社区的。但不论开发动机如何，所有这些应用的用户界面的基本组成都是一个个被称为控件的元素。
通过使用在Microsoft Visual Studio称为Windows Forms Designer的窗体设计器，控件可以被快速的对齐、移动、调整大小等等，总而言之，就是开发者能够在设计时即所见即所得的完成他们的开发。应用的用户界面设计完全成了一件艺术，而再不需要过多的技术。窗体设计器提供了一块画布，鼠标就像一把刷子，而控件则成了一个像点、线这样的基本绘图元素。
When a developer uses Microsoft Visual Studio .NET 2003 to create custom controls for smart device applications the process is tedious and error-prone. Creating a custom control that functions solely at run time almost seems trivial. Unfortunately, getting that custom control to properly integrate with the designer can be frustrating for Visual C# developers, and it is not possible for Visual Basic developers. But that was then; now, Visual Studio 2005 has changed the way that developers build design-time support for custom controls.
当一个开发者使用Microsoft Visual Studio .NET 2003为智能设备程序创建自定义控件时，创建过程非常的繁琐且容易出错。不幸的是，要让自定义控件与设计器很好的集成对于C#开发者来说更是一件让人痛苦的事情，而对于VB开发者来说则干脆就是件不可能的事情。不过这都是过去的事了，现在Visual Studio 2005已经改变了为自定义控件开发设计时支持的方式。
待开发控件的背景介绍
Throughout this article, you're going to develop a custom control for Contoso, Ltd. that targets the Pocket PC platform. The general purpose of the control is to display text to the end user and to provide a strong design-time experience for the end developer. The result will be two versions of your control—one compiled against the Microsoft .NET Compact Framework version 1.0 and another compiled against version 2.0. However, because you want the maximum number of Pocket PC developers to be able to use this control, you'll also need to ensure that you have the expected design-time experience in both Visual Studio .NET 2003 and Visual Studio 2005.
This is one of the more complicated scenarios that a custom control developer may encounter because Visual Studio 2005 enables developers to target Windows Mobile 2003–based Pocket PCs with .NET Compact Framework 1.0 and 2.0 project types. What this means to you is that the control needs to support both the old and the new design-time paradigms because Visual Studio 2005 offers the same design-time support to .NET Compact Framework 1.0 project types as it does to the 2.0 project types. The challenge is to provide seamless support to end developers for the versions of the .NET Compact Framework and Visual Studio that are currently on the market.
When developing a custom control or class library, following the Design Guidelines for Class Library Developersis important for the discoverability of types and members in addition to the consistency of fitting in with the .NET Compact Framework.
You should name the control BasicLabel; you should define an AutoSize property that automatically sizes the control to the displayed text at both design time and run time; and you should also define a BorderStyleproperty that allows the border of the control to be modified at both design time and run time. Following the design guidelines that state that a namespace should be constructed from the company name and the technology name, you should use "Contoso.Windows.Forms" as the primary namespace in which the control is defined and use "Contoso.Windows.Forms.Design" as the associated design namespace when you should define any design-time–specific types. With this information, the fully qualified name of the control should beContoso.Windows.Forms.BasicLabel. This name implies that the company (Contoso) is building upon a technology (Windows Forms) by providing a class named BasicLabel that defines a custom control. The basic code definition for your BasicLabel class looks like the following.
已赞过
已踩过<
评论
收起
你对这个回答的评价是？
推荐律师服务：
若未解决您的问题，请您详细描述您的问题，通过百度律临进行免费专业咨询
