微软在想什么？ [英] What the hell was Microsoft thinking?
问题描述
Hello everyone，
我是ASP.Net网站的首席开发人员。我们有超过150个b $ b应用程序在我们的网站上运行。每个应用程序都是VS中的解决方案
。当我们滚动到测试和生产时，主dll被滚动到站点单个bin目录和aspx，asmx等文件是
滚动到服务器上的各个文件夹。
现在使用ASP.Net 2.0他们改变了一切。不再是一个网站
项目项目，它是一个网站。每次发布时，dll名称都会被修改并重命名为
。过去只是引用的部分现在是部分
的soruce控件，好像我想在sourcesafe中编译dll！
总而言之，两周之后我希望转向ASP.net 2.0，我会说它不会发生！他们管理了一个像我们这样不可能的大型，多元化的网站。当然，微软给了我们很多
" Wiz Bang"小伙子的东西，但真的搞了大规模的b $ b网站开发者，或者至少看起来对我的团队来说。
总而言之，我认为微软真的把这个狗搞砸了。
L. Lee Saunders
Hello Everyone,
I''m a lead developer of a ASP.Net site. We have over 150
"applications" running at our site. Each application is a "Solution"
in VS. When we roll to test and production, the main dlls are rolled
to the sites single bin directory and the aspx, asmx etc files are
rolled to various folders on the server.
Now with ASP.Net 2.0 they changed everything. No longer is a web
project a project, its a SITE. The dll names are mangled and renamed
every time its published. What used to be just references are now part
of the soruce control, as if I want compiled dlls in sourcesafe!
All told, after two weeks of looking to move to ASP.net 2.0, I''ll have
to say that "It will not happen!" They have made managing a large,
diverse site like ours impossible. Sure, Microsoft gave us lots of
"Wiz Bang" stuff for the kiddies, but really screwed the large scale
site developers, or so it at least seems to my team.
All told, I think that Microsoft REALLY screwed the pooch on this one.
L. Lee Saunders
推荐答案
哇！抓住你的马。
下载并安装Web部署项目插件：
http://msdn.microsoft.com/asp.net/re...p/default.aspx
"这个加载项包含一个新工具，可以让你合并
在ASP.NET 2.0预编译期间创建的程序集
Juan T. Llibre，ASP.NET MVP
ASP.NET常见问题解答： http://asp.net.do/faq/
ASPNETFAQ.COM： http://www.aspnetfaq.com/
Foros de ASP.NET en Espa？ol： http://asp.net.do/foros/
======================================
< sa * *****@hotmail.com>在消息中写道
news：11 ********************* @ g44g2000cwa.googlegro ups.com ...
Whoa! Hold your horses.
Download and install the Web Deployment Projects add-in :
http://msdn.microsoft.com/asp.net/re...p/default.aspx
"This add-in includes a new tool that enables you to merge
the assemblies created during ASP.NET 2.0 precompilation"
Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
ASPNETFAQ.COM : http://www.aspnetfaq.com/
Foros de ASP.NET en Espa?ol : http://asp.net.do/foros/
======================================
<sa******@hotmail.com> wrote in message
news:11*********************@g44g2000cwa.googlegro ups.com...
大家好，
我是ASP.Net网站的首席开发人员。我们有超过150个应用程序在我们的网站上运行。每个应用程序都是VS中的解决方案。当我们滚动到测试和生产时，主dll被滚动到站点单个bin目录，aspx，asmx等文件被滚动到服务器上的各个文件夹。
现在使用ASP.Net 2.0他们改变了一切。网站不再是一个项目，它是一个网站。每次发布时，dll名称都会被修改并重命名。以前只是引用的部分现在是soruce控件的一部分，就好像我想在sourcesafe中编译dll一样！
所有人都说，经过两周的转移到ASP.net 2.0之后，我会说它不会发生！他们已经使像我们这样的大型，多样化的网站无法管理。当然，微软给了我们很多的Wiz Bang。小伙子的东西，但真的搞砸了大规模的网站开发者，或者至少对我的团队来说似乎是这样。
总而言之，我认为微软真的搞砸了这个小狗。
L. Lee Saunders
Hello Everyone,
I''m a lead developer of a ASP.Net site. We have over 150
"applications" running at our site. Each application is a "Solution"
in VS. When we roll to test and production, the main dlls are rolled
to the sites single bin directory and the aspx, asmx etc files are
rolled to various folders on the server.
Now with ASP.Net 2.0 they changed everything. No longer is a web
project a project, its a SITE. The dll names are mangled and renamed
every time its published. What used to be just references are now part
of the soruce control, as if I want compiled dlls in sourcesafe!
All told, after two weeks of looking to move to ASP.net 2.0, I''ll have
to say that "It will not happen!" They have made managing a large,
diverse site like ours impossible. Sure, Microsoft gave us lots of
"Wiz Bang" stuff for the kiddies, but really screwed the large scale
site developers, or so it at least seems to my team.
All told, I think that Microsoft REALLY screwed the pooch on this one.
L. Lee Saunders
VS小组决定停止与asp.net编译器作战。 VS2005现在使用
asp.net编译器来构建所有asp.net站点。这就是为什么VS有一个
发布网站命令来构建一个干净的目录，需要部署的是什么。
在1.1 VS构建1 dll后面的代码，而asp.net每页构建一个dll
但隐藏它的临时性。在v2中，VS使用asp.net编译器来预编译
站点，这样就可以看到所有的页面dll。
请参阅aspnet_compiler文档，看看是什么您的自动构建
选项是。看看fixednames选项。
- 布鲁斯（sqlwork.com）
< sa ****** @ hotmail.com>在消息中写道
news：11 ********************* @ g44g2000cwa.googlegro ups.com ...
the VS group decided to stop battling the asp.net compiler. VS2005 now uses
the asp.net compiler to build all asp.net sites. this is why VS has a
Publish web site command that builds a clean dir tith what needs to be
deployed.
in 1.1 VS build 1 dll for the code behind, and asp.net build a dll per page
but hide it a temp. in v2, VS uses the asp.net compiler to precompile the
site, so you see all the page dlls.
see the aspnet_compiler documentation to see what your automated build
options are. look at fixednames option.
-- bruce (sqlwork.com)
<sa******@hotmail.com> wrote in message
news:11*********************@g44g2000cwa.googlegro ups.com...
大家好，
我是ASP.Net网站的首席开发人员。我们有超过150个应用程序在我们的网站上运行。每个应用程序都是VS中的解决方案。当我们滚动到测试和生产时，主dll被滚动到站点单个bin目录，aspx，asmx等文件被滚动到服务器上的各个文件夹。
现在使用ASP.Net 2.0他们改变了一切。网站不再是一个项目，它是一个网站。每次发布时，dll名称都会被修改并重命名。以前只是引用的部分现在是soruce控件的一部分，就好像我想在sourcesafe中编译dll一样！
所有人都说，经过两周的转移到ASP.net 2.0之后，我会说它不会发生！他们已经使像我们这样的大型，多样化的网站无法管理。当然，微软给了我们很多的Wiz Bang。小伙子的东西，但真的搞砸了大规模的网站开发者，或者至少对我的团队来说似乎是这样。
总而言之，我认为微软真的搞砸了这个小狗。
L. Lee Saunders
Hello Everyone,
I''m a lead developer of a ASP.Net site. We have over 150
"applications" running at our site. Each application is a "Solution"
in VS. When we roll to test and production, the main dlls are rolled
to the sites single bin directory and the aspx, asmx etc files are
rolled to various folders on the server.
Now with ASP.Net 2.0 they changed everything. No longer is a web
project a project, its a SITE. The dll names are mangled and renamed
every time its published. What used to be just references are now part
of the soruce control, as if I want compiled dlls in sourcesafe!
All told, after two weeks of looking to move to ASP.net 2.0, I''ll have
to say that "It will not happen!" They have made managing a large,
diverse site like ours impossible. Sure, Microsoft gave us lots of
"Wiz Bang" stuff for the kiddies, but really screwed the large scale
site developers, or so it at least seems to my team.
All told, I think that Microsoft REALLY screwed the pooch on this one.
L. Lee Saunders
2005年11月11日13:03:00 -0800， sa ****** @ hotmail.com 写道：
On 11 Nov 2005 13:03:00 -0800, sa******@hotmail.com wrote:
全部告知，经过两周的希望转向ASP.net 2.0，我会说它不会发生！他们已经使像我们这样的大型，多样化的网站无法管理。当然，微软给了我们很多的Wiz Bang。小伙子的东西，但真的搞砸了大规模的网站开发者，或者至少对我的团队来说似乎是这样。
总而言之，我认为微软真的搞砸了这个小狗。
All told, after two weeks of looking to move to ASP.net 2.0, I''ll have
to say that "It will not happen!" They have made managing a large,
diverse site like ours impossible. Sure, Microsoft gave us lots of
"Wiz Bang" stuff for the kiddies, but really screwed the large scale
site developers, or so it at least seems to my team.
All told, I think that Microsoft REALLY screwed the pooch on this one.
不要把受害者归咎于此，但微软已经制作了这些东西
大约两年了，*现在*，发货后，你说嘿，
等一下，这对我不起作用。也许你应该对之前需要的更改进行调查，然后你可以在他们最终确定产品之前向微软提供
反馈。
好的，现在我已经把它放在胸前了（对不起，当人们提前几年获得这些信息时，它只会让我感到烦恼，然后他们就会知道
投诉太晚了。
您可能想阅读这篇文章（巧合的是，它还显示了
如何参与这个过程让你积极主动地获得你需要的b $ b b。它还解释了他们的想法。
http://www.dotnetnuke.com/Community/...5/Default.aspx
这篇关于微软在想什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
