可维护性准则 [英] Maintainability Guidelines

问题描述

我想得到一些非常好的要点，在维护asp.net应用程序时需要考虑这些要点.

在维护应用程序方面，任何人都可以在一些好的职位上为我提供帮助，这些职位具有与应用程序应注意的事项有关的一些优点.


谢谢，
Vijay

Hi,

I would like to get some really good points which are need to take into account for maintaining an asp.net application.

Can anybody help me in some good posts which has some good points relating to things to be taken care for an application in terms of maintaining the application.


Thanks,
Vijay

推荐答案

应该在一个论坛中发布，而不是在此处提问/回答.它需要一个可行的线程式讨论模型，而问题/答案没有提供该模型.

除此之外，几年前，我在这里发表了一篇文章，讨论了如何成为一名程序员.当涉及到本主题时，您可能会发现它很有用.这是链接:

成为程序员 [

This should be posted in one of the forums instead of here in questions/answers. It needs a viable threaded discussion model, and questions/answers does not provide that.

Beyond that, I posted an article here a few years ago that discusses being a programmer. You may find it somewhat useful as this topic is touched on. Here''s a link:

Being a Programmer[^]

您正在询问有关维护asp.net应用程序的好处.应用程序的实际可维护性取决于其设计和构建方式.如果失败了，您只能尽力而为.

尝试找出冗余代码并为此创建方法或类.这将缩短必须维护的实际代码，并使更改特定功能变得更加容易，因为只需更改一次即可完成.

但是在进行任何编码之前，请先熟悉应用程序并尝试完全了解其用途.即使它们像地狱一样丑陋，这也使理解代码和理解黑客变得更加容易.此时，您只需要超越自己的知识范围，并尝试了解一个人在您之前使用的编码方法即可.有时，它将提供有关新编码方法和方式的见解.在大多数情况下，它只是在抱怨毛孔质量，但偶尔会笑到一些荒谬的实现. (我可能会在网站上制造一些编码恐怖的东西，这超出了您和我的想象力.)

祝你好运！

You are asking about good points about maintaining an asp.net application. The actual maintainability of an application is dependent on how it is designed and built. If that has failed, you can only salvage as good as you can.

Try to spot redundant code and make methods or classes for that. This will shorten the actual code that must be maintained and makes changes to specific functionality easier because it can be done by changing it only once.

But before you do any coding, familiarize yourself with the application and try to fully understand what it is meant to do. This makes it more easy to understand the code and understand hacks even though they are as ugly as hell. At this point, you just need to look beyond your own knowledge and try to understand the coding methods someone used by the one before you. Sometimes it will give insight about new methods and ways of coding. Most of the time it''s just crying about the pore quality but with an occasional laugh about some ridiculous implementation. (I could make a site with some coding horror that goes beyond your, and also my, imagination.)

Good luck!

您主要是在考虑技术债务.您可以在此处 [ ^ ].

You are primarily going to be thinking about technical debt. You can find a good article with some decent links here[^].

这篇关于可维护性准则的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！