ASP.NET开发 [英] ASP.NET Development

问题描述

作为一名顾问公司的ASP开发人员，考虑开始使用ASP.NET进行开发我已经在论坛上阅读了数百个网页和帖子

互联网了解我们需要什么才能适应.b $ b适应。我已经阅读过Microsofta的一个用Visual Studio .NET进行的团队开发

和Visual SourceSafea ??并试图建立一个开发环境，因为建议使用a ??隔离模式？
。但是，关于

开发环境以及技术本身的许多问题仍然无法回答。我试着在这里总结其中一些，希望有人能够给我一些我无法找到自己的答案。


1.开发

我无法理解推荐的模型如何在应用程序部署在
应用程序/>
用IIS 6赢取2003 Server。对我来说这肯定会引起问题。在

添加 - 安全设置，安装的软件等可能会因不同的开发人员工作站以及不同的服务器而异。


2.部署

微软自豪地宣传a ?? x-copya ?? - 部署，但考虑到一个新的Web应用程序，他们似乎没有... b $ b部署了x-copy wona ?? t运行没有

手动更改IIS中的设置。

a ??复制projecta ?? - 功能似乎大多是一个笑话我。在阅读了关于FPSE安全问题的
后，我甚至会考虑将其安装在公共的
网络服务器上，以便留下文件共享选项当然不是什么颜色

else但x-copy包含一些文件类型排除项。他们如何决定不包括
包括FTP作为一个选项超出了我的理解。

所以，我留下了一些叫做Web安装项目的东西。但是从我理解的内容来看，他们不能安装在localhost以外的任何东西上。在其他

字样中，我不能在托管多个网站的服务器上使用它。


3.使用多个网站

我们是一家咨询公司，我们与多个网站合作，为不同的客户提供许多b
。也许我不明白我们应该如何建立

环境，但我们倾向于为我们合作的网站提供一个解决方案。

网站发布后，我们的大部分工作都包含相对较少的b $ b b b变化和修复。不得不在不同的

解决方案之间快速跳转并且似乎无休止地等待每次加载的解决方案

我们需要做出微小的改变，感觉浪费宝贵的时间和

钱。


4.测试和调试

提到我们经常做一些小改动？移动到ASP.NET感觉

因为制作和测试这些更改的时间将大大增加

所需的时间。首先，整个项目必须加载到

VS.NET中。然后我对文件后面的代码进行了一些更改，这将导致整个项目需要重新编译的结果为
。编辑将需要发生

每次我测试一个从未如此小的变化，我将不得不等待至少

15-20秒才能查看变化。如果Ia ??我满意

的更改（在我的本地开发工作站上测试）我将不得不使用我们的VSS数据库作为源代码在测试服务器上编译它。如果我们认为它是功能性的，我将以某种方式尝试将其部署到公共网站

服务器。


我认真对待想知道微软是否真的认为VS.NET用于开发和维护许多小型网络项目。

Being a ASP developer for a consultant company thinking of starting
developing with ASP.NET I have read literally hundreds of web pages and posts
in discussion forums on the Internet to get an idea of what we will need to
adapt to. I have read Microsofta??s a??Team Development with Visual Studio .NET
and Visual SourceSafea?? and tried to set up a development environment as
recommended using the a??Isolated modela??. However, many questions regarding the
development environment as well as the technique itself still remain
unanswered. Ia??ll try to summarize some of them here and hopefully someone
will be able to give me the answers I cana??t find myself.

1. Development
I simply cannot understand how the recommended model can be to develop an
application on Win XP with IIS 5 when the application is to be deployed on a
Win 2003 Server with IIS 6. To me this is bound to cause problems. In
addition - security settings, installed software etc. is likely to vary on
different developer workstations as well as on different servers.

2. Deploying
Microsoft proudly promotes the a??x-copya??-deployment but they havena??t seemed
to consider that a new web application deployed with x-copy wona??t run without
manually changing settings in the IIS.
The a??Copy projecta??-functionality seems mostly as a joke to me. Having read
about FPSE security issues I wouldna??t even consider installing it on a public
web server so that leaves the file share option which of course is nothing
else but x-copy with some file type exclusions. And how they decided not to
include FTP as an option is beyond my understanding.
So, Ia??m left with something called Web setup projects. But from what I
understand, they wona??t install under anything else than localhost. In other
words I cannot use it on servers hosting multiple web sites.

3. Working with multiple web sites
We are a consultant company and we work with multiple web sites for many
different clients. Maybe I havena??t understood how we should set up the
environment but we are leaning towards having one solution for each one of
the web sites we work with.
After a web site is released the majority of our work consists of relatively
small changes and fixes. Having to quickly jump between the different
solutions and waiting seemingly endlessly for the solution to load every time
we need to make small changes feels as a terrible waste of valuable time and
money.

4. Testing and debugging
Having mentioned that we often make small changes a?? moving to ASP.NET feels
as the time for making and testing these changes will dramatically increase
the time needed. First of all the entire project will have to load into
VS.NET. Then I make some changes to a code behind file which will result in
the entire project will need recompiling. The compilation will need to occur
every time I test a never so small change and I will have to wait at least
15-20 seconds before I will be able to view the changes. When Ia??m satisfied
with the changes (tested on my local development workstation) I will have to
compile it on a testing server using our VSS database as source and if we
consider it to be functional I will somehow try to deploy it to a public web
server.

I seriously wonder if Microsoft really has considered VS.NET to be used for
developing and maintaining many small web projects.

推荐答案

＃1。 .NET代码在构建一次运行任何地方
部门中远远超过Java。任何尝试部署JSP servlet的人都知道我正在谈论的是什么。

你只需构建一次.NET代码就可以在任何地方运行。我认为我能想到的唯一主要的因素是关于Server.MapPath。在Windows 2003上

它最后没有附加/所以如果你没有检查它，那么与EndsWith一起存在
并且如果它不存在则追加它你的应用程序

可能有问题。

任何其他编程问题都可能与最初的有缺陷的设计有关。

这实际上取决于你要去的地方

但是在大多数情况下我可以在xp pro上开发web应用程序和

部署到任何支持.net的MS旗舰服务器系统，2k，xp

pro和2k3服务器


＃2 X-copy在这里工作得非常好。什么x-copy不做它是

不是x-configure注意单词copy而不是在x-copy实用程序的

名称中配置。您仍然必须设置和配置您的IIS

应用程序。

＃3 - 如果您的解决方案需要很长时间才能加载我会建议您

买更好的硬件。我使用1.5GB内存的旧AMD XP 1800开发。

200+文件Web项目需要20-30秒才能加载。大多数其他

项目几乎是即时的。有足够的时间将标签替换为另一个

应用程序，聊天或排队一些音乐。

＃4 - 测试和调试。与我调试过的任何其他网络平台相比，测试和调试.net应用程序是一个很好的魅力。

与Source Safe的集成是错误的但是我的所有源代码都是安全的

集成有问题，你学习使用你选择的源安全

，我的选择不是真正的VSS。我更喜欢CVS，

但这只是我的偏好。与部署和调试相关我

喜欢它。我唯一希望看到的是远程调试更可靠，但是我很少需要远程调试，因为任何问题通常都会发生发生在dev

机器上。

不确定你的体验是什么，但我一直在使用asp，

php，jsp而且我已经涉足到CF.对我来说，在所有语言和

框架中，asp.net是迄今为止功能最丰富的功能，它带来了桌面及其开发产品。 YMMV


我个人认为，一旦你理解了OOP和新的.NET架构背后的基本概念，你会感激地抛弃

你的PHP / ASP包含文件hacks并拥抱.NET推出的新的可重用性模型

。

#1. .NET Code far surpasses Java in the "build once run anywhere
department". Anybody that has ever tried to deploy JSP servlets knows
what I am talking about.
You build .NET code once and it runs anywhere. I think the only major
discrepancy I can think of is regarding Server.MapPath. On windows 2003
it does not append a / at the end so if you do not do a check for it to
exist with EndsWith and append it if it is not there your application
may fault.
Any other programming issues that come up very well could be related to
an initial flawed design. It really depends upon where you are going
but for the most part i can develop web applications on xp pro and
deploy to any of MS flagship server systems that support .net, 2k, xp
pro and 2k3 server

#2 X-copy works absolutely fine here. What x-copy DOES NOt do is it
does not "x-configure" notice the word copy and not configure in the
name of the x-copy utility. You must still setup and configure your IIS
application.
#3 - If your solution takes a long time to load I would recommend you
buy better hardware. I develop on an old AMD XP 1800 with 1.5GB of ram.
a 200+ file web project takes 20-30 seconds to load. Most other
projects are almost instantaneously. Enough time to alt tab to another
application, chit chat or queue up some music.
#4 - Testing and debuggin. Testing and debugging .net applications is a
charm compared to any other web platform I have debugged for.
Integration with Source Safe is buggy but imho all source safe
integration has its problems and you learn to work with the source safe
of your choice, and my choice is not really VSS. i prefer CVS over it,
but that is just my preference. Related to deploying and debugging I
love it. The only thing I would like to see is Remote debugging to be
more reliable, however I have so seldom ever had a need for remote
debugging as any problem that occurs usually happens on the dev
machine.
Not really sure what your experience is but I''ve been working with asp,
php, jsp and i''ve dabbled with CF. For me, Of all the languages and
frameworks available asp.net is by far the most feature rich both in
what it brings to the table and its development offerings. YMMV

I personally think that once you understand the fundemental concepts
behind OOP and the new .NET architecture you will thankfully cast aside
your PHP/ASP include file hacks and embrace the new reusability model
that .NET promotes.

Linus写道：

作为一名顾问公司的ASP开发人员，考虑开始使用ASP.NET进行开发我已经在互联网的论坛上阅读了数百个网页和帖子。了解我们需要适应什么。我已经阅读过Microsofta的一个用Visual Studio .NET进行的团队开发
和Visual SourceSafea ??并尝试建立一个开发环境，建议使用a ??隔离模式??但是，关于
开发环境以及技术本身的许多问题仍然没有答案。我试着在这里总结其中的一些，希望有人能够给我答案，我找不到自己。

1.发展
我当应用程序要部署在带有IIS 6的Win 2003服务器上时，根本无法理解推荐的模型如何在带有IIS 5的Win XP上开发应用程序。对我来说，这必然会导致问题。
另外 - 安全设置，安装的软件等可能会因不同的开发人员工作站以及不同的服务器而异。


使用.net，你从操作系统和网络服务器中删除了一步：IIS传递了一个aspx进程的aspx页面请求
。只要

（W2k3和XP）版本的功能相同，就应该没有问题。

2.部署
微软自豪地宣传了这个问题。 x-copya ?? - 部署但他们似乎没有考虑使用x-copy部署的新Web应用程序运行而无需手动更改IIS中的设置。
a ??复制projecta ?? - 功能似乎对我来说大多是个玩笑。阅读了有关FPSE安全问题的内容后，我甚至会考虑将其安装在公共的Web服务器上，以便保留文件共享选项，当然这不是什么，而是x-copy with一些文件类型排除。他们如何决定不包括FTP作为一种选择是我无法理解的。
所以，我留下了一些叫做Web安装项目的东西。但是从我理解的内容来看，他们不能安装在localhost以外的任何地方。换句话说，我不能在托管多个网站的服务器上使用它。


普通xcopy对于网站来说有点困难。我们做什么：首先在网站上创建

（在IIS中），然后复制所有内容。 （使用复制项目从

开发到测试/暂存，然后使用ftp复制到外部
直播服务器）。注意web.config，因为该文件可能包含

网站特定信息。

3.使用多个网站
我们是一家咨询公司，我们为许多不同的客户提供多个网站。也许我不明白我们应该如何建立
环境，但我们倾向于为我们合作的每个网站提供一个解决方案。
一个网站之后是发布我们的大部分工作包括相对较小的变化和修复。不得不在不同的解决方案之间快速跳转并且无休止地等待每次加载解决方案
我们需要进行小的改变，感觉浪费宝贵的时间和金钱。


每个站点一个解决方案（加上可能更多的框架代码解决方案）

似乎是要走的路。

4测试和调试
已经提到我们经常做一些小改动了？移动到ASP.NET感觉
因为制作和测试这些更改的时间将大大增加所需的时间。首先，整个项目必须加载到VS.NET中。然后我对文件后面的代码进行了一些更改，这将导致整个项目需要重新编译。每次我测试一个从未如此小的变化时，都需要进行编译。在我能够查看更改之前，我必须至少等待15-20秒。当我对变化感到满意（在我的本地开发工作站上测试）时，我将不得不使用我们的VSS数据库作为源代码在测试服务器上编译它，如果我们考虑它为了实现功能，我将以某种方式尝试将其部署到公共Web服务器上。

我真的很想知道Microsoft是否真的考虑过将VS.NET用于开发和维护许多小型网络项目。

Being a ASP developer for a consultant company thinking of starting
developing with ASP.NET I have read literally hundreds of web pages and posts
in discussion forums on the Internet to get an idea of what we will need to
adapt to. I have read Microsofta??s a??Team Development with Visual Studio .NET
and Visual SourceSafea?? and tried to set up a development environment as
recommended using the a??Isolated modela??. However, many questions regarding the
development environment as well as the technique itself still remain
unanswered. Ia??ll try to summarize some of them here and hopefully someone
will be able to give me the answers I cana??t find myself.

1. Development
I simply cannot understand how the recommended model can be to develop an
application on Win XP with IIS 5 when the application is to be deployed on a
Win 2003 Server with IIS 6. To me this is bound to cause problems. In
addition - security settings, installed software etc. is likely to vary on
different developer workstations as well as on different servers.
With .net you are one step removed from OS and webserver: IIS passes
a request for an aspx page to the aspnet process. As long as both
(W2k3 and XP) versions function the same, there should be no problem.

2. Deploying
Microsoft proudly promotes the a??x-copya??-deployment but they havena??t seemed
to consider that a new web application deployed with x-copy wona??t run without
manually changing settings in the IIS.
The a??Copy projecta??-functionality seems mostly as a joke to me. Having read
about FPSE security issues I wouldna??t even consider installing it on a public
web server so that leaves the file share option which of course is nothing
else but x-copy with some file type exclusions. And how they decided not to
include FTP as an option is beyond my understanding.
So, Ia??m left with something called Web setup projects. But from what I
understand, they wona??t install under anything else than localhost. In other
words I cannot use it on servers hosting multiple web sites.

plain xcopy is a bit difficult for websites. What we do: first create
(in IIS) the site, then copy "everything" (using "copy project" from
development to test/staging, and then ftp for copying to an external
live server). Watch out for web.config, as that file probably contains
site specific info.
3. Working with multiple web sites
We are a consultant company and we work with multiple web sites for many
different clients. Maybe I havena??t understood how we should set up the
environment but we are leaning towards having one solution for each one of
the web sites we work with.
After a web site is released the majority of our work consists of relatively
small changes and fixes. Having to quickly jump between the different
solutions and waiting seemingly endlessly for the solution to load every time
we need to make small changes feels as a terrible waste of valuable time and
money.
One solution per site (plus maybe more solutions for framework code)
seems to be the way to go.

4. Testing and debugging
Having mentioned that we often make small changes a?? moving to ASP.NET feels
as the time for making and testing these changes will dramatically increase
the time needed. First of all the entire project will have to load into
VS.NET. Then I make some changes to a code behind file which will result in
the entire project will need recompiling. The compilation will need to occur
every time I test a never so small change and I will have to wait at least
15-20 seconds before I will be able to view the changes. When Ia??m satisfied
with the changes (tested on my local development workstation) I will have to
compile it on a testing server using our VSS database as source and if we
consider it to be functional I will somehow try to deploy it to a public web
server.

I seriously wonder if Microsoft really has considered VS.NET to be used for
developing and maintaining many small web projects.

asp.net最适合大型（复杂）网站。那么你*将*具有

编码和可维护性优势。对于很多小的网站，也许你

最好坚持使用asp（你可以用服务器改变服务器上的东西

，并立即查看更改）

-

Hans Kesting

asp.net works best for larger (complicated) sites. Then you *will* have
coding and maintainability benefits. For "many small" sites, maybe you
are better off to stick with asp (you can change things on the server
with Notepad and see the changes immediatly)
--
Hans Kesting

在我看来，你根本没有出售ASP.NET的想法。你的问题看起来似乎是关于.NET的轻微伪装。你可能想用
行使你选择的剩余ASP，否则你可能需要

接受范式转换及其带来的所有好处。


-

问候，

Alvin Bruney


[无耻作者插件]

带有.NET的Microsoft Office Web Components黑皮书

www.lulu.com/owc

------------------------------ ------------------------------


" Linus" <黎*** @ discussions.microsoft.com>在消息中写道

新闻：B2 ********************************** @ microsof t.com ...

It seems to me that you are not sold on the ASP.NET idea at all. Your
questions seem to be thinly disguised rants about .NET. You may want to
exercise your choice of remaining with ASP, otherwise you may need to
embrace the paradigm shift and all the benefits it bring.

--
Regards,
Alvin Bruney

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
available at www.lulu.com/owc
------------------------------------------------------------

"Linus" <Li***@discussions.microsoft.com> wrote in message
news:B2**********************************@microsof t.com...

作为一名顾问公司的ASP开发人员，考虑开始使用ASP.NET进行开发我已经阅读了数百个网页和
帖子开发环境以及技术本身的许多问题仍然没有答案。我会试着在这里总结一些，希望有人能够给我答案，我找不到自己。

1.发展
我当应用程序要部署在带有IIS 6的Win 2003 Server上时，根本无法理解推荐的模型如何在Win XP上使用IIS 5开发应用程序。对我来说这个必然会引起问题。另外 - 安全设置，安装的软件等可能会因不同的开发人员工作站以及不同的服务器而异。

2.部署
微软自豪地促进x-copy部署但他们似乎没有考虑用x-copy部署的新Web应用程序不会运行
而无需手动更改设置在IIS中。
复制项目 - 功能似乎对我来说似乎是一个笑话。阅读了有关FPSE安全问题的内容后，我甚至不会考虑将其安装在公共网页服务器上，这样就可以保留文件共享选项，当然这不是其他选择。带有一些文件类型排除的x-copy。他们如何决定不包括FTP作为一种选择是我无法理解的。
所以，我留下了一些叫做Web安装项目的东西。但是根据我的理解，他们不会安装在除localhost之外的任何东西上。在其他单词中我不能在托管多个网站的服务器上使用它。

3.使用多个网站
我们是一家咨询公司，我们与之合作许多不同客户的多个网站。也许我不明白我们应该如何建立
环境，但我们倾向于为我们合作的每个网站提供一个解决方案。
一个网站之后是发布我们的大部分工作包括相对较小的变化和修复。必须在不同的解决方案之间快速跳转并且无休止地等待解决方案加载每一个时间
我们需要做出微小的改变，感觉是浪费宝贵的时间和/或
金钱。

4.测试和调试
提到我们经常做一些小的改动 - 转向ASP.NET
感觉
为时间制作和测试这些变化将极大地增加所需的时间。首先，整个项目必须加载到VS.NET中。然后我对文件后面的代码进行了一些更改，这将导致
整个项目需要重新编译。每次我测试一个从未如此小的变化时都需要编译
我必须至少等待15-20秒才能查看更改。当我对变更感到满意（在我的本地开发工作站上测试）时，我将使用我们的VSS数据库作为源代码在测试服务器上编译它。如果我们认为它是功能性的，我会以某种方式尝试将其部署到公共服务器上。

我真的很想知道微软是否真的考虑过VS. NET将用于
开发和维护许多小型Web项目。

Being a ASP developer for a consultant company thinking of starting
developing with ASP.NET I have read literally hundreds of web pages and
posts
in discussion forums on the Internet to get an idea of what we will need
to
adapt to. I have read Microsoft''s "Team Development with Visual Studio
.NET
and Visual SourceSafe" and tried to set up a development environment as
recommended using the "Isolated model". However, many questions regarding
the
development environment as well as the technique itself still remain
unanswered. I''ll try to summarize some of them here and hopefully someone
will be able to give me the answers I can''t find myself.

1. Development
I simply cannot understand how the recommended model can be to develop an
application on Win XP with IIS 5 when the application is to be deployed on
a
Win 2003 Server with IIS 6. To me this is bound to cause problems. In
addition - security settings, installed software etc. is likely to vary on
different developer workstations as well as on different servers.

2. Deploying
Microsoft proudly promotes the "x-copy"-deployment but they haven''t seemed
to consider that a new web application deployed with x-copy won''t run
without
manually changing settings in the IIS.
The "Copy project"-functionality seems mostly as a joke to me. Having read
about FPSE security issues I wouldn''t even consider installing it on a
public
web server so that leaves the file share option which of course is nothing
else but x-copy with some file type exclusions. And how they decided not
to
include FTP as an option is beyond my understanding.
So, I''m left with something called Web setup projects. But from what I
understand, they won''t install under anything else than localhost. In
other
words I cannot use it on servers hosting multiple web sites.

3. Working with multiple web sites
We are a consultant company and we work with multiple web sites for many
different clients. Maybe I haven''t understood how we should set up the
environment but we are leaning towards having one solution for each one of
the web sites we work with.
After a web site is released the majority of our work consists of
relatively
small changes and fixes. Having to quickly jump between the different
solutions and waiting seemingly endlessly for the solution to load every
time
we need to make small changes feels as a terrible waste of valuable time
and
money.

4. Testing and debugging
Having mentioned that we often make small changes - moving to ASP.NET
feels
as the time for making and testing these changes will dramatically
increase
the time needed. First of all the entire project will have to load into
VS.NET. Then I make some changes to a code behind file which will result
in
the entire project will need recompiling. The compilation will need to
occur
every time I test a never so small change and I will have to wait at least
15-20 seconds before I will be able to view the changes. When I''m
satisfied
with the changes (tested on my local development workstation) I will have
to
compile it on a testing server using our VSS database as source and if we
consider it to be functional I will somehow try to deploy it to a public
web
server.

I seriously wonder if Microsoft really has considered VS.NET to be used
for
developing and maintaining many small web projects.

这篇关于ASP.NET开发的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！