问题描述： 使用swfupload.js上传文件,在IE8、火狐、谷歌浏览器中显示正常，但是在IE9下不能显示上传按钮。 解决方法： 打开swfupload.js文件找到307行开始的如下代码： // Private: getFlashHTML generates the object tag needed to embed the flash in to the document SWFUpload.prototype.getFlashHTML = function (flashVersion) { // Flash Satay object syntax: http://www.alistapart.com/articles/flashsatay return ['<object id="',this.movieName, '" type="application/x-shockwave-flash" data="', (this.support.imageResize ?this.settings.flash_url : this.settings.flash9_url), '" width="', this.settings.button_width, '" height="',this.settings.button_height, '" class="swfupload">', '<param name="wmode" value="',this.settings.button_window_mode, '" />', '<param name="movie" value="', (this.support.imageResize ?this.settings.flash_url : this.settings.flash9_url), '" />', '<param name="quality" value="high" />', '<param name="allowScriptAccess" value="always" />', '<param name="flashvars" value="' +this.getFlashVars() + '" />', '</object>'].join(""); }; 将其替换为： // Private: getFlashHTML generates the object tag […]
View DetailsAsp.net的NamePipe机制给我们提供了很多扩展性. 使用HttpModule我们可能实现的有: 强制站点范围的Cookie策略 集中化监控与日志 编写设置与删除HTTP头 控制response输出,如删除多余空白字符 Session管理 认证与受权 下面我们来看如何实现自定义异常处理:
|
1 |
<span class="lnum"> 1: </span> <span class="kwrd">public</span> <span class="kwrd">class</span> ErrorModule:IHttpModule |
|
1 |
<span class="lnum"> 2: </span> { |
|
1 |
<span class="lnum"> 3: </span> <span class="preproc">#region</span> IHttpModule Members |
|
1 |
<span class="lnum"> 4: </span> |
|
1 |
<span class="lnum"> 5: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 6: </span> <span class="rem">/// Disposes of the resources (other than memory) used by the module that implements <see cref="T:System.Web.IHttpModule"/>.</span> |
|
1 |
<span class="lnum"> 7: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 8: </span> <span class="kwrd">public</span> <span class="kwrd">void</span> Dispose() |
|
1 |
<span class="lnum"> 9: </span> { |
|
1 |
<span class="lnum"> 10: </span> <span class="rem">//do nothing </span> |
|
1 |
<span class="lnum"> 11: </span> } |
|
1 |
<span class="lnum"> 12: </span> |
|
1 |
<span class="lnum"> 13: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 14: </span> <span class="rem">/// Initializes a module and prepares it to handle requests.</span> |
|
1 |
<span class="lnum"> 15: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 16: </span> <span class="rem">/// <param name="context">An <see cref="T:System.Web.HttpApplication"/> that provides access to the methods, properties, and events common to all application objects within an ASP.NET application</param></span> |
|
1 |
<span class="lnum"> 17: </span> <span class="kwrd">public</span> <span class="kwrd">void</span> Init(HttpApplication context) |
|
1 |
<span class="lnum"> 18: </span> { |
|
1 |
<span class="lnum"> 19: </span> context.Error += <span class="kwrd">new</span> EventHandler(customcontext_Error); |
|
1 |
<span class="lnum"> 20: </span> } |
|
1 |
<span class="lnum"> 21: </span> |
|
1 |
<span class="lnum"> 22: </span> <span class="kwrd">private</span> <span class="kwrd">void</span> customcontext_Error(<span class="kwrd">object</span> sender, EventArgs e) |
|
1 |
<span class="lnum"> 23: </span> { |
|
1 |
<span class="lnum"> 24: </span> HttpContext ctx = HttpContext.Current; |
|
1 |
<span class="lnum"> 25: </span> HttpResponse response = ctx.Response; |
|
1 |
<span class="lnum"> 26: </span> HttpRequest request = ctx.Request; |
|
1 |
<span class="lnum"> 27: </span> |
|
1 |
<span class="lnum"> 28: </span> Exception exception = ctx.Server.GetLastError(); |
|
1 |
<span class="lnum"> 29: </span> |
|
1 |
<span class="lnum"> 30: </span> var sboutput = <span class="kwrd">new</span> StringBuilder(); |
|
1 |
<span class="lnum"> 31: </span> sboutput.Append(<span class="str">"Querystring:<p/>"</span>); |
|
1 |
<span class="lnum"> 32: </span> <span class="rem">//Get out the query string </span> |
|
1 |
<span class="lnum"> 33: </span> <span class="kwrd">int</span> count = request.QueryString.Count; |
|
1 |
<span class="lnum"> 34: </span> <span class="kwrd">for</span> (<span class="kwrd">int</span> i = 0; i < count; i++) |
|
1 |
<span class="lnum"> 35: </span> { |
|
1 |
<span class="lnum"> 36: </span> sboutput.AppendFormat(<span class="str">"<br/> {0}:-- {1} "</span>, request.QueryString.Keys[i], request.QueryString[i]); |
|
1 |
<span class="lnum"> 37: </span> } |
|
1 |
<span class="lnum"> 38: </span> <span class="rem">//Get out the form collection info</span> |
|
1 |
<span class="lnum"> 39: </span> sboutput.Append(<span class="str">"<p>-------------------------<p/>Form:<p/>"</span>); |
|
1 |
<span class="lnum"> 40: </span> count = request.Form.Count; |
|
1 |
<span class="lnum"> 41: </span> <span class="kwrd">for</span> (<span class="kwrd">int</span> i = 0; i < count; i++) |
|
1 |
<span class="lnum"> 42: </span> { |
|
1 |
<span class="lnum"> 43: </span> sboutput.AppendFormat(<span class="str">"<br/> {0}:-- {1} -- <br/>"</span>, request.Form.Keys[i], request.Form[i]); |
|
1 |
<span class="lnum"> 44: </span> } |
|
1 |
<span class="lnum"> 45: </span> sboutput.Append(<span class="str">"<p>-------------------------<p/>ErrorInfo:<p/>"</span>); |
|
1 |
<span class="lnum"> 46: </span> sboutput.AppendFormat(<span class="str">@"Your request could not processed. Please press the back button on your browser and try again.<br/></span> |
|
1 |
<span class="lnum"> 47: </span> If the problem persists, please contact technical support<p/> |
|
1 |
<span class="lnum"> 48: </span> Information below is for technical support:<p/> |
|
1 |
<span class="lnum"> 49: </span> <p/>URL:{0}<p/>Stacktrace:---<br/>{1}<p/>InnerException:<br/>{2}" |
|
1 |
<span class="lnum"> 50: </span> , ctx.Request.Url, exception.InnerException.StackTrace, exception.InnerException); |
|
1 |
<span class="lnum"> 51: </span> |
|
1 |
<span class="lnum"> 52: </span> response.Write(sboutput.ToString()); |
|
1 |
<span class="lnum"> 53: </span> |
|
1 |
<span class="lnum"> 54: </span> <span class="rem">// To let the page finish running we clear the error</span> |
|
1 |
<span class="lnum"> 55: </span> ctx.Server.ClearError(); |
|
1 |
<span class="lnum"> 56: </span> } |
|
1 |
<span class="lnum"> 57: </span> |
|
1 |
<span class="lnum"> 58: </span> <span class="preproc">#endregion</span> |
|
1 |
<span class="lnum"> 59: </span> |
|
1 |
<span class="lnum"> 60: </span> } |
上面的代码实现了IHttpModule接口, 实现基于HttpApplication.Error事件, 接着我们自定义输出了一些信息,包括Form,QueryString. 最后把原来的Error信息清除了,这样你看到以前那个黄页了. 这个自定义的Module可以用于调试Web应用程序使用. Web.config中配置:
|
1 |
<span class="kwrd"><</span><span class="html">httpModules</span><span class="kwrd">></span> |
|
1 |
<span class="kwrd"><</span><span class="html">add</span> <span class="attr">name</span><span class="kwrd">="ErrorLoggingModule"</span> <span class="attr">type</span><span class="kwrd">="MyWeb.ErrorModule"</span><span class="kwrd">/></span> |
|
1 |
<span class="kwrd"></</span><span class="html">httpModules</span><span class="kwrd">></span> |
实际开发中,我们可以做的事儿很多,对这些信息记日志,发邮件. 如下, 我们演示使用Enterprise Library 做异常处理并日志记录,部分代码如下:
|
1 |
<span class="lnum"> 1: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 2: </span> <span class="rem">/// Handles the Error event of the EntLibLogging control.</span> |
|
1 |
<span class="lnum"> 3: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 4: </span> <span class="rem">/// <param name="sender">The source of the event.</param></span> |
|
1 |
<span class="lnum"> 5: </span> <span class="rem">/// <param name="e">The <see cref="System.EventArgs"/> instance containing the event data.</param></span> |
|
1 |
<span class="lnum"> 6: </span> <span class="rem">/// <remarks>author Petter Liu http://wintersun.cnblogs.com</remarks></span> |
|
1 |
<span class="lnum"> 7: </span> <span class="kwrd">private</span> <span class="kwrd">void</span> EntLibLogging_Error(<span class="kwrd">object</span> sender, EventArgs e) |
|
1 |
<span class="lnum"> 8: </span> { |
|
1 |
<span class="lnum"> 9: </span> var builder = <span class="kwrd">new</span> ConfigurationSourceBuilder(); |
|
1 |
<span class="lnum"> 10: </span> |
|
1 |
<span class="lnum"> 11: </span> builder.ConfigureInstrumentation() |
|
1 |
<span class="lnum"> 12: </span> .ForApplicationInstance(<span class="str">"MyApp"</span>) |
|
1 |
<span class="lnum"> 13: </span> .EnableLogging() |
|
1 |
<span class="lnum"> 14: </span> .EnablePerformanceCounters(); |
|
1 |
<span class="lnum"> 15: </span> |
|
1 |
<span class="lnum"> 16: </span> <span class="rem">//a single exception handling policy named MyPolicy for exceptions of type ArgumentNullException. </span> |
|
1 |
<span class="lnum"> 17: </span> <span class="rem">//The handler for this exception policy will log the exception to the General category (defined in the Logging Application Block configuration) </span> |
|
1 |
<span class="lnum"> 18: </span> <span class="rem">//as a warning with event ID 9000, wrap the ArgumentNullException with an InvalidOperationException, set the new exception message to MyMessage, and then re-throw the exception.</span> |
|
1 |
<span class="lnum"> 19: </span> builder.ConfigureExceptionHandling() |
|
1 |
<span class="lnum"> 20: </span> .GivenPolicyWithName(<span class="str">"MyPolicy"</span>) |
|
1 |
<span class="lnum"> 21: </span> .ForExceptionType<ArgumentNullException>() |
|
1 |
<span class="lnum"> 22: </span> .LogToCategory(<span class="str">"Exception"</span>) |
|
1 |
<span class="lnum"> 23: </span> .WithSeverity(System.Diagnostics.TraceEventType.Warning) |
|
1 |
<span class="lnum"> 24: </span> .UsingEventId(9000) |
|
1 |
<span class="lnum"> 25: </span> .WrapWith<InvalidOperationException>() |
|
1 |
<span class="lnum"> 26: </span> .UsingMessage(<span class="str">"MyMessage"</span>) |
|
1 |
<span class="lnum"> 27: </span> .ThenNotifyRethrow(); |
|
1 |
<span class="lnum"> 28: </span> |
|
1 |
<span class="lnum"> 29: </span> <span class="rem">//logging application </span> |
|
1 |
<span class="lnum"> 30: </span> builder.ConfigureLogging() |
|
1 |
<span class="lnum"> 31: </span> .WithOptions |
|
1 |
<span class="lnum"> 32: </span> .DoNotRevertImpersonation() |
|
1 |
<span class="lnum"> 33: </span> .LogToCategoryNamed(<span class="str">"Exception"</span>) |
|
1 |
<span class="lnum"> 34: </span> .SendTo.FlatFile(<span class="str">"Exception Logging File"</span>) |
|
1 |
<span class="lnum"> 35: </span> .FormatWith(<span class="kwrd">new</span> FormatterBuilder() |
|
1 |
<span class="lnum"> 36: </span> .TextFormatterNamed(<span class="str">"Text Formatter"</span>) |
|
1 |
<span class="lnum"> 37: </span> . UsingTemplate(<span class="str">"Timestamp: {timestamp}{newline}Message: {message}{newline}Category: {category}{newline}"</span>)) |
|
1 |
<span class="lnum"> 38: </span> .ToFile(<span class="str">"d:\\logs\\ExceptionsLog.log"</span>) |
|
1 |
<span class="lnum"> 39: </span> .SendTo.RollingFile(<span class="str">"Rolling Log files"</span>) |
|
1 |
<span class="lnum"> 40: </span> .RollAfterSize(1024) |
|
1 |
<span class="lnum"> 41: </span> .ToFile(<span class="str">"d:\\logs\\Rollinglog.log"</span>) |
|
1 |
<span class="lnum"> 42: </span> .LogToCategoryNamed(<span class="str">"General"</span>) |
|
1 |
<span class="lnum"> 43: </span> .WithOptions.SetAsDefaultCategory() |
|
1 |
<span class="lnum"> 44: </span> .SendTo.SharedListenerNamed(<span class="str">"Exception Logging File"</span>); |
|
1 |
<span class="lnum"> 45: </span> |
|
1 |
<span class="lnum"> 46: </span> var configSource = <span class="kwrd">new</span> DictionaryConfigurationSource(); |
|
1 |
<span class="lnum"> 47: </span> builder.UpdateConfigurationWithReplace(configSource); |
|
1 |
<span class="lnum"> 48: </span> EnterpriseLibraryContainer.Current = EnterpriseLibraryContainer.CreateDefaultContainer(configSource); |
|
1 |
<span class="lnum"> 49: </span> |
|
1 |
<span class="lnum"> 50: </span> var ex = HttpContext.Current.Server.GetLastError(); |
|
1 |
<span class="lnum"> 51: </span> var em = EnterpriseLibraryContainer.Current.GetInstance<ExceptionManager>(); |
|
1 |
<span class="lnum"> 52: </span> em.HandleException(ex.InnerException, <span class="str">"MyPolicy"</span>); |
|
1 |
<span class="lnum"> 53: </span> } |
注意上面的代码, 为了运行代码您需要引用以下程序集 Enterprise Library Share Common LibraryMicrosoft.Practices.ServiceLocationLogging Application BlockException Handling Application BlockException Handling Logging Provider 这里我们使用Fluent API配置, 因此没有配置XML文件. 所以不需要Web.Config中配置任何信息. 代码中有注释. 为了测试我们使用一个PAGE故意Throw 一个ArgumentNullException. 通过Server.GetLastError()获取Exception, 这时由名为MyPolicy策略处理异常. 对于ArgumentNullException把它们记录日志到名为Exception分类中,这个日志文件位于d:\\logs\\ExceptionLog.log.实际开发你完全按照你的需要来自定义策略. 然后这个日志文件中写出的内容是这样的:
|
1 |
----------------------------------------Timestamp: 2011-11-12 5:57:08Message: HandlingInstanceID: a99d005d-5f8d-4613-9522-2d60efb089aaAn exception of type <span class="str">'System.ArgumentNullException'</span> occurred and was caught.----------------------------------------------------------------------------11/12/2011 13:57:08Type : System.ArgumentNullException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089Message : Value cannot be <span class="kwrd">null</span>.Parameter name: Demo errorSource : MyWebHelp link : ParamName : Demo errorData : System.Collections.ListDictionaryInternalTargetSite : Void Page_Load(System.Object, System.EventArgs)Stack Trace : at MyWeb.About.Page_Load(Object sender, EventArgs e) <span class="kwrd">in</span> H:\My Project\DotNet40\TDD2010\WebHost\MyWeb\About.aspx.cs:line 14 at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)Additional Info:MachineName : USERTimeStamp : 2011-11-12 5:57:08FullName : Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35AppDomainName : 3e5cb21e-3-129655510216406250ThreadIdentity : WindowsIdentity : USER\PetterCategory: Exception |
由于我们日志模块我们配置还需要写Rollinglog.log文件,内容如下:
|
1 |
----------------------------------------Exception Warning: 9000 : Timestamp: 2011-11-12 5:57:08Message: HandlingInstanceID: a99d005d-5f8d-4613-9522-2d60efb089aaAn exception of type <span class="str">'System.ArgumentNullException'</span> occurred and was caught.----------------------------------------------------------------------------11/12/2011 13:57:08Type : System.ArgumentNullException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089Message : Value cannot be <span class="kwrd">null</span>.Parameter name: Demo errorSource : MyWebHelp link : ParamName : Demo errorData : System.Collections.ListDictionaryInternalTargetSite : Void Page_Load(System.Object, System.EventArgs)Stack Trace : at MyWeb.About.Page_Load(Object sender, EventArgs e) <span class="kwrd">in</span> H:\My Project\DotNet40\TDD2010\WebHost\MyWeb\About.aspx.cs:line 14 at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)Additional Info:MachineName : USERTimeStamp : 2011-11-12 5:57:08FullName : Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35AppDomainName : 3e5cb21e-3-129655510216406250ThreadIdentity : WindowsIdentity : USER\PetterCategory: ExceptionPriority: 0EventId: 9000Severity: WarningTitle:Enterprise Library Exception HandlingMachine: USERApp Domain: 3e5cb21e-3-129655510216406250ProcessId: 2444Process Name: C:\Program Files\Common Files\Microsoft Shared\DevServer\10.0\WebDev.WebServer40.exeThread Name: Win32 ThreadId:2748Extended Properties: ---------------------------------------- |
|
1 |
你可以看到上面的EventId=9000与我们之前在CODE中配置是相同的. <br /> |
|
1 |
在开源社区有一个组件<a href="http://code.google.com/p/elmah/" target="_blank">ELMAH</a>(Error Logging Modules and Handlers for ASP.NET),已实现Error处理发邮件,写DB,发送到SNS等功能. 我们随意来看下它的代码:<br />它就是基于IHttpModule的扩展,下面代码来ELMAH: |
|
1 |
<span class="lnum"> 1: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 2: </span> <span class="rem">/// Provides an abstract base class for <see cref="IHttpModule"/> that</span> |
|
1 |
<span class="lnum"> 3: </span> <span class="rem">/// supports discovery from within partial trust environments.</span> |
|
1 |
<span class="lnum"> 4: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 5: </span> <span class="kwrd">public</span> <span class="kwrd">abstract</span> <span class="kwrd">class</span> HttpModuleBase : IHttpModule |
|
1 |
<span class="lnum"> 6: </span> { |
|
1 |
<span class="lnum"> 7: </span> <span class="kwrd">void</span> IHttpModule.Init(HttpApplication context) |
|
1 |
<span class="lnum"> 8: </span> { |
|
1 |
<span class="lnum"> 9: </span> <span class="kwrd">if</span> (context == <span class="kwrd">null</span>) |
|
1 |
<span class="lnum"> 10: </span> <span class="kwrd">throw</span> <span class="kwrd">new</span> ArgumentNullException(<span class="str">"context"</span>); |
|
1 |
<span class="lnum"> 11: </span> |
|
1 |
<span class="lnum"> 12: </span> <span class="kwrd">if</span> (SupportDiscoverability) |
|
1 |
<span class="lnum"> 13: </span> HttpModuleRegistry.RegisterInPartialTrust(context, <span class="kwrd">this</span>); |
|
1 |
<span class="lnum"> 14: </span> |
|
1 |
<span class="lnum"> 15: </span> OnInit(context); |
|
1 |
<span class="lnum"> 16: </span> } |
|
1 |
<span class="lnum"> 17: </span> |
|
1 |
<span class="lnum"> 18: </span> <span class="kwrd">void</span> IHttpModule.Dispose() |
|
1 |
<span class="lnum"> 19: </span> { |
|
1 |
<span class="lnum"> 20: </span> OnDispose(); |
|
1 |
<span class="lnum"> 21: </span> } |
|
1 |
<span class="lnum"> 22: </span> |
|
1 |
<span class="lnum"> 23: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 24: </span> <span class="rem">/// Determines whether the module will be registered for discovery</span> |
|
1 |
<span class="lnum"> 25: </span> <span class="rem">/// in partial trust environments or not.</span> |
|
1 |
<span class="lnum"> 26: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 27: </span> <span class="kwrd">protected</span> <span class="kwrd">virtual</span> <span class="kwrd">bool</span> SupportDiscoverability |
|
1 |
<span class="lnum"> 28: </span> { |
|
1 |
<span class="lnum"> 29: </span> get { <span class="kwrd">return</span> <span class="kwrd">false</span>; } |
|
1 |
<span class="lnum"> 30: </span> } |
|
1 |
<span class="lnum"> 31: </span> |
|
1 |
<span class="lnum"> 32: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 33: </span> <span class="rem">/// Initializes the module and prepares it to handle requests.</span> |
|
1 |
<span class="lnum"> 34: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 35: </span> <span class="kwrd">protected</span> <span class="kwrd">virtual</span> <span class="kwrd">void</span> OnInit(HttpApplication application) {} |
|
1 |
<span class="lnum"> 36: </span> |
|
1 |
<span class="lnum"> 37: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 38: </span> <span class="rem">/// Disposes of the resources (other than memory) used by the module.</span> |
|
1 |
<span class="lnum"> 39: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 40: </span> <span class="kwrd">protected</span> <span class="kwrd">virtual</span> <span class="kwrd">void</span> OnDispose() {} |
|
1 |
<span class="lnum"> 41: </span> } |
|
1 |
这是ErrorLogModule实现之前HttpModuleBase: |
|
1 |
<span class="lnum"> 1: </span><span class="kwrd">public</span> <span class="kwrd">class</span> ErrorLogModule : HttpModuleBase, IExceptionFiltering |
|
1 |
<span class="lnum"> 2: </span> { |
|
1 |
<span class="lnum"> 3: </span> <span class="kwrd">public</span> <span class="kwrd">event</span> ExceptionFilterEventHandler Filtering; |
|
1 |
<span class="lnum"> 4: </span> <span class="kwrd">public</span> <span class="kwrd">event</span> ErrorLoggedEventHandler Logged; |
|
1 |
<span class="lnum"> 5: </span> |
|
1 |
<span class="lnum"> 6: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 7: </span> <span class="rem">/// Initializes the module and prepares it to handle requests.</span> |
|
1 |
<span class="lnum"> 8: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 9: </span> |
|
1 |
<span class="lnum"> 10: </span> <span class="kwrd">protected</span> <span class="kwrd">override</span> <span class="kwrd">void</span> OnInit(HttpApplication application) |
|
1 |
<span class="lnum"> 11: </span> { |
|
1 |
<span class="lnum"> 12: </span> <span class="kwrd">if</span> (application == <span class="kwrd">null</span>) |
|
1 |
<span class="lnum"> 13: </span> <span class="kwrd">throw</span> <span class="kwrd">new</span> ArgumentNullException(<span class="str">"application"</span>); |
|
1 |
<span class="lnum"> 14: </span> |
|
1 |
<span class="lnum"> 15: </span> application.Error += <span class="kwrd">new</span> EventHandler(OnError); |
|
1 |
<span class="lnum"> 16: </span> ErrorSignal.Get(application).Raised += <span class="kwrd">new</span> ErrorSignalEventHandler(OnErrorSignaled); |
|
1 |
<span class="lnum"> 17: </span> } |
|
1 |
<span class="lnum"> 18: </span> |
|
1 |
<span class="lnum"> 19: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 20: </span> <span class="rem">/// Gets the <see cref="ErrorLog"/> instance to which the module</span> |
|
1 |
<span class="lnum"> 21: </span> <span class="rem">/// will log exceptions.</span> |
|
1 |
<span class="lnum"> 22: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 23: </span> <span class="kwrd">protected</span> <span class="kwrd">virtual</span> ErrorLog GetErrorLog(HttpContext context) |
|
1 |
<span class="lnum"> 24: </span> { |
|
1 |
<span class="lnum"> 25: </span> <span class="kwrd">return</span> ErrorLog.GetDefault(context); |
|
1 |
<span class="lnum"> 26: </span> } |
|
1 |
<span class="lnum"> 27: </span> |
|
1 |
<span class="lnum"> 28: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 29: </span> <span class="rem">/// The handler called when an unhandled exception bubbles up to </span> |
|
1 |
<span class="lnum"> 30: </span> <span class="rem">/// the module.</span> |
|
1 |
<span class="lnum"> 31: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 32: </span> <span class="kwrd">protected</span> <span class="kwrd">virtual</span> <span class="kwrd">void</span> OnError(<span class="kwrd">object</span> sender, EventArgs args) |
|
1 |
<span class="lnum"> 33: </span> { |
|
1 |
<span class="lnum"> 34: </span> HttpApplication application = (HttpApplication) sender; |
|
1 |
<span class="lnum"> 35: </span> LogException(application.Server.GetLastError(), application.Context); |
|
1 |
<span class="lnum"> 36: </span> } |
|
1 |
<span class="lnum"> 37: </span> |
|
1 |
<span class="lnum"> 38: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 39: </span> <span class="rem">/// The handler called when an exception is explicitly signaled.</span> |
|
1 |
<span class="lnum"> 40: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 41: </span> <span class="kwrd">protected</span> <span class="kwrd">virtual</span> <span class="kwrd">void</span> OnErrorSignaled(<span class="kwrd">object</span> sender, ErrorSignalEventArgs args) |
|
1 |
<span class="lnum"> 42: </span> { |
|
1 |
<span class="lnum"> 43: </span> LogException(args.Exception, args.Context); |
|
1 |
<span class="lnum"> 44: </span> } |
|
1 |
<span class="lnum"> 45: </span> |
|
1 |
<span class="lnum"> 46: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 47: </span> <span class="rem">/// Logs an exception and its context to the error log.</span> |
|
1 |
<span class="lnum"> 48: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 49: </span> <span class="kwrd">protected</span> <span class="kwrd">virtual</span> <span class="kwrd">void</span> LogException(Exception e, HttpContext context) |
|
1 |
<span class="lnum"> 50: </span> { |
|
1 |
<span class="lnum"> 51: </span> <span class="kwrd">if</span> (e == <span class="kwrd">null</span>) |
|
1 |
<span class="lnum"> 52: </span> <span class="kwrd">throw</span> <span class="kwrd">new</span> ArgumentNullException(<span class="str">"e"</span>); |
|
1 |
<span class="lnum"> 53: </span> |
|
1 |
<span class="lnum"> 54: </span> <span class="rem">//</span> |
|
1 |
<span class="lnum"> 55: </span> <span class="rem">// Fire an event to check if listeners want to filter out</span> |
|
1 |
<span class="lnum"> 56: </span> <span class="rem">// logging of the uncaught exception.</span> |
|
1 |
<span class="lnum"> 57: </span> <span class="rem">//</span> |
|
1 |
<span class="lnum"> 58: </span> |
|
1 |
<span class="lnum"> 59: </span> ExceptionFilterEventArgs args = <span class="kwrd">new</span> ExceptionFilterEventArgs(e, context); |
|
1 |
<span class="lnum"> 60: </span> OnFiltering(args); |
|
1 |
<span class="lnum"> 61: </span> |
|
1 |
<span class="lnum"> 62: </span> <span class="kwrd">if</span> (args.Dismissed) |
|
1 |
<span class="lnum"> 63: </span> <span class="kwrd">return</span>; |
|
1 |
<span class="lnum"> 64: </span> |
|
1 |
<span class="lnum"> 65: </span> <span class="rem">//</span> |
|
1 |
<span class="lnum"> 66: </span> <span class="rem">// Log away...</span> |
|
1 |
<span class="lnum"> 67: </span> <span class="rem">//</span> |
|
1 |
<span class="lnum"> 68: </span> |
|
1 |
<span class="lnum"> 69: </span> ErrorLogEntry entry = <span class="kwrd">null</span>; |
|
1 |
<span class="lnum"> 70: </span> |
|
1 |
<span class="lnum"> 71: </span> <span class="kwrd">try</span> |
|
1 |
<span class="lnum"> 72: </span> { |
|
1 |
<span class="lnum"> 73: </span> Error error = <span class="kwrd">new</span> Error(e, context); |
|
1 |
<span class="lnum"> 74: </span> ErrorLog log = GetErrorLog(context); |
|
1 |
<span class="lnum"> 75: </span> <span class="kwrd">string</span> id = log.Log(error); |
|
1 |
<span class="lnum"> 76: </span> entry = <span class="kwrd">new</span> ErrorLogEntry(log, id, error); |
|
1 |
<span class="lnum"> 77: </span> } |
|
1 |
<span class="lnum"> 78: </span> <span class="kwrd">catch</span> (Exception localException) |
|
1 |
<span class="lnum"> 79: </span> { |
|
1 |
<span class="lnum"> 80: </span> <span class="rem">//</span> |
|
1 |
<span class="lnum"> 81: </span> <span class="rem">// IMPORTANT! We swallow any exception raised during the </span> |
|
1 |
<span class="lnum"> 82: </span> <span class="rem">// logging and send them out to the trace . The idea </span> |
|
1 |
<span class="lnum"> 83: </span> <span class="rem">// here is that logging of exceptions by itself should not </span> |
|
1 |
<span class="lnum"> 84: </span> <span class="rem">// be critical to the overall operation of the application.</span> |
|
1 |
<span class="lnum"> 85: </span> <span class="rem">// The bad thing is that we catch ANY kind of exception, </span> |
|
1 |
<span class="lnum"> 86: </span> <span class="rem">// even system ones and potentially let them slip by.</span> |
|
1 |
<span class="lnum"> 87: </span> <span class="rem">//</span> |
|
1 |
<span class="lnum"> 88: </span> |
|
1 |
<span class="lnum"> 89: </span> Trace.WriteLine(localException); |
|
1 |
<span class="lnum"> 90: </span> } |
|
1 |
<span class="lnum"> 91: </span> |
|
1 |
<span class="lnum"> 92: </span> <span class="kwrd">if</span> (entry != <span class="kwrd">null</span>) |
|
1 |
<span class="lnum"> 93: </span> OnLogged(<span class="kwrd">new</span> ErrorLoggedEventArgs(entry)); |
|
1 |
<span class="lnum"> 94: </span> } |
|
1 |
<span class="lnum"> 95: </span> |
|
1 |
<span class="lnum"> 96: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 97: </span> <span class="rem">/// Raises the <see cref="Logged"/> event.</span> |
|
1 |
<span class="lnum"> 98: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 99: </span> <span class="kwrd">protected</span> <span class="kwrd">virtual</span> <span class="kwrd">void</span> OnLogged(ErrorLoggedEventArgs args) |
|
1 |
<span class="lnum"> 100: </span> { |
|
1 |
<span class="lnum"> 101: </span> ErrorLoggedEventHandler handler = Logged; |
|
1 |
<span class="lnum"> 102: </span> |
|
1 |
<span class="lnum"> 103: </span> <span class="kwrd">if</span> (handler != <span class="kwrd">null</span>) |
|
1 |
<span class="lnum"> 104: </span> handler(<span class="kwrd">this</span>, args); |
|
1 |
<span class="lnum"> 105: </span> } |
|
1 |
<span class="lnum"> 106: </span> |
|
1 |
<span class="lnum"> 107: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 108: </span> <span class="rem">/// Raises the <see cref="Filtering"/> event.</span> |
|
1 |
<span class="lnum"> 109: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 110: </span> <span class="kwrd">protected</span> <span class="kwrd">virtual</span> <span class="kwrd">void</span> OnFiltering(ExceptionFilterEventArgs args) |
|
1 |
<span class="lnum"> 111: </span> { |
|
1 |
<span class="lnum"> 112: </span> ExceptionFilterEventHandler handler = Filtering; |
|
1 |
<span class="lnum"> 113: </span> |
|
1 |
<span class="lnum"> 114: </span> <span class="kwrd">if</span> (handler != <span class="kwrd">null</span>) |
|
1 |
<span class="lnum"> 115: </span> handler(<span class="kwrd">this</span>, args); |
|
1 |
<span class="lnum"> 116: </span> } |
|
1 |
<span class="lnum"> 117: </span> |
|
1 |
<span class="lnum"> 118: </span> <span class="rem">/// <summary></span> |
|
1 |
<span class="lnum"> 119: </span> <span class="rem">/// Determines whether the module will be registered for discovery</span> |
|
1 |
<span class="lnum"> 120: </span> <span class="rem">/// in partial trust environments or not.</span> |
|
1 |
<span class="lnum"> 121: </span> <span class="rem">/// </summary></span> |
|
1 |
<span class="lnum"> 122: </span> <span class="kwrd">protected</span> <span class="kwrd">override</span> <span class="kwrd">bool</span> SupportDiscoverability |
|
1 |
<span class="lnum"> 123: </span> { |
|
1 |
<span class="lnum"> 124: </span> get { <span class="kwrd">return</span> <span class="kwrd">true</span>; } |
|
1 |
<span class="lnum"> 125: </span> } |
|
1 |
<span class="lnum"> 126: </span> } |
|
1 |
更多的功能等待您去挖掘,我们在实际开发中按需选择.希望这篇POST对您开发有帮助.<br /> |
转自：http://www.cnblogs.com/wintersun/archive/2011/11/12/2246513.html
View Detailsusing System;using System.Data;using System.Configuration;using System.Web;using System.Web.Security;using System.Web.UI;using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;using System.Web.UI.HtmlControls; using System.IO; public partial class _Default : System.Web.UI.Page{ protected void Page_Load(object sender, EventArgs e) { string Path = Server.MapPath("1.txt"); string strings = "1232222"; FileAdd(Path, strings); } public static void FileAdd(string Path, string strings) { //实现一个System.IO.StreamWrite,使其以一种特定的编码向流中写入数据,AppendText数据追加到文件末尾 //这句也可以写成StreamWriter sw = new StreamWriter(Path, true, Encoding.GetEncoding("GB2312")); StreamWriter sw = File.AppendText(Path); //开始写入 sw.WriteLine(strings); //清理当前编码器的缓冲区,并将所有缓存数据写入基础流 sw.Flush(); sw.Close(); } } 转自：http://blog.sina.com.cn/s/blog_812ce0500100ywjb.html
View DetailsGlobal.asax 文件，有时候叫做 ASP.NET 应用程序文件，提供了一种在一个中心位置响应应用程序级或模块级事件的方法。你可以使用这个文件实现应用程序安全性以及其它一些任务。下面让我们详细看一下如何在应用程序开发工作中使用这个文件。 概述Global.asax 位 于应用程序根目录下。虽然 Visual Studio .NET 会自动插入这个文件到所有的 ASP.NET 项目中，但是它实际上是一个可选文件。 删除它不会出问题——当然是在你没有使用它的情况下。.asax 文件扩展名指出它是一个应用程序文件，而不是一个使 用 aspx 的 ASP.NET 文件。Global.asax 文件被配置为任何（通过 URL 的）直接 HTTP 请求都被自动 拒绝，所以用户不能下载或查看其内容。ASP.NET 页面框架能够自动识别出对Global.asax 文件所做的任何更改。 在 Global.asax 被更改后ASP.NET 页面框架会重新启动应用程序，包括关闭所有的浏览器会话，去除所有状态信息，并重新启动应用程序 域。 编程Global.asax 文件继承自HttpApplication 类，它维护一个HttpApplication 对象池，并在需要时将对象池中的对象分配给应用程序。Global.asax 文件包含以下事件：Application_Init：在应用程序被实例化或第一次被调用时，该事件被触发。对于所有的HttpApplication 对象实例，它都会被调用。Application_Disposed：在应用程序被销毁之前触发。这是清除以前所用资源的理想位置。Application_Error：当应用程序中遇到一个未处理的异常时，该事件被触发。Application_Start：在HttpApplication 类的第一个实例被创建时，该事件被触发。它允许你创建可以由所有HttpApplication 实例访问的对象。Application_End：在HttpApplication 类的最后一个实例被销毁时，该事件被触发。在一个应用程序的生命周期内它只被触发一次。Application_BeginRequest：在接收到一个应用程序请求时触发。对于一个请求来说，它是第一个被触发的事件，请求一般是用户输入的一个页面请求（URL）。Application_EndRequest：针对应用程序请求的最后一个事件。Application_PreRequestHandlerExecute：在 ASP.NET 页面框架开始执行诸如页面或 Web 服务之类的事件处理程序之前，该事件被触发。Application_PostRequestHandlerExecute：在 ASP.NET 页面框架结束执行一个事件处理程序时，该事件被触发。Applcation_PreSendRequestHeaders：在 ASP.NET 页面框架发送 HTTP 头给请求客户（浏览器）时，该事件被触发。Application_PreSendContent：在 ASP.NET 页面框架发送内容给请求客户（浏览器）时，该事件被触发。Application_AcquireRequestState：在 ASP.NET 页面框架得到与当前请求相关的当前状态（Session 状态）时，该事件被触发。Application_ReleaseRequestState：在 ASP.NET 页面框架执行完所有的事件处理程序时，该事件被触发。这将导致所有的状态模块保存它们当前的状态数据。Application_ResolveRequestCache：在 ASP.NET 页面框架完成一个授权请求时，该事件被触发。它允许缓存模块从缓存中为请求提供服务，从而绕过事件处理程序的执行。Application_UpdateRequestCache：在 ASP.NET 页面框架完成事件处理程序的执行时，该事件被触发，从而使缓存模块存储响应数据，以供响应后续的请求时使用。Application_AuthenticateRequest：在安全模块建立起当前用户的有效的身份时，该事件被触发。在这个时候，用户的凭据将会被验证。Application_AuthorizeRequest：当安全模块确认一个用户可以访问资源之后，该事件被触发。Session_Start：在一个新用户访问应用程序 Web 站点时，该事件被触发。 Session_End：在一个用户的会话超时、结束或他们离开应用程序 Web 站点时，该事件被触发。Application_Error 事件显示一个简单的消息用以说明发生的错误。 这个事件列表看起来好像多得吓人，但是在不同环境下这些事件可能会非常有用。使用这些事件的一个关键问题是知道它们被触发的顺序。Application_Init 和Application_Start 事件在应用程序第一次启动 时被触发一次。相似地，Application_Disposed 和 Application_End 事件在应用程序终止时被触发一次。此外，基于会 话的事件（Session_Start 和 Session_End）只在用户进入和离开站点时被使用。其余的事件则处理应用程序请求，这些事件被触发的 顺序是：Application_BeginRequestApplication_AuthenticateRequestApplication_AuthorizeRequestApplication_ResolveRequestCacheApplication_AcquireRequestStateApplication_PreRequestHandlerExecuteApplication_PreSendRequestHeadersApplication_PreSendRequestContent<<执行代码>>Application_PostRequestHandlerExecuteApplication_ReleaseRequestStateApplication_UpdateRequestCacheApplication_EndRequest 这些事件常被用于安全性方面。 转自：http://www.cnblogs.com/xiaopin/archive/2010/08/31/1813747.html
View Detailsweb.config是asp.net中保存配置信息（比如数据库连接字符串等）的重要文件。它是基于xml的文本文件方式放在Web应用程序的任何目录中，并且默认不随源文件编译到Dll中，而运行环境随时监视着它是否有改变，一但有变动，系统会自动重新加载里面的最新内容。 一、 配置文件保存位置 .net的默认配置文件保存在“windows目录\Microsoft.NET\Framework\对应.net版本\config”文件夹下面。不同的操作系统windows目录不一样，我们在命令行下输入“echo %windir%”查看windows目录所在的位置。 图：web.config所在的目录 Asp.net中有两个非常重要的配置文件，分别是machine.config和web.config，它们都位于config文件夹下面。这两个文件一般不需要我们手工是维护它，保持默认即可。但针对asp.net应用程序，它自身会有0个，1个或者多个web.config配置文件，多个配置文件会存在加载顺序问题。下节会介绍。 注意，传说中.net3.0和.net3.5只是在.net2.0的基础上扩充中，所以还是没用的.net2.0的配置文件。它们连config这个目录都没有。 二、 配置文件加载顺序 IIS在Asp.net网站启动时，会加载配置文件中的配置信息，然后缓存这些信息，不会每次要用都去读取配置文件，只是IIS会随时监视着这些文件的变化，一量有变化，它会重新去读取并缓存配置信息。 Asp.net网站运行时会按照以下方式加载配置文件中的节点信息： 1) 如果在当前运行页面所在的目录下有web.config文件，则查找是否存在所需要的节点，如果存在则返回结果，并停止下一步地查找。 2) 如里所在目录不存在web.config配置或者配置文件里没有所需要的节点，则查找它所在的上一级目录的配置文件中的节点，直到网站根目录。（问题：IIS6中的虚拟目录算不算根目录） 3) 如果网站根目录中都不存在web.config或者所需要的配置节点，转而到“windows目录\Microsoft.NET\Framework\对应.net版本\config\web.config”中去查找。 4) 如果第3条中还没找到，继续到“windows目录\Microsoft.NET\Framework\对应.net版本\config\machine.config”中去查找。 5) 如果还没找到，那就报错吧。 存在两个问题 1) IIS6中的虚拟目录算不算根目录。 2) 在系统运行时，在一个原本没有web.config的目录中手工加上一个web.config，会不会自动加载。 三、 配置文件节点介绍 Web.config文件是一个xml文本文件，它的根节点为<configuration>,该节点下包含常见的子节点有：<configSections>、<appSettings>、<connectionStrings>（保存数据库连接字符串）、<location>和<system.web>。下面针对各节点配置进行介绍。 1. <configSections> configSections 元素指定了配置节和处理程序声明。由于 ASP.NET 不对如何处理配置文件内的设置作任何假设，因此这非常必要。但 ASP.NET 会将配置数据的处理委托给配置节处理程序。配置结构信息如下： <configSections> <!--定义配置节处理程序与配置元素之间的关联。--> <section /> <!--定义配置节处理程序与配置节之间的关联。--> <sectionGroup /> <!--移除对继承的节和节组的引用。--> <remove /> <!--移除对继承的节和节组的所有引用，只允许由当前 section 和 sectionGroup 元素添加的节和节组。--> <clear/> </configSections> 每个 section 元素标识一个配置节或元素以及对该配置节或元素进行处理的关联 ConfigurationSection 派生类。可以在 sectionGroup 元素中对 section 元素进行逻辑分组，以对 section 元素进行组织并避免命名冲突。section 和 sectionGroup 元素包含在 configSections 元素中。 如果配置文件中包含 configSections 元素，则 configSections 元素必须是 configuration 元素的第一个子元素。 下面我们来示例写一个自定义配置信息，并完成它的SectionHandler，首先我们在<configuration>节点下添加configSections。 <configuration> <configSections> <sectionGroup name="mySectionGroup"> <section name="mySection" requirePermission="true" type="ConfigTest.SectionHandler.MySectionHandler,ConfigTest.SectionHandler" /> […]
View Details本文From hongshengpeng 解决ASP.NET 4.0 "A potentially dangerous Request.Form value was detected from the client". 错误在.net中，Request时出现有HTML或Javascript等字符串时，系统会认为是危险性值。立马报错。（在.aspx文件头中加入这句： <%@ Page validateRequest="false" %>，但还是出现相同错误） 或是修改web.config文件: <configuration> < system.web> <pages validateRequest="false" /> < /system.web> < /configuration> 但错误依旧。对.NET 4.0, 应该加上requestValidationMode="2.0" to the httpRuntime configuration section of the web.config :<httpRuntime requestValidationMode="2.0"/>（这句重要） 结构：<configuration> <system.web> <httpRuntime requestValidationMode="2.0">
View Details本文将揭示.NET 4.0中的3个新特性：图表控件、SEO支持以及ASP.NET 4可扩展的输出缓存。 图表控件 微软向开发者提供了大量可免费下载的图表控件，可以在.NET 3.5 ASP.NET或WinForms项目中使用这些控件。要想在Visual Studio 2008中使用这些控件则需要安装一个插件，该插件提供了VS工具箱及智能集成功能。现在这些控件已经集成到了.NET 4.0中，这样就无需再去下载额外的插件了。Samples Environment for MS Chart Controls提供了这些控件的使用示例。下图是示例的运行截图： ASP.NET 4.0 SEO 微软发布了一个SEO Toolkit并集成到了IIS 7中，同时可以在IIS Manager中运行。除了可以创建站点地图和地图索引外，该工具集还能够从SEO的视角分析站点情况，在出现SEO规则违例时生成报告：创建错误描述并给出进一步的改进提示。这些规则有：重复的文件、重复的标题、没有内容、过多的内容等等。该工具集会从性能视角分析站点，识别出运行缓慢或是会访问很多资源的页面。我们还可以通过增加自定义规则来扩展该工具集。 虽然该SEO Toolkit需要运行在IIS Manager上，但并不需要在服务器上安装别的东西。此外，它还可以对所有操作系统上的所有Web服务器进行分析。Scott Guthrie总结了可以进一步提升SEO的ASP.NET 4.0中的新特性，如下： ◆Page.MetaKeywords与Page.MetaDescription； ◆ASP.NET Web Forms的URL Routing支持； ◆Response.RedirectPermanent()。 我们可以通过Page类的MetaKeywords和MetaDescription属性以编程的方式设定站点的关键词和描述。Guthrie阐述了这么做的意义所在： ASP.NET 4.0的<head>服务器端控件会在输出页面的<head>部分时使用到他们，这对于使用了母板页的站点非常有用——<head>部分位于.master文件中，这就与包含了具体页面内容的.aspx文件独立开来，现在可以在.aspx页面中设定新的MetaKeywords和MetaDescription属性并通过母板页中的<head>控件自动生成其值。URL Routing会将外部URL转换为内部的。通过这种方式，站点可以公开SEO友好的URL，但却可以在内部使用不同的链接。这对于遗留站点来说非常有用。 我们应该使用Response.RedirectPermanent()方法而非Response.Redirect()，因为后者会生成一个临时的重定向，这导致搜索引擎在多个重定向之间跳跃，降低了页面的等级。Guthrie解释了RedirectPermanent()的工作方式： ASP.NET 4.0引入了一个全新的Response.RedirectPermanent(string url)辅助方法，可以通过HTTP 301（moved permanently）响应进行重定向。这样，搜索引擎和其他能够识别出永久重定向的user agents就会存储并使用与内容关联的新URL。这么做会为页面内容加上索引，同时提升搜索引擎对页面的PR（Page Ranking）值。 ASP.NET 4.0输出缓存 自从1.0开始，ASP.NET就拥有了一个输出缓存来存储页面和资源以提供更快的响应速度，但存储位置只能在内存中。ASP.NET 4.0提供了一个扩展点，可以在本地/远程磁盘、数据库、分布式缓存引擎（如velocity、memcached）甚至是云中增加多个缓存。 转自：51cto.com 原文标题：三方面诠释.NET 4.0的新特性
View Details1、在.net中，windows服务的实现类必需继承于System.ServiceProcess.ServiceBase public partial class myService : ServiceBase { } 2、在windows服务的实现类的构造函数中进行必要的初始化工作，如设置系统标识服务的简短名称等。 public partial class myService : ServiceBase { public SqlBackupService() { ServiceName = "Myservice"; AutoLog = false; CanStop = true; } } 3、重写OnStar和OnStop函数，在OnStar里实现具体功能，OnStop中释放OnStat中创建的资源。 public partial class myService : ServiceBase { private int tickcount = 0; private System.Timers.Timer t = null; public SqlBackupService() { ServiceName = "Myservice"; AutoLog = false; CanStop = true; } protected override void OnStart(string[] args) { Console.WriteLine("Myservice start …"); //建立定时器 t = new System.Timers.Timer(10000); t.AutoReset = true; //每隔10000毫秒触发一次 t.Elapsed += new System.Timers.ElapsedEventHandler(myWork); t.Start(); […]
View Details_ _ DbType 说明 OleDbType 说明 SqlDbType 说明 Boolean 简单类型，表示 true 或 false 的布尔值。 Boolean 布尔值 (DBTYPE_BOOL)。它映射到 Boolean。 Bit Boolean。无符号数值，可以是 0、1 或 nullNothingnullptrnull 引用（在 Visual Basic 中为 Nothing）。 SByte 整型，表示值介于 -128 到 127 之间的有符号 8 位整数。 TinyInt 8 位带符号的整数 (DBTYPE_I1)。它映射到 SByte。 Byte 一个 8 位无符号整数，范围在 0 到 255 之间。 UnsignedTinyInt 8 位无符号整数 (DBTYPE_UI1)。它映射到 Byte。 TinyInt Byte。8 位的无符号整数。 Int16 整型，表示值介于 -32768 到 32767 之间的有符号 16 位整数。 SmallInt 16 位带符号的整数 (DBTYPE_I2)。它映射到 Int16。 SmallInt Int16。16 位的有符号整数。 Int32 整型，表示值介于 -2147483648 到 2147483647 之间的有符号 […]
View Details