维护ASP.NET站点 [英] Maintaining ASP.NET Sites
问题描述
他们说它更容易，但有没有人试过
维护一个没有
源代码的ASP.NET网站？这不是问题
使用经典的ASP，所有的代码几乎总是
只是在文本文件中，很容易查看，最重要的是
随手可在网站上获取，任何人都可以访问该网站的文件夹。
但是想象一下，那里有很多公司，管理
非技术人员，他们有一大堆外部开发人员在他们的网站上工作。在当天结束时，他们有几个dll位于bin文件夹中，
并且没有可用的源代码或项目文件。现在你是一个新的
开发人员，他们受雇修复错误并扩展网站。你如何在没有代码隐藏源代码的情况下现在维护这些网站
文件？你怎么理解他们？是的，你可以添加它，是的甚至
扩展类。但是如何在没有
源代码的情况下修复dll中的bug？你怎么理解代码的作用
完全没有源代码???这是一场噩梦！
在这方面，我认为经典ASP优于ASP.NET。
获得雇佣的新开发人员获得由
外包开发人员留下的源代码。那些外包的开发人员将被要求向b
提供DLL的源代码，当旧的开发人员离开时，非技术人员会在这段代码的后面提供
项目。因此，
新开发将收到源代码并从那里开始。
我不明白为什么你没有源代码代码??
顺便说一下，你可以像在ASP中一样在ASP.NET中编码。你
不必使用代码隐藏。您可以在.aspx
文件中拥有100％的代码，而且没有任何DLL。
也许您应该在宣布ASP优先之前进行研究。 ..
雷蒙德 <无***** @ 33.net>在消息新闻中写道：3jSxf.37
MG1.28@trnddc05 ...他们说它更容易，但有人试过
维护没有dll源代码的ASP.NET站点？这不是一个问题
使用经典的ASP，所有的代码几乎总是
只是在文本文件中，易于查看，最重要的是在网站上随时可用，任何人访问
该网站的文件夹。
但是想象一下，那里有很多公司，由非技术人员管理，他们有很多外部的开发人员在做什么在他们的网站上工作。在当天结束时，他们有几个dll坐在bin文件夹中，没有可用的源代码或项目文件。现在，您是一名新的开发人员，负责修复错误并扩展网站。如果没有代码隐藏文件的源代码，您如何现在维护这些网站？你怎么理解他们？是的，您可以添加它，甚至是扩展类。但是如何在没有
源代码的情况下修复dll中的bug？如果没有源代码，你怎么理解代码的确是什么？这是一场噩梦！
在这方面，我认为经典ASP优于ASP.NET。
< blockquote>没有源代码是asp.net的一个选项。关闭你的asp.net服务器上的dll支持，并且需要源代码。
- brcue（sqlwork.com）
雷蒙德 <无***** @ 33.net>在消息新闻中写道：3jSxf.37
They say it''s easier, but has anyone tried
maintaining an ASP.NET site without the
source code of the dlls? This was not a problem
with classic ASP, all the code was almost always
just in text files, easily viewable and most importantly
readily AVAILABLE on the site, to anyone access to
the site''s folder.
But just imagine, bunch of companies out there, managed
by non-technical people, who have had a bunch of outside
developers doing work on their site. At the
end of the day, they have several dlls sitting in the bin folder,
and no source code or project files available. Now you''re a new
developer hired to fix bugs and extend the site. How do you
maintain these sites now without the source code of the codebehind
files? How do you understand them? Yes, you can add to it, yes even
extend the classes. But how do you fix bugs in the dlls without the
source code??? How do you even understand what the code does
exactly without the source code??? It''s a nightmare!
In this respect I think classic ASP is way superior to ASP.NET.
The new developer that gets hired gets the source code that is left by the
outsourced developers. Those outsourced developers would be required to
provide the source code to the DLLs, and the non-technical people would be
in posession of this code when the old developers left the project. Thus,
the new develop would receive the source code and go from there.
I don''t understand why you wouldn''t have the source code??
And by the way, you can code in ASP.NET exactly like you did in ASP. You
don''t have to use codebehind. You can have 100% of the code in the .aspx
files, and no DLLs whatsoever.
Maybe you should do your research before declaring ASP superior...
"Raymond" <no*****@33.net> wrote in message news:3jSxf.37
MG1.28@trnddc05...They say it''s easier, but has anyone tried
maintaining an ASP.NET site without the
source code of the dlls? This was not a problem
with classic ASP, all the code was almost always
just in text files, easily viewable and most importantly
readily AVAILABLE on the site, to anyone access to
the site''s folder.
But just imagine, bunch of companies out there, managed
by non-technical people, who have had a bunch of outside
developers doing work on their site. At the
end of the day, they have several dlls sitting in the bin folder,
and no source code or project files available. Now you''re a new
developer hired to fix bugs and extend the site. How do you
maintain these sites now without the source code of the codebehind
files? How do you understand them? Yes, you can add to it, yes even
extend the classes. But how do you fix bugs in the dlls without the
source code??? How do you even understand what the code does
exactly without the source code??? It''s a nightmare!
In this respect I think classic ASP is way superior to ASP.NET.
not having source code is an option with asp.net. turn off dll support on
your asp.net servers, and the source code will be required.
-- brcue (sqlwork.com)
"Raymond" <no*****@33.net> wrote in message news:3jSxf.37
这篇关于维护ASP.NET站点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
