如何提前为asp.net 2.0发布做好准备？ [英] How to best prepare for asp.net 2.0 release in advance?

问题描述

大家好，


我花了几个月的时间使用

Beta 2开发我的ASP.NET 2.0网站，以及它的工作原理很棒。


即使2.0 beta 2有Go Live许可证，我还没有部署到

产品。这是一个全新的网站，所以我想等待，并且只需要在最终版本为2.0的情况下进行
部署，现在只需要几个星期的b
。 />

然而，一旦2.0发布，我就开始使用新网站是至关重要的，因为我想尽可能多地为这个网站做准备发布版本

提前。以下是我希望能帮助我做好准备的问题：


1）代码的结构/体系结构是否需要更改

后面创建的页面Beta 2？我似乎记得读过一些关于

需要在页面后面重做代码以适应某种新格式的东西。这是

案例，如果是这样的话我在哪里可以了解更多信息？将转换向导

来处理这个问题，还是我需要手动执行此操作？我在这里阅读了这篇

的文章
http://msdn.microsoft.com/asp.net/be...s/default.aspx 但是

没有说什么除了将
类移到特殊文件夹之外的代码后面的更改。


2）有谁知道最终的发货版本是否与

发布Candiate（RC发布与RTM相同），或者RC和最终版本之间是否有任何变化？

3）通用MSDN用户是否可以在11月7日发布之前获得最终发货版本

，即使他们无法使用它？

我想再次把服务器上的所有内容都设置好，这样我们就可以立即上线，然后我就可以将网站公之于众，并且go

live。


4）贝西des本文中列出的内容
http ：//msdn.microsoft.com/asp.net/be...s/default.aspx

有任何其他考虑因素或陷阱我应该注意吗？


5）你认为我们能够安全清楚地删除RC构建

并在可用时安装最终版本？我很犹豫要安装RC

，因为我害怕不知何故我最终需要重建

我的盒子才能运行最终版本。


谢谢！


Steve

Hi all,

I''ve spent the past several months developing my ASP.NET 2.0 web site using
Beta 2, and its working great.

Even though 2.0 beta 2 has a Go Live license, I have not deployed to
production yet. It is a brand new web site so I want to wait and just
deploy with the final release of 2.0 now that it is coming in just a couple
weeks.

However it is critical that I go live with the new site as soon as 2.0 is
released as I''d like to prepare as much as possible for the released version
in advance. Here are questions I am hoping will help me prepare better:

1) Will there be changes required to the structure/architecture of code
behind pages created in Beta 2? I seem to recall reading something about
needing to redo code behind pages to fit into some new format. Is this the
case, and if so where can I learn more about it? Will a conversion wizard
take care of this or will I need to do this by hand? I read through this
article here
http://msdn.microsoft.com/asp.net/be...s/default.aspx but it
didn''t say anything about changes to code behind other than it moving
classes to a special folder.

2) Does anyone know if the final shipping version will be identical to the
Release Candiate (is the RC release the same as RTM), or whether there have
been any changes made between the RC and final builds?

3) Will Universal MSDN subscribers have access to the final shipping version
any point before release on Nov 7, even if they cannot go live with it?
Again I want to get everything on the server and set up so that as soon as
we are permited to go live I can make the site publicly accessible and "go
live".

4) Besides what is listed in this article
http://msdn.microsoft.com/asp.net/be...s/default.aspx are
there any other considerations or "gotchas" I should watch out for?

5) Do you think we will be able to safely and clearly remove the RC build
and install the final build when available? I''m hesitant to install RC
because I dread the thought that somehow I could wind up needed to rebuild
my box in order to run the final version.

Thanks!

Steve

推荐答案

> 5）像Kevin说的那样，我现在尝试转移到RC - 但我不会把

> 5) Like Kevin said, I''d try moving to the RC now - but I wouldn''t put

放在生产机器附近，除非你准备重新格式化并从
开始从头开始获取RTM版本。尝试一台备用机器或一台虚拟PC。

it near a production machine unless you are prepared to reformat and
start from scratch to get the RTM version on. Try a spare machine or a
Virtual PC.

根据你的回复我应该假设如果我把RC版本放在我的
上
dev box我可能需要重新格式化并从头开始让RTM运行

呢？我肯定会想要避免这种情况。


我对虚拟PC一点都不熟悉，但这听起来是个好主意。

有些是什么更受欢迎的产品呢？我尝试使用谷歌搜索，但

似乎只提出了MS获得的产品的参考名称

Virtual PC - 但这听起来像是与Mac有关，而我不要
运行Macs。


最后 - 我非常有信心我没有使用任何API />
从Beta 2更改或删除到RTM。然而，我仍然想知道（基于我一个月前读过的东西是
）如果我将不得不重新编码或更改我的代码页面后面的

结构一些新的格式或构造。

这有什么道理吗？如果是这样，VS.NET会为我转换后面的代码吗？

希望它可以做很多手动重新编写。无论如何，你能告诉我b $ b这是真的吗？谢谢。


史蒂夫

Based on your reply should I assume then that if I put the RC build on my
dev box I may have to reformat and start from scratch to get the RTM to run
on it as well? I definately would want to avoid that.

I am not familiar at all with virtual PCs but it sounds like a great idea.
What are some of the more popular products to do this? I tried googling but
only seem to come up with references to a product acquired by MS called
Virtual PC - however that sounds like it had to do with Macs, and I don''t
run Macs.

Lastly - I''m quite confident that I''m not using any of the APIs that were
changed or deleted from Beta 2 to RTM. However I''m still wondering (based
on something I read a month ago) if I will have to recode or change the
structure of my code behind pages due to some new format or construct. Is
there any truth to this? If so does VS.NET convert the code behind for me?
Hope it does as that would be a lot of manual re-working. Anyway can you
let me know if ths is true? Thanks.

Steve

我没有看到重新格式化或者从头开始是必要的。首先，你的开发盒上的
，只要你正确卸载所有以前的

安装，根据Readme.htm文件中的说明为

新安装，你应该没有任何麻烦安装新的

。这是来自安装了至少3个不同测试版本（一个测试版1和两个测试版2）的RC版本以及在工作时我的开发框上的RC版本。在家。只有当自述文件不严格遵循
时才会出现问题。这些都可以解决。我从来没有必要重新格式化。


其次，就部署平台而言，你只需安装框架即可。
。您需要做的就是卸载以前的

版本的Framework并安装新版本。框架安装

在VS.Net安装CD上。再一次，我已多次这样做了

没有发生任何事故。


重要的是要注意框架不会改变你的运营

系统。它在运行时访问操作系统。它在安装时注册了一个数量为
的COM组件。并且它在安装时向IIS添加了一些信息

元数据库。


-

HTH，


Kevin Spencer

Microsoft MVP

..Net开发人员

歧义具有一定的品质。


" Steve Franks" < PL **** @ postreplyhere.com>在消息中写道

新闻：Y - ******************** @ comcast.com ...

I don''t see reformatting OR starting from scratch as being necessary. First,
on your dev box, as long as you correctly uninstall all previous
installations, according to the instructions in the Readme.htm files for the
new installation, you should have no trouble whatsoever with the new
installation. This is coming from someone who has installed at least 3
different beta versions (one beta 1 and two beta 2s) and the RC version on
my dev box at work and at home. Issues only arise when the readme is not
strictly followed. And these can be remedied. I have NEVER had to reformat.

Secondly, as far as the deployment platform is concerned, you''re only
installing the Framework. All you need to do is uninstall the previous
version of the Framework and install the new version. The Framework install
is on the VS.Net installation CD. Again, I have done this numerous times
without incident.

It is important to note that the Framework does not change your Operating
System. It accesses the Operating System at run-time. It registers a number
of COM components on install. And it adds some information to the IIS
metabase on install.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Ambiguity has a certain quality to it.

"Steve Franks" <pl****@postreplyhere.com> wrote in message
news:Y-********************@comcast.com...

5）像Kevin说的那样，我现在会尝试转移到RC - 但除非你准备重新格式化，否则我不会把它放在生产机器附近/>从头开始获取RTM版本。尝试一台备用机器或一台虚拟PC。

5) Like Kevin said, I''d try moving to the RC now - but I wouldn''t put
it near a production machine unless you are prepared to reformat and
start from scratch to get the RTM version on. Try a spare machine or a
Virtual PC.

根据你的回复我应该假设如果我把RC版本放在我的开发盒上，我可以必须重新格式化并从头开始以使RTM在其上运行？我肯定会想要避免这种情况。

我对虚拟PC一点也不熟悉，但这听起来很棒。有哪些更受欢迎的产品可以做到这一点？我试过谷歌搜索，但似乎只提出了被称为Virtual PC的MS获得的产品 - 但这听起来像是与Mac有关，
我不是运行Mac。

最后 - 我非常有信心我没有使用任何从Beta 2更改或删除到RTM的API。然而，我仍然想知道（基于我一个月前读过的内容），如果由于一些新的格式或构造，我将不得不重新编码或更改我的代码页面背后的结构。这有什么道理吗？如果是这样的话，VS.NET会转换后面的代码吗？希望它确实如此，那将是很多手动重新工作。无论如何可以告诉我，如果这是真的吗？谢谢。

Steve

Based on your reply should I assume then that if I put the RC build on my
dev box I may have to reformat and start from scratch to get the RTM to
run on it as well? I definately would want to avoid that.

I am not familiar at all with virtual PCs but it sounds like a great
idea. What are some of the more popular products to do this? I tried
googling but only seem to come up with references to a product acquired by
MS called Virtual PC - however that sounds like it had to do with Macs,
and I don''t run Macs.

Lastly - I''m quite confident that I''m not using any of the APIs that were
changed or deleted from Beta 2 to RTM. However I''m still wondering (based
on something I read a month ago) if I will have to recode or change the
structure of my code behind pages due to some new format or construct. Is
there any truth to this? If so does VS.NET convert the code behind for
me? Hope it does as that would be a lot of manual re-working. Anyway can
you let me know if ths is true? Thanks.

Steve

On Sun，2005年10月23日08:03:34 -0400，Steve Franks

< pl **** @ postreplyhere.com>写道：

On Sun, 23 Oct 2005 08:03:34 -0400, "Steve Franks"
<pl****@postreplyhere.com> wrote:

我对虚拟电脑一点都不熟悉，但这听起来是个好主意。
有哪些比较流行的产品可以做到这一点？我尝试使用谷歌搜索，但似乎只提出了被MS收购的名为
Virtual PC的产品 - 但这听起来像是与Mac有关，而且我不是
运行Macs。


是的，MS Virtual PC是一款出色的产品，适用于Windows PC。

最后 - 我很有信心我''我没有使用任何从Beta 2更改或删除到RTM的API。然而，我仍然想知道（基于我一个月前读过的内容），如果由于一些新的格式或构造，我将不得不重新编码或更改我的代码页面背后的结构。这有什么道理吗？如果是这样的话，VS.NET会为我转换代码吗？
希望它可以做很多手动重新编写。无论如何，你能告诉我这是真的吗？谢谢。

I am not familiar at all with virtual PCs but it sounds like a great idea.
What are some of the more popular products to do this? I tried googling but
only seem to come up with references to a product acquired by MS called
Virtual PC - however that sounds like it had to do with Macs, and I don''t
run Macs.

Yes, MS Virtual PC is a great product and works on Windows PCs.
Lastly - I''m quite confident that I''m not using any of the APIs that were
changed or deleted from Beta 2 to RTM. However I''m still wondering (based
on something I read a month ago) if I will have to recode or change the
structure of my code behind pages due to some new format or construct. Is
there any truth to this? If so does VS.NET convert the code behind for me?
Hope it does as that would be a lot of manual re-working. Anyway can you
let me know if ths is true? Thanks.

添加了很多功能[1]，但我不知道任何会破坏代码的结构性改变。

http：// msdn.microsoft.com/asp.net/be...s/default.aspx


-

Scott
http://www.OdeToCode.com/blogs/scott/

这篇关于如何提前为asp.net 2.0发布做好准备？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！