blocks|key|2662386|text|以下是一些类似的问题，可能会对你有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2662387|.NET最佳实践？|offset|length|2662388|学习.NET/OOP最佳实践的最佳方法？|2662389|这可能也应该是社区wiki。|2662390|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/528500/net-best-practices|1|https://stackoverflow.com/questions/293152/best-way-to-learn-net-oop-best-practices^0|0|0|9|0|0|0|K|1|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

Here are some similar questions that may help you.

<a href="https://stackoverflow.com/questions/528500/net-best-practices">.NET best practices?</a>

<a href="https://stackoverflow.com/questions/293152/best-way-to-learn-net-oop-best-practices">Best way to learn .NET/OOP best practices?</a>

This should probably be community wiki as well.

blocks|key|1099741|text|我不认为尝试/捕捉块总是适合于低级别的方法。您希望捕获(并记录/警告，甚至更好！)当然，在到达用户之前，任何错误都会发生。但是，对于一个低层次的方法来说，让它的错误被提升到一个更高的水平通常更好。我在低级别错误捕获中看到的问题是，它通常会让更大的操作继续进行，但是，如果结果不太正确，就会显示给用户或保存到数据库中，而且从长远来看，修复起来要困难得多。如果您不打算对错误“做任何事情”，直到将错误提升到更高的级别，那么在您的代码中也会有很多杂乱无章的地方来尝试/捕捉错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1099742|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I don't think try/catch blocks are always appropriate for low-level methods. You want to catch (and log/alert, even better!) any errors before they get to the user, of course. But it is often better for a low-level method to just lets its errors get raised up to a higher level. The problem I have seen with low-level error trapping is that it often lets a larger operation continue, but then a result that is not quite correct gets presented to the user or saved to the database, and in the long run it's much more difficult to fix. It's also just a lot of extra clutter in your code to put a try/catch at every level if you're not going to "do anything" with the error until it's raised up to a higher level.

blocks|key|1099778|text|为所有asp.net页面创建一个基页。此页面将从System.Web.UI.Page派生，您可以将其放在YourApp.Web.UI中。让您的所有asp.net页面从YourApp.Web.UI.Page类中删除。这可以减轻很多痛苦。|type|ordered-list-item|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1099779|使用Application_OnError处理程序来优雅地处理任何错误或异常。您应该记录关键异常，并将异常的详细信息以及客户端的日期、时间和IP发送到管理电子邮件id。是的，ELMAH是很好的选择。|1099780|使用ASP.NET主题。许多开发人员不使用它。一定要使用它们--它们是一笔很大的交易。|1099781|使用MembershipProvider和RoleProvider。从不使用内置的ProfileProvider+--它们将所有东西都存储在普通字符串中。在执行R/W时，它将大大减慢表演速度。|1099782|使用火虫进行客户端调试.尝试遵循YSlow的web应用标准。对YSlow使用FireBug扩展。|1099783|使用jQuery进行客户端脚本编写。|1099784|从不在会话中存储用户身份验证信息，也不使用会话判断用户是否登录。只在会话中存储最低限度的必要信息。|1099785|看看PostSharp。可以提高代码的可维护性，并使您更有效率。|1099786|从未在产品上在调试配置下部署asp.net应用程序。找出这里，斯科特古对此有什么看法。|1099787|用户Web部署项目。它可以转换web.config部分并替换为生产服务器集。它将把所有编译后的代码隐藏类合并成一个程序集，这是一个很大的问题。|1099788|使用Cookie无域来提供静态资源，如图像、脚本、样式等。每个客户端请求都与大量Cookie一起发送，您在提供图片或脚本时不需要Cookie。所以把这些资源存放在没有cookie的域上。|1099789|缩小了来自服务器的脚本、样式表和HTML+。消除不必要的换行和空白可以改善加载时间和带宽优化.|1099790|unstyled|entityMap|0|LINK|mutability|MUTABLE|url|http://www.raboof.com/projects/Elmah/|1|http://getfirebug.com/|2|http://developer.yahoo.com/yslow/|3|http://jquery.com/|4|http://www.postsharp.net/|5|http://weblogs.asp.net/scottgu/archive/2006/04/11/Don_1920_t-run-production-ASP.NET-Applications-with-debug_3D001D20_true_1D20_-enabled.aspx|6|http://weblogs.asp.net/scottgu|7|http://www.asp.net/downloads/^0|0|I|0|0|L|2F|5|0|0|0|B|0|0|X|Y|M|0|2|2|1|V|5|2|0|2|6|3|0|0|5|W|4|0|2|9|4|0|0|B|S|2|5|V|4|6|0|2|7|7|0|0|A|0|0|L|0^^$0|@$1|2|3|4|5|6|7|1O|8|@$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1R|8|@$9|1S|A|1T|B|C]]|D|@$9|1U|A|1V|1|1W]]|E|$]]|$1|H|3|I|5|6|7|1X|8|@$9|1Y|A|1Z|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|20|8|@$9|21|A|22|B|C]|$9|23|A|24|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|25|8|@]|D|@$9|26|A|27|1|28]|$9|29|A|2A|1|2B]]|E|$]]|$1|N|3|O|5|6|7|2C|8|@]|D|@$9|2D|A|2E|1|2F]]|E|$]]|$1|P|3|Q|5|6|7|2G|8|@$9|2H|A|2I|B|C]|$9|2J|A|2K|B|C]]|D|@]|E|$]]|$1|R|3|S|5|6|7|2L|8|@]|D|@$9|2M|A|2N|1|2O]]|E|$]]|$1|T|3|U|5|6|7|2P|8|@$9|2Q|A|2R|B|C]]|D|@$9|2S|A|2T|1|2U]|$9|2V|A|2W|1|2X]]|E|$]]|$1|V|3|W|5|6|7|2Y|8|@]|D|@$9|2Z|A|30|1|31]]|E|$]]|$1|X|3|Y|5|6|7|32|8|@$9|33|A|34|B|C]]|D|@]|E|$]]|$1|Z|3|10|5|6|7|35|8|@$9|36|A|37|B|C]]|D|@]|E|$]]|$1|11|3|-4|5|12|7|38|8|@]|D|@]|E|$]]]|13|$14|$5|15|16|17|E|$18|19]]|1A|$5|15|16|17|E|$18|1B]]|1C|$5|15|16|17|E|$18|1D]]|1E|$5|15|16|17|E|$18|1F]]|1G|$5|15|16|17|E|$18|1H]]|1I|$5|15|16|17|E|$18|1J]]|1K|$5|15|16|17|E|$18|1L]]|1M|$5|15|16|17|E|$18|1N]]]]

<ol>
<li>Create a base page for all your asp.net pages. This page will derive from System.Web.UI.Page and you may put this in YourApp.Web.UI. Let all your asp.net pages dervice from YourApp.Web.UI.Page class. This can reduce lot of pain.</li>
<li>Use Application_OnError handler to gracefully handle any error or exception. You should log the critical exception and send the details of the exception along with date-time and IP of client to the admin email id. Yes <a href="http://www.raboof.com/projects/Elmah/" rel="nofollow noreferrer">ELMAH</a> is sure way to go.</li>
<li>Use ASP.NET Themes. Many developers don't use it. Do use them - they are a great deal.</li>
<li>Use MembershipProvider and RoleProvider. And Never use inbuilt ProfileProvider - They store everything in plain strings. It will drastically slow-down the performance while performing R/W</li>
<li>Use <a href="http://getfirebug.com/" rel="nofollow noreferrer">Firebug</a> for client-side debugging. Try to follow YSlow standards for web-applications. Use <a href="http://developer.yahoo.com/yslow/" rel="nofollow noreferrer">YSlow</a> extension for FireBug.</li>
<li>Use <a href="http://jquery.com/" rel="nofollow noreferrer">jQuery</a> for client-scripting.</li>
<li>Never store User Authentication information in session or don't use sessions to judge if user is logged on. Store only minimum necessary information in sessions.</li>
<li>Have a look at <a href="http://www.postsharp.net/" rel="nofollow noreferrer">PostSharp</a>. Can improve maintainability of your code and make you more productive.</li>
<li>Never ever Deploy asp.net application under debug configuration on production. Find out <a href="http://weblogs.asp.net/scottgu/archive/2006/04/11/Don_1920_t-run-production-ASP.NET-Applications-with-debug_3D001D20_true_1D20_-enabled.aspx" rel="nofollow noreferrer">here</a> what <a href="http://weblogs.asp.net/scottgu" rel="nofollow noreferrer">scottgu</a> has to say about this.</li>
<li>User <a href="http://www.asp.net/downloads/" rel="nofollow noreferrer">Web Deployment projects</a>. It can transform web.config sections and replace with production server setings. It will merge all compiled code-behind classes into one single assembly which is a great deal.</li>
<li>Use Cookie-less domains to serve static resources like images, scripts, styles etc. Each client request is sent along with whole bunch of cookies, you don't need cookies while serving pictures or scripts. So host those resources on a cookie-less domain.</li>
<li>Minify scripts, stylesheets and HTML response from the server. Removing unnecessary line-breaks and white-spaces can improve the time-to-load and bandwidth optimization.</li>
</ol>

blocks|key|1138179|text|随着时间的推移，我学到并编写在我的company...many中使用的一些最佳实践主要适用于WebForms而不是MVC。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1138180|不要在您的ASPX标记中直接编写.NET代码(除非是用于数据绑定，即Evals)。如果后面有代码，这会将页面的代码放置在多个地方，从而降低代码的可管理性。将所有.NET代码放入代码隐藏中。|unordered-list-item|1138181|SessionPageStatePersister可以与ViewState一起使用，使ViewState在不增加页面大小的情况下很有用。用新的PageStatePersister重写页面的SessionPageStatePersister将在内存中存储所有ViewState数据，并且只在客户端存储加密密钥。|1138182|创建一个页面可以继承的BasePage，以便重用页面之间的通用代码。为您的页面创建一个用于视觉继承的MasterPage。视觉样式迥异的页面应该使用不同的MasterPage。|1138183|在通过URL传入的每个WebForm上创建页面参数键名的枚举，以设置强类型的页面参数。这防止了硬编码页面参数键字符串及其可能的错误类型的需要，以及允许其他页面进行强类型参数访问的需要。|1138184|利用ASP.NET缓存来缓存数据库中经常使用的信息。构建(或从另一个项目中重用)一个将包装ASP.NET缓存的通用缓存层。|1138185|在页面上使用属性包装ViewState对象，以避免在引用来自ViewState集合的项时出现拼写等方面的开发错误。|1138186|避免在ViewState中放置大型对象和对象图，主要用于存储ID或非常简单的DTO对象。|1138187|将ASP.NET会话包装为SessionManager，以避免在引用会话中的项时出现拼写等方面的开发错误。|1138188|广泛使用web.config中的web.config键/值配置值--用一个类包装Configuration.ApplicationSettings，该类可以方便地检索配置设置，而不必记住来自web.config的键。|1138189|避免在UI控件上设置显示属性的简单性，而使用CSS样式和类-这将使您的样式更易于管理。|1138190|在应用程序中创建UserControls，以便在整个页面中重用通用UI功能。例如，如果包含类别集合的下拉列表将在站点的许多地方使用--创建一个CategoryPicker控件，该控件将在加载页面时绑定自己。|1138191|使用UserControls上的属性设置默认值、页面间的不同显示等。值类型属性可以在UserControls上定义，然后通过在UserControls上使用类级属性在ASP.NET标记中设置。|1138192|使用ASP.NET验证控件执行简单验证，或使用CustomValidator执行复杂验证。|1138193|创建一个可重定向到网站内发生未处理异常时的错误处理页面。重定向可以通过页面中的Page_Error事件、Global.asax中的Application_Error事件或web.config中的部分进行。|1138194|当使用使用高度动态数据驱动显示的页面时，使用第三方(免费)+DynamicControlsPlaceholder控件来简化保存回发之间动态添加控件的状态所需的代码。|1138195|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|19|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|1A|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|1B|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1C|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|1D|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1E|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1G|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1H|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|1I|8|@]|9|@]|A|$]]|$1|W|3|X|5|D|7|1J|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|D|7|1K|8|@]|9|@]|A|$]]|$1|10|3|11|5|D|7|1L|8|@]|9|@]|A|$]]|$1|12|3|13|5|D|7|1M|8|@]|9|@]|A|$]]|$1|14|3|15|5|D|7|1N|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|17|$]]

Some of the best practices that I've learned over time and written up for use at my company...many are mainly applicable to WebForms and not MVC.

<ul>
<li>Don't write .NET code directly in
your ASPX markup (unless it is for
databinding, i.e. Evals). If you
have a code behind, this puts code
for a page in more than one place and
makes the code less manageable. Put
all .NET code in your code-behind.</li>
<li>SessionPageStatePersister can be used in conjunction with ViewState
to make ViewState useful without
increasing page sizes. Overriding
the Page's PageStatePersister with a
new SessionPageStatePersister will
store all ViewState data in memory,
and will only store an encrypted key
on the client side.</li>
<li>Create a BasePage that your pages can inherit from in order to
reuse common code between pages. 
Create a MasterPage for your pages
for visual inheritance. Pages with
vastly different visual styles should
use a different MasterPage.</li>
<li>Create an enum of page parameter key names on each WebForm
that are passed in via the URL, to
setup strongly-typed page parameters.
This prevents the need for hard-coded
page parameter key strings and their
probable mis-typing, as well as
allowing strongly-typed parameter
access from other pages.</li>
<li>Make use of the ASP.NET Cache in order to cache frequently used
information from your database. 
Build (or reuse from another project)
a generic caching layer that will
wrap the ASP.NET Cache.</li>
<li>Wrap ViewState objects with Properties on your Pages to avoid
development mistakes in spelling,
etc. when referencing items from the
ViewState collection.</li>
<li>Avoid putting large objects and object graphs in ViewState, use it mainly for storing IDs or very simple DTO objects.</li>
<li>Wrap the ASP.NET Session with a SessionManager to avoid development
mistakes in spelling, etc. when
referencing items from Session.</li>
<li>Make extensive use of the applicationSettings key/value
configuration values in the
web.config - wrap the
Configuration.ApplicationSettings
with a class that can be used to
easily retrieve configuration
settings without having to remember
the keys from the web.config.</li>
<li>Avoid the easiness of setting display properties on your UI
controls, instead use CSS styles and
classes - this will make your styles
more manageable.</li>
<li>Create UserControls in your application in order to reuse common
UI functionality throughout your
pages. For example, if a drop down
list containing a collection of
categories will be used in many
places in the site - create a
CategoryPicker control that will data
bind itself when the page is loaded.</li>
<li>Use Properties on your UserControls to setup things like
default values, different displays
between pages, etc. Value type
properties can be defined on your
UserControls and then be set in your
ASP.NET markup by using class level
properties on UserControls.</li>
<li>Make use of the ASP.NET validation controls to perform simple
validations, or use the
CustomValidator to perform complex
validations.</li>
<li>Create an Error handling page that can be redirected to when an
unhandled exception occurs within
your website. The redirection can
occur via the Page_Error event in
your Page, the Application_Error
event in your Global.asax, or within
the section within the
web.config.</li>
<li>When working with pages that use a highly dynamic data driven
display, use the 3rd party (free)
DynamicControlsPlaceholder control to
simplify the code needed to save the
state of dynamically added controls
between postbacks.</li>
</ul>

blocks|key|1099850|text|如果您有兴趣追求成为一个更好、更高效的开发人员的旅程，我会推荐几本书。这些书是语言不可知论，你可以从用户的评论中看到，非常有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1099851|代码完成2|offset|length|1099852|实用程序员|1099853|如果您正在寻找一本特定于.NET的书，您可能会欣赏以下书：|1099854|Microsoft应用程序架构指南可在打印格式之外免费在线使用|1099855|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0735619670|1|https://rads.stackoverflow.com/amzn/click/com/020161622X|2|https://rads.stackoverflow.com/amzn/click/com/073562710X^0|0|0|5|0|0|0|5|1|0|0|0|H|2|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|L|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]|V|$5|O|P|Q|A|$R|W]]]]

I would recommend a couple of books if you are interested in pursuing a journey to become a better, more productive developer. These books are language agnostic and as you can see by the user reviews, very very helpful.

<a href="https://rads.stackoverflow.com/amzn/click/com/0735619670" rel="nofollow noreferrer" rel="nofollow noreferrer">Code Complete 2</a>

<a href="https://rads.stackoverflow.com/amzn/click/com/020161622X" rel="nofollow noreferrer" rel="nofollow noreferrer">Pragmatic Programmer</a>

If you are looking for a .NET specific book, you may appreciate the following book:

<a href="https://rads.stackoverflow.com/amzn/click/com/073562710X" rel="nofollow noreferrer" rel="nofollow noreferrer">Microsoft Application Architecture Guide</a> [available online for free outside of print format]

blocks|key|1099527|text|表单：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1099528|设置Page.Form.DefaultFocus和Page.Form.DefaultButton以改善用户体验|ordered-list-item|CODE|1099529|在继续之前，请检查保存按钮处理程序中的Page.IsValid。|1099530|General:|1099531|理解并实现"真正理解ViewState“一文中的技术|1099532|在页面事件中使用Page.IsPostBack来阻止代码不必要地运行。|1099533|尽可能使用超链接而不是张贴和使用Response.Redirect。
理解并使用Response.Redirect的第二个参数(它“指示当前页面的执行是否应该终止”)|1099534|正确使用页面生命周期。|1099535|在有意义的地方使用每个请求缓存+(HttpContext.Items)而不是缓存。|1099536|Web.Config:|1099537|使用<compilation+debug="false">部署|1099538|在web.config水平而不是页级+(即@页级)注册您的控件。|1099539|主题：|1099540|在使用主题时，也要将静态图像放在主题中。
不要直接从标记链接到图像，而是从主题中的皮肤文件或css文件链接到它们。
例：<asp:Image+SkinID="MyImage"+runat="server"+ImageUrl="Images/myImage.gif"+/>|1099541|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/infinitiesloop/archive/2006/08/03/truly-understanding-viewstate.aspx|1|http://msdn.microsoft.com/en-us/library/a8wa7sdt%2528VS.80%2529.aspx|2|http://msdn.microsoft.com/en-us/library/ms178472.aspx|3|https://web.archive.org/web/20210608183011/http://aspnet.4guysfromrolla.com/articles/060904-1.aspx|4|http://msdn.microsoft.com/en-us/library/tbazwch5.aspx|5|http://msdn.microsoft.com/en-us/library/c76dd5k1.aspx|6^0|0|3|0|2|M|P|N|0|J|C|0|0|8|0|6|D|0|0|0|14|H|1|0|4|6|2|0|9|6|3|0|0|B|0|2|R|0|1|C|4|G|2|5|M|2|6|0|0|3|0|1O|23|0^^$0|@$1|2|3|4|5|6|7|1Q|8|@$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1T|8|@$9|1U|A|1V|B|I]|$9|1W|A|1X|B|I]]|D|@]|E|$]]|$1|J|3|K|5|H|7|1Y|8|@$9|1Z|A|20|B|I]]|D|@]|E|$]]|$1|L|3|M|5|6|7|21|8|@$9|22|A|23|B|C]]|D|@]|E|$]]|$1|N|3|O|5|H|7|24|8|@]|D|@$9|25|A|26|1|27]]|E|$]]|$1|P|3|Q|5|H|7|28|8|@]|D|@]|E|$]]|$1|R|3|S|5|H|7|29|8|@]|D|@$9|2A|A|2B|1|2C]]|E|$]]|$1|T|3|U|5|H|7|2D|8|@]|D|@$9|2E|A|2F|1|2G]]|E|$]]|$1|V|3|W|5|H|7|2H|8|@]|D|@$9|2I|A|2J|1|2K]]|E|$]]|$1|X|3|Y|5|6|7|2L|8|@$9|2M|A|2N|B|C]]|D|@]|E|$]]|$1|Z|3|10|5|H|7|2O|8|@$9|2P|A|2Q|B|I]]|D|@]|E|$]]|$1|11|3|12|5|H|7|2R|8|@]|D|@$9|2S|A|2T|1|2U]|$9|2V|A|2W|1|2X]|$9|2Y|A|2Z|1|30]]|E|$]]|$1|13|3|14|5|6|7|31|8|@$9|32|A|33|B|C]]|D|@]|E|$]]|$1|15|3|16|5|H|7|34|8|@$9|35|A|36|B|I]]|D|@]|E|$]]|$1|17|3|-4|5|6|7|37|8|@]|D|@]|E|$]]]|18|$19|$5|1A|1B|1C|E|$1D|1E]]|1F|$5|1A|1B|1C|E|$1D|1G]]|1H|$5|1A|1B|1C|E|$1D|1I]]|1J|$5|1A|1B|1C|E|$1D|1K]]|1L|$5|1A|1B|1C|E|$1D|1M]]|1N|$5|1A|1B|1C|E|$1D|1O]]|1P|$5|1A|1B|1C|E|$1D|1O]]]]

Forms:

<ol>
<li>Set <code>Page.Form.DefaultFocus</code> and <code>Page.Form.DefaultButton</code> to improve user experience</li>
<li>Check <code>Page.IsValid</code> in your Save button handler before proceeding.</li>
</ol>

General:

<ol>
<li>Understand and implement the techniques found in the article "<a href="http://weblogs.asp.net/infinitiesloop/archive/2006/08/03/truly-understanding-viewstate.aspx" rel="noreferrer">TRULY Understanding ViewState</a>" </li>
<li>Use Page.IsPostBack in your page events to stop code from running unnecessarily.</li>
<li>Use hyperlinks instead of posting and using Response.Redirect whenever possible.

a. Understand and use the second parameter of <a href="http://msdn.microsoft.com/en-us/library/a8wa7sdt%28VS.80%29.aspx" rel="noreferrer">Response.Redirect</a> (it "Indicates whether execution of the current page should terminate")</li>
<li>Use the <a href="http://msdn.microsoft.com/en-us/library/ms178472.aspx" rel="noreferrer">Page Lifecycle</a> properly.</li>
<li>Use the <a href="https://web.archive.org/web/20210608183011/http://aspnet.4guysfromrolla.com/articles/060904-1.aspx" rel="noreferrer">Per-Request cache</a> (HttpContext.Items) instead of Cache where it makes sense.</li>
</ol>

Web.Config:

<ol>
<li>Deploy with <code>&lt;compilation debug="false"&gt;</code></li>
<li>Register your controls at the <a href="http://msdn.microsoft.com/en-us/library/tbazwch5.aspx" rel="noreferrer">web.config level</a> instead of the <a href="http://msdn.microsoft.com/en-us/library/c76dd5k1.aspx" rel="noreferrer">page level</a> (i.e. @Register).</li>
</ol>

Themes:

<ol>
<li>When using Themes, put your static images in the Theme as well. 

a. Don't link to the images directly from your markup, link to them from a skin file or css file in your Theme instead.

ex: <code>&lt;asp:Image SkinID="MyImage" runat="server" ImageUrl="Images/myImage.gif" /&gt;</code></li>
</ol>

blocks|key|2662803|text|ASP.NET|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2662804|如果不使用会话状态，请不要忘记关闭它。|unordered-list-item|2662805|如果可能的话，使用Server.Transfer而不是Response.Redirect。|CODE|2662806|在IIS中设置过期参数。|2662807|使用GZip压缩文本文件。|2662808|同时使用服务器端和客户端验证。|2662809|使用Url重写或路由为SEO制作友好的url。|2662810|设计|2662811|将CSS文件的每个类及其属性写在同一行中。(以减小文件大小)|2662812|使用CSS雪碧。(减少请求)|2662813|entityMap^0|0|7|0|0|9|F|R|H|0|0|0|0|0|0|2|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|14|8|@]|D|@]|E|$]]|$1|I|3|J|5|H|7|15|8|@$9|16|A|17|B|K]|$9|18|A|19|B|K]]|D|@]|E|$]]|$1|L|3|M|5|H|7|1A|8|@]|D|@]|E|$]]|$1|N|3|O|5|H|7|1B|8|@]|D|@]|E|$]]|$1|P|3|Q|5|H|7|1C|8|@]|D|@]|E|$]]|$1|R|3|S|5|H|7|1D|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|V|3|W|5|H|7|1H|8|@]|D|@]|E|$]]|$1|X|3|Y|5|H|7|1I|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|10|$]]

ASP.NET

<ul>
<li>If you don't use Session state, don't
forget to turn off it.</li>
<li>Use <code>Server.Transfer</code> instead of <code>Response.Redirect</code> if possible.</li>
<li>Set expiration parameter in IIS.</li>
<li>Use GZip to compress the text files.</li>
<li>Use Server-Side and Client-Side validation together.</li>
<li>Use Url Rewriter or Routing to make friendly url for SEO.</li>
</ul>

<hr>

Design

<ul>
<li>Write each class and its properties
of your CSS file in the same line. (To decrease the file size)</li>
<li>Use CSS Sprites. (To decrease request)</li>
</ul>

We are building an ASP.NET application and would like to follow the best practices. Some of the best practices are:

<hr>

Server side Code:

<ul>
<li>Use catch blocks to trap &amp; log low level errors too.</li>
<li>Use Cache objects to populate dropdowns etc. where we won’t expect the changes in the underlying data/database.</li>
<li>In case of error logging framework, provide emailing alerts along with logging the errors.</li>
</ul>

<hr>

HTML code:
- Don’t write inline CSS.
- Place the JavaScript code (If needed by the page) at the end of the page unless the page needs it for load time actions.

<hr>

Now coming to the point, Would you please share these best practice points if you have a comprehensive list of them already?

Building ASP.NET application - Best Practices

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们正在构建一个ASP.NET应用程序，并希望遵循最佳实践。一些最佳做法是：服务器端代码：使用catch块也可以捕获和记录低级别错误。使用Cache对象填充下拉列表等，这样我们就不会期望底层数据/数据库中的更改。如果出现错误日志记录框架，请在记录错误的同时提供电子邮件通知。HTML代码：-不要写内联CSS。-将Java...

问构建ASP.NET应用程序-最佳实践
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问构建ASP.NET应用程序-最佳实践EN