新项目&设计环境 [英] New Project & Design Environment

问题描述

我的公司刚刚开始使用VB.NET开发一个新项目。

我的问题是，自VS 2005和2.0 Framework发布以来，
即将推出，我们是否应该开始使用Beta版本进行开发？或者

我们应该坚持2003& 1.1框架。 2005年将在

之前发布我们甚至已经完成了该项目的一半，我急于获得一些新功能的优势。


有什么想法吗？


谢谢，

-Matt

解决方案

Matthew，

我会用它来期待花时间更新&测试我的代码每个

VS.NET的临时版本（测试版），加上最终版本。


另外我会采取未知的发布日期将VS.NET 2005纳入考虑范围......


2005年建立它的很酷的事情是你可以在2005年发布的时候发布你的项目

&说看这是2005年，很酷！......


我应该加上一句警告，请记住这是测试版代码，

方法显示，方法消失，即使是新的2005类型我已经注意到了一些过时的成员。


加上一些类/概念被取而代之的是新的（WinBar是

重命名为MenuStrip ...）基于
的线程
microsoft.private.whidbey.windowsforms.databinding DataContainer被删除

支持DataConnector。


取决于您投资的程度。在某些新项目中你可能会有一些时间在临时版本上更新...


此外Beta代码是Beta代码，事情可能只是不工作，一定要报告

错误！


祝你好运&玩得开心！


希望这有帮助

Jay

" Matthew Hood" <否***** @ NoMail.com>在消息中写道

新闻：OV ************** @ tk2msftngp13.phx.gbl ...

我的公司刚刚开始使用VB.NET开发一个新项目。
我的问题是，自从VS 2005和2.0 Framework即将发布以来，我们是否应该开始使用Beta版本进行开发？或者我们应该坚持2003& 1.1框架。 2005年将会发布之前我们甚至已经完成了这个项目的一半，我急于获得一些新功能的优势。

有什么想法？
谢谢，
-Matt

就个人而言，我会采取与Jay相反的方法。

在Beta产品中，方法/对象来来去去，事情会发生变化。

您可能会不断修改代码以使其在每个

版本中保持正常运行。

然后，当

官方2.0框架发布时，你可能会有一个重大的重新工作或至少一个很长的调试周期。

另外，无论多么努力他们试试，最初的

2.0版本中会出现错误。框架是巨大的，一些错误将会漏掉。


如果你在1.1框架上写它，你可以继续前进并制作

确保一切正常。

当2.0 Framework发布时，你可以升级已知的优秀代码，以获得实际需要的改进优势。这比试图升级可疑的beta代码要容易得多，这些代码可能依赖于与正式版本不同或大不相同的东西。

最坏的情况，你在1.1 Framework上发布你的应用程序。然后很快

在2.0 Framework上重新发布你的应用程序。您的客户可能会认为这是一个很好的升级。这比扩展的调试时间表要好得多，并且试图向客户解释为什么有些东西不起作用。由于最终2.0框架中的错误或遗漏，可能是

，并且可能

要求您降级你的软件。客户不喜欢这样。


Gerald


Matthew Hood <否***** @ NoMail.com>在消息中写道

新闻：OV ************** @ tk2msftngp13.phx.gbl ...

我的公司刚刚开始使用VB.NET开发一个新项目。
我的问题是，自从VS 2005和2.0 Framework即将发布以来，我们是否应该开始使用Beta版本进行开发？或者我们应该坚持2003& 1.1框架。 2005年将会发布之前我们甚至已经完成了这个项目的一半，我急于获得一些新功能的优势。

有什么想法？
谢谢，
-Matt

Gerald。

就个人而言，我会采用与Jay相反的方法。
在Beta产品中，方法/对象来来去去，事情会发生变化。
您可能会不断修改代码以使其在每个产品中都有效。
在我看来杰伊写的是什么？
/>

My company is just starting development of a new project using VB.NET.
The question I have is, since the release of VS 2005 and the 2.0 Framework
comming out soon, should we start developing with the Beta version? Or
should we stick to 2003 & the 1.1 framework. 2005 will be released before
we are even halfway done with the project, and I am anxious to take
advantage of some of the new features.

Any thoughts?

Thanks,
-Matt

解决方案

Matthew,
I would use it expecting to take time to update & test my code for each
interim build (beta release) of VS.NET, plus the final build.

Also I would take the unknown release date of VS.NET 2005 into account...

The cool thing about building it for 2005, is you can release you project
when 2005 is released & say "Look this is 2005, cool huh!"...

I should have added a word of caution, remember that this is beta code,
methods show up, methods disappear, even on new 2005 Types I''ve noticed a
handful of Obsolete members.

Plus some classes/concepts are dropped in favor of new ones (WinBar was
renamed MenuStrip...) Based on a thread in
microsoft.private.whidbey.windowsforms.databinding DataContainer was dropped
in favor of DataConnector.

Depending on how heavily you "invested" in some of the new items you may
have some time to update on an interim release...

Also Beta code is Beta code, things may just not work, be certain to report
bugs!

Good luck & have fun!

Hope this helps
Jay
"Matthew Hood" <No*****@NoMail.com> wrote in message
news:OV**************@tk2msftngp13.phx.gbl...

My company is just starting development of a new project using VB.NET.
The question I have is, since the release of VS 2005 and the 2.0 Framework
comming out soon, should we start developing with the Beta version? Or
should we stick to 2003 & the 1.1 framework. 2005 will be released before
we are even halfway done with the project, and I am anxious to take
advantage of some of the new features.

Any thoughts?

Thanks,
-Matt

Personally, I would take the opposite approach from Jay.
In Beta products, methods/objects come and go, things change.
You may be constantly reworking your code to keep it working in each
release.
Then you might have a major re-work or at least a long debug cycle when the
official 2.0 Framework is released.
Additionally, no matter how hard they try, there will be bugs in the initial
2.0 release. The Framework is massive and some bugs will slip through.

If you write it on the 1.1 Framework, you could just keep going and make
sure everything works.
When the 2.0 Framework is released, you can upgrade known good code to take
advantage of the improvements you actually need. This is far easier than
trying to upgrade questionable beta code that may rely on things that are
not in or substantially different than the official release.
Worst case, you release your app on 1.1 Framework. Then very quickly
re-release your app on the 2.0 Framework. You customers might perceive this
as a good upgrade. This is much better than an extended debug schedule and
trying to explain to your customers why something doesn''t work. It might be
due to a bug or something missing in the final 2.0 Framework and might
require you to "downgrade" your software. Customers don''t like that.

Gerald

"Matthew Hood" <No*****@NoMail.com> wrote in message
news:OV**************@tk2msftngp13.phx.gbl...

My company is just starting development of a new project using VB.NET.
The question I have is, since the release of VS 2005 and the 2.0 Framework
comming out soon, should we start developing with the Beta version? Or
should we stick to 2003 & the 1.1 framework. 2005 will be released before
we are even halfway done with the project, and I am anxious to take
advantage of some of the new features.

Any thoughts?

Thanks,
-Matt

Gerald.

Personally, I would take the opposite approach from Jay.
In Beta products, methods/objects come and go, things change.
You may be constantly reworking your code to keep it working in each
release.

In my opinion is that what Jay wrote?

Cor

这篇关于新项目&amp;设计环境的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！