Category Archives: Asp.net

Asp.net Web Applicatoin实现自定义HttpModule拦截异常处理

Asp.net的NamePipe机制给我们提供了很多扩展性. 使用HttpModule我们可能实现的有: 强制站点范围的Cookie策略集中化监控与日志编写设置与删除HTTP头控制response输出,如删除多余空白字符 Session管理认证与受权下面我们来看如何实现自定义异常处理:

1	1: public class ErrorModule:IHttpModule

2: {

1	3: #region IHttpModule Members

1	5: /// <summary>

1	6: /// Disposes of the resources (other than memory) used by the module that implements <see cref="T:System.Web.IHttpModule"/>.

1	7: /// </summary>

1	8: public void Dispose()

9: {

1	10: //do nothing

11: }

12:

1	13: /// <summary>

1	14: /// Initializes a module and prepares it to handle requests.

1	15: /// </summary>

1	16: /// <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>

1	17: public void Init(HttpApplication context)

18: {

1	19: context.Error += new EventHandler(customcontext_Error);

20: }

21:

1	22: private void customcontext_Error(object sender, EventArgs e)

23: {

1	24: HttpContext ctx = HttpContext.Current;

1	25: HttpResponse response = ctx.Response;

1	26: HttpRequest request = ctx.Request;

27:

1	28: Exception exception = ctx.Server.GetLastError();

29:

1	30: var sboutput = new StringBuilder();

1	31: sboutput.Append("Querystring:<p/>");

1	32: //Get out the query string

1	33: int count = request.QueryString.Count;

1	34: for (int i = 0; i < count; i++)

35: {

1	36: sboutput.AppendFormat("<br/> {0}:-- {1} ", request.QueryString.Keys[i], request.QueryString[i]);

37: }

1	38: //Get out the form collection info

1	39: sboutput.Append("<p>-------------------------<p/>Form:<p/>");

1	40: count = request.Form.Count;

1	41: for (int i = 0; i < count; i++)

42: {

1	43: sboutput.AppendFormat("<br/> {0}:-- {1} -- <br/>", request.Form.Keys[i], request.Form[i]);

44: }

1	45: sboutput.Append("<p>-------------------------<p/>ErrorInfo:<p/>");

1	46: sboutput.AppendFormat(@"Your request could not processed. Please press the back button on your browser and try again.<br/>

1	47: If the problem persists, please contact technical support<p/>

1	48: Information below is for technical support:<p/>

1	49: <p/>URL:{0}<p/>Stacktrace:---<br/>{1}<p/>InnerException:<br/>{2}"

1	50: , ctx.Request.Url, exception.InnerException.StackTrace, exception.InnerException);

51:

1	52: response.Write(sboutput.ToString());

53:

1	54: // To let the page finish running we clear the error

1	55: ctx.Server.ClearError();

56: }

57:

1	58: #endregion

59:

60: }

上面的代码实现了IHttpModule接口, 实现基于HttpApplication.Error事件, 接着我们自定义输出了一些信息,包括Form,QueryString. 最后把原来的Error信息清除了,这样你看到以前那个黄页了. 这个自定义的Module可以用于调试Web应用程序使用. Web.config中配置:

1	<httpModules>

1	<add name="ErrorLoggingModule" type="MyWeb.ErrorModule"/>

1	</httpModules>

实际开发中,我们可以做的事儿很多,对这些信息记日志,发邮件. 如下, 我们演示使用Enterprise Library 做异常处理并日志记录,部分代码如下:

1	1: /// <summary>

1	2: /// Handles the Error event of the EntLibLogging control.

1	3: /// </summary>

1	4: /// <param name="sender">The source of the event.</param>

1	5: /// <param name="e">The <see cref="System.EventArgs"/> instance containing the event data.</param>

1	6: /// <remarks>author Petter Liu http://wintersun.cnblogs.com</remarks>

1	7: private void EntLibLogging_Error(object sender, EventArgs e)

8: {

1	9: var builder = new ConfigurationSourceBuilder();

10:

1	11: builder.ConfigureInstrumentation()

1	12: .ForApplicationInstance("MyApp")

1	13: .EnableLogging()

1	14: .EnablePerformanceCounters();

15:

1	16: //a single exception handling policy named MyPolicy for exceptions of type ArgumentNullException.

1	17: //The handler for this exception policy will log the exception to the General category (defined in the Logging Application Block configuration)

1	18: //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.

1	19: builder.ConfigureExceptionHandling()

1	20: .GivenPolicyWithName("MyPolicy")

1	21: .ForExceptionType<ArgumentNullException>()

1	22: .LogToCategory("Exception")

1	23: .WithSeverity(System.Diagnostics.TraceEventType.Warning)

1	24: .UsingEventId(9000)

1	25: .WrapWith<InvalidOperationException>()

1	26: .UsingMessage("MyMessage")

1	27: .ThenNotifyRethrow();

28:

1	29: //logging application

1	30: builder.ConfigureLogging()

1	31: .WithOptions

1	32: .DoNotRevertImpersonation()

1	33: .LogToCategoryNamed("Exception")

1	34: .SendTo.FlatFile("Exception Logging File")

1	35: .FormatWith(new FormatterBuilder()

1	36: .TextFormatterNamed("Text Formatter")

1	37: . UsingTemplate("Timestamp: {timestamp}{newline}Message: {message}{newline}Category: {category}{newline}"))

1	38: .ToFile("d:\\logs\\ExceptionsLog.log")

1	39: .SendTo.RollingFile("Rolling Log files")

1	40: .RollAfterSize(1024)

1	41: .ToFile("d:\\logs\\Rollinglog.log")

1	42: .LogToCategoryNamed("General")

1	43: .WithOptions.SetAsDefaultCategory()

1	44: .SendTo.SharedListenerNamed("Exception Logging File");

45:

1	46: var configSource = new DictionaryConfigurationSource();

1	47: builder.UpdateConfigurationWithReplace(configSource);

1	48: EnterpriseLibraryContainer.Current = EnterpriseLibraryContainer.CreateDefaultContainer(configSource);

49:

1	50: var ex = HttpContext.Current.Server.GetLastError();

1	51: var em = EnterpriseLibraryContainer.Current.GetInstance<ExceptionManager>();

1	52: em.HandleException(ex.InnerException, "MyPolicy");

53: }

注意上面的代码, 为了运行代码您需要引用以下程序集 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.实际开发你完全按照你的需要来自定义策略. 然后这个日志文件中写出的内容是这样的:

----------------------------------------Timestamp: 2011-11-12 5:57:08Message: HandlingInstanceID: a99d005d-5f8d-4613-9522-2d60efb089aaAn exception of type 'System.ArgumentNullException' 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 null.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) in 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文件,内容如下:

----------------------------------------Exception Warning: 9000 : Timestamp: 2011-11-12 5:57:08Message: HandlingInstanceID: a99d005d-5f8d-4613-9522-2d60efb089aaAn exception of type 'System.ArgumentNullException' 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 null.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) in 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中配置是相同的.

1 2	在开源社区有一个组件<a href="http://code.google.com/p/elmah/" target="_blank"><span style="color:#E3272D;">ELMAH</span></a>(Error Logging Modules and Handlers for ASP.NET),已实现Error处理发邮件,写DB,发送到SNS等功能. 我们随意来看下它的代码: 它就是基于IHttpModule的扩展,下面代码来ELMAH:

1	1: /// <summary>

1	2: /// Provides an abstract base class for <see cref="IHttpModule"/> that

1	3: /// supports discovery from within partial trust environments.

1	4: /// </summary>

1	5: public abstract class HttpModuleBase : IHttpModule

6: {

1	7: void IHttpModule.Init(HttpApplication context)

8: {

1	9: if (context == null)

1	10: throw new ArgumentNullException("context");

11:

1	12: if (SupportDiscoverability)

1	13: HttpModuleRegistry.RegisterInPartialTrust(context, this);

14:

1	15: OnInit(context);

16: }

17:

1	18: void IHttpModule.Dispose()

19: {

1	20: OnDispose();

21: }

22:

1	23: /// <summary>

1	24: /// Determines whether the module will be registered for discovery

1	25: /// in partial trust environments or not.

1	26: /// </summary>

1	27: protected virtual bool SupportDiscoverability

28: {

1	29: get { return false; }

30: }

31:

1	32: /// <summary>

1	33: /// Initializes the module and prepares it to handle requests.

1	34: /// </summary>

1	35: protected virtual void OnInit(HttpApplication application) {}

36:

1	37: /// <summary>

1	38: /// Disposes of the resources (other than memory) used by the module.

1	39: /// </summary>

1	40: protected virtual void OnDispose() {}

41: }

1	这是ErrorLogModule实现之前HttpModuleBase:

1	1: public class ErrorLogModule : HttpModuleBase, IExceptionFiltering

2: {

1	3: public event ExceptionFilterEventHandler Filtering;

1	4: public event ErrorLoggedEventHandler Logged;

1	6: /// <summary>

1	7: /// Initializes the module and prepares it to handle requests.

1	8: /// </summary>

1	10: protected override void OnInit(HttpApplication application)

11: {

1	12: if (application == null)

1	13: throw new ArgumentNullException("application");

14:

1	15: application.Error += new EventHandler(OnError);

1	16: ErrorSignal.Get(application).Raised += new ErrorSignalEventHandler(OnErrorSignaled);

17: }

18:

1	19: /// <summary>

1	20: /// Gets the <see cref="ErrorLog"/> instance to which the module

1	21: /// will log exceptions.

1	22: /// </summary>

1	23: protected virtual ErrorLog GetErrorLog(HttpContext context)

24: {

1	25: return ErrorLog.GetDefault(context);

26: }

27:

1	28: /// <summary>

1	29: /// The handler called when an unhandled exception bubbles up to

1	30: /// the module.

1	31: /// </summary>

1	32: protected virtual void OnError(object sender, EventArgs args)

33: {

1	34: HttpApplication application = (HttpApplication) sender;

1	35: LogException(application.Server.GetLastError(), application.Context);

36: }

37:

1	38: /// <summary>

1	39: /// The handler called when an exception is explicitly signaled.

1	40: /// </summary>

1	41: protected virtual void OnErrorSignaled(object sender, ErrorSignalEventArgs args)

42: {

1	43: LogException(args.Exception, args.Context);

44: }

45:

1	46: /// <summary>

1	47: /// Logs an exception and its context to the error log.

1	48: /// </summary>

1	49: protected virtual void LogException(Exception e, HttpContext context)

50: {

1	51: if (e == null)

1	52: throw new ArgumentNullException("e");

53:

54: //

1	55: // Fire an event to check if listeners want to filter out

1	56: // logging of the uncaught exception.

57: //

58:

1	59: ExceptionFilterEventArgs args = new ExceptionFilterEventArgs(e, context);

1	60: OnFiltering(args);

61:

1	62: if (args.Dismissed)

1	63: return;

64:

65: //

1	66: // Log away...

67: //

68:

1	69: ErrorLogEntry entry = null;

70:

71: try

72: {

1	73: Error error = new Error(e, context);

1	74: ErrorLog log = GetErrorLog(context);

1	75: string id = log.Log(error);

1	76: entry = new ErrorLogEntry(log, id, error);

77: }

1	78: catch (Exception localException)

79: {

80: //

1	81: // IMPORTANT! We swallow any exception raised during the

1	82: // logging and send them out to the trace . The idea

1	83: // here is that logging of exceptions by itself should not

1	84: // be critical to the overall operation of the application.

1	85: // The bad thing is that we catch ANY kind of exception,

1	86: // even system ones and potentially let them slip by.

87: //

88:

1	89: Trace.WriteLine(localException);

90: }

91:

1	92: if (entry != null)

1	93: OnLogged(new ErrorLoggedEventArgs(entry));

94: }

95:

1	96: /// <summary>

1	97: /// Raises the <see cref="Logged"/> event.

1	98: /// </summary>

1	99: protected virtual void OnLogged(ErrorLoggedEventArgs args)

100: {

1	101: ErrorLoggedEventHandler handler = Logged;

102:

1	103: if (handler != null)

1	104: handler(this, args);

105: }

106:

1	107: /// <summary>

1	108: /// Raises the <see cref="Filtering"/> event.

1	109: /// </summary>

1	110: protected virtual void OnFiltering(ExceptionFilterEventArgs args)

111: {

1	112: ExceptionFilterEventHandler handler = Filtering;

113:

1	114: if (handler != null)

1	115: handler(this, args);

116: }

117:

1	118: /// <summary>

1	119: /// Determines whether the module will be registered for discovery

1	120: /// in partial trust environments or not.

1	121: /// </summary>

1	122: protected override bool SupportDiscoverability

123: {

1	124: get { return true; }

125: }

126: }

1	更多的功能等待您去挖掘,我们在实际开发中按需选择.希望这篇POST对您开发有帮助.

转自：http://www.cnblogs.com/wintersun/archive/2011/11/12/2246513.html

龙生 19 Feb 2013

View Details

.net网站出现:不能使用；文件已在使用中

今天分析iislog 发现一堆 “不能使用；文件已在使用中” fuck…. 还不少呢！Google了一下，。找到了问题所在整站，是asp+acc 的。。。所以只给了acc的数据库权限。。数据库目录是只读的、。解决办法数据库目录，给webuser加上写权限。。。立刻生成了个.ldb 。。。顺便解释下，什么是ldb ldb 文件是由共享数据库的使用者自动创建以及删除得。.LDB 文件建立并存储计算机名、用户名以及放置扩展域锁的。 .LDB 文件一般与 .MDB 同名，并且与 .MDB 文件在相同目录，在 .MDB 文件被打开时建立并锁定。举个例子，如果你打开 c:\northwind.mdb 文件后 c:\northwind.ldb 文件会自动被建立并被锁定。当最后一个用户关闭共享数据库时 .ldb 文件会被自动删除。但是当用户没有正常关闭数据库或者数据库已经被标记为损坏，那么 .LDB 文件不会被自动删除，因为 .LDB 文件中存储着数据库损坏时谁正在使用该数据库。权限问题：记得要给予 .LDB 文件所在的文件夹一定的权限。–我就没给。。虽然可以用，但是影响了性能。。如果你准备共享一个数据库，该 .MDB 文件应该被放置在一个用户拥有读取、写入、建立、删除权限的目录中（NTSF格式）。即使你要求每个用户有不同的文件权限（比如，只读或者可读写），所有能够共享该数据的用户对该目录都应该拥有读取、写入、建立的权限，但是你可以分配用户对某个 .MDB 文件只拥有只读权限。注意：如果用独占方式打开某个数据库，那么 MS JET DB 将不会建立 .LDB 文件，此时用户对目录的权限只要求有读取和写入两个权限即可。 .ldb 文件的内容： MS JET DB ENGINE 会为每个以共享方式打开数据库的使用者在 .LDB 文件中创建一个条目，每个条目的大小是 64 字节。前面 32 字节保存计算机名，后面 32 字节保存用户名。JET DB ENGINE 支持的最大用户数是 255，因此 .LDB 文件的大小不会超过 16 KB。当一个用户关闭一个共享数据库时，该用户在 .LDB 文件中的条目不会立即被删除，可是该条目会在下一个用户打开这个数据库时被覆盖。这也就意味着你不能通过 .LDB 文件来唯一确定谁是某个数据库的当前使用者。 .LDB 文件的使用方法： JET DB ENGINE 使用 .LDB 文件中的信息来确定谁锁定了数据，谁正在写入被其他人锁定的数据。如果 JET DB ENGINE 发现有其他用户的锁定冲突，它会读取 .LDB 文件以获取计算机名与用户名谁锁定了文件或者记录。在多数锁定冲突情况下，你会在存储记录时得到一个 “写入冲突”的提示并且取消你所做的修改。在有些情况下你会得到如下提示： Couldn”t lock table <table name>; currently in use by user <security name> on computer <computer name>. 注意：上述关于 .LDB 文件的信息与数据库文件无关。如果一个 .LDB 文件损坏，数据库文件仍然能够工作正常。但是写入冲突的提示消息中<security name>这个部分你可能会看见一串不知所云的文字。参考：在 Access 2000 中，你可以用 VBA 来输出某个数据库的所有登陆用户的信息。关于此代码请参考： 198755 ACC2000: Checking Who Logged into Database with Jet UserRoster 转自：http://rogermmg.blog.163.com/blog/static/117472889201112343341825/

龙生 19 Feb 2013

View Details

详解在IIS中配置并运行WCF服务

【IT168 技术文档】WCF是Microsoft为构建面向服务的应用提供的分布式通信编程框架，是.NET Framework 3.5的重要组成部分。使用该框架，开发人员可以构建跨平台、安全、可靠和支持事务处理的企业级互联应用解决方案。　在IIS中运行服务　　之前我们让Derivatives Calculator服务在一个.NET可执行文件中运行，在这个练习中，我们将让服务在IIS中运行。　　利用IIS作为宿主程序来运行WCF服务通常有许多好处。　　·将项目构建到\bin目录中　　为了方便部署，我们需要对服务项目进行配置，让它编译到一个bin目录中。　　1. 在Solution Explorer中右键单击DerivativesCalculatorService项目并选择Properties菜单项。　　2. 在Project designer中，单击Build选项卡。　　3. 将Output path从bin\Debug\改为bin\，如图所示。 Project designer中经过调整的Output path属性　　4. 选择File | Save All菜单项。　　5. 选择File | Close菜单项来关闭Project designer。　　现在，在构建服务时产生的所有文件都会被输出到\bin目录中。　　·添加一个.svc文件　　为了让WCF服务能够在IIS中运行，我们需要用一种特殊的内容文件(.svc文件)表示它。这种模型和ASMX页面在IIS中的表示方法类似。.svc文件包含一个WCF专用的处理指示符(@ServiceHost)，这个指示符告诉WCF运行库在收到消息时激活服务。　　1. 在Solution Explorer中右键单击DerivativesCalculatorService项目并选择Add | New Item菜单项。　　2. 在Add New Item对话框中，选择Text File模板。 wordend 相关阅读：　　3. 在Name文本框中输入Service.svc。　　4. Add New Item对话框看起来应该如图所示。添加一个svc文件　　5. 单击Add按钮。　　6. 在Service.svc文件中添加下面这行语句。 Code highlighting produced by Actipro CodeHighlighter (freeware)http://www.CodeHighlighter.com/ <%@ServiceHost Service="DerivativesCalculatorService.Calculator" […]

龙生 15 Oct 2012

View Details

HTTP 错误 500.19 Internal Server Error的解决方法

以下从网络中搞定我的Win7下IIS错误： HTTP 错误 500.19 Internal Server Error 第一种可能,能解决一部分问题 http://wenku.baidu.com/view/c5cb4a08bb68a98271fefa3f.html 第二种可能,解决另外一部分问题经过检查发现是由于先安装vs2008后安装iis的缘故，只需重新注册下AspNet就可以了，具体步骤如下 1 打开运行，输入cmd进入到命令提示符窗口。 2 进入到C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 目录。 3 输入aspnet_regiis.exe –i 执行既可注意：如果系统为64位第二步的路径为C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727 第三种可能解决方法: Win7下我碰到的问题 WIN7下.Net开发遇到的又一问题：HTTP 错误 500.19 – Internal Server Error，无法访问请求的页面，因为该页的相关配置数据无效。详细错误信息模块 IIS Web Core 通知 BeginRequest 处理程序尚未确定错误代码 0x80070021 配置错误不能在此路径中使用此配置节。如果在父级别上锁定了该节，便会出现这种情况。锁定是默认设置的(overrideModeDefault="Deny")，或者是通过包含 overrideMode="Deny" 或旧有的 allowOverride="false" 的位置标记明确设置的。配置源 219: <add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></modules> 220: <handlers> 221: <remove name="WebServiceHandlerFactory-Integrated"/> […]

龙生 08 Oct 2012

View Details

如何在ashx页面获取Session值

在一般事务处理页面，可以轻松的得到 Request,Response对象，从而进行相应的操作，如下： HttpRequest Request = context.Request; HttpResponse Response = context.Response; 但是要得到 Session的值就没有那么简单了。比如你要在ashx得到保存在Session中的登录帐号Session["userAccount"] 如果你只是context.Session["userAccount"]的话是会报 “未将对象引用设置到对象的实例”的异常所以，如果要想取Session中的值，需要如下所示 1、引入命名空间： using System.Web.SessionState; 2、实现IRequiresSessionState接口，具体如下 /// <summary>/// $codebehindclassname$ 的摘要说明/// </summary>[WebService(Namespace = "http://tempuri.org/")][WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]public class AddUserInfo : IHttpHandler,IRequiresSessionState //就是这样显示的实现一下，不用实现什么方法{ public void ProcessRequest(HttpContext context){ 　　　　　　//… 　　　　　 //这样你就可以如下操作了 if(context.Session["userAccount"] != null) 　　　　　　{ 　　　　　　　　string account = context.Session["userAccount"].ToString(); 　　　　　　} 　　　　　　//…继续下面的代码　　　　} 　　} FROM URL:http://www.cnblogs.com/vihone/archive/2010/06/04/1751490.html

龙生 18 Sep 2012

View Details

SWFUpload V2.2.0 说明文档

SWFUpload V2.2.0 说明文档更新时间：2008-11-07 TOC SWFUpload SWFUpload 2 概述入门 SWFUpload JavaScript 对象构造器全局变量和常量 instances movieCount QUEUE_ERROR UPLOAD_ERROR FILE_STATUS Default Event Handlers BUTTON_ACTION(added in v2.2.0) BUTTON_CURSOR(added in v2.2.0) BUTTON_WINDOW_MODE(added in v2.2.0) 属性 customSettings movieName 方法 addSetting (不推荐使用) getSetting (不推荐使用) retrieveSetting (v2.1.0中已删除) destroy (v2.1.0中新增) displayDebugInfo selectFile (不推荐使用) selectFiles (不推荐使用) startUpload cancelUpload stopUpload getStats setStats getFile addPostParam removePostParam addFileParam removeFileParam setUploadURL setPostParams setFileTypes setFileSizeLimit setFileUploadLimit setFileQueueLimit setFilePostName setUseQueryString setDebugEnabled setButtonImageURL (added in v2.2.0) setButtonDimensions (added in v2.2.0) setButtonText (added in v2.2.0) setButtonTextStyle (added in v2.2.0) setButtonTextPadding (added in v2.2.0) […]

龙生 12 Sep 2012

View Details

swfupload在IE9中不显示上传按钮的问题

问题描述：使用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 […]

龙生 12 Sep 2012

View Details

Asp.net Web Applicatoin实现自定义HttpModule拦截异常处理

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> }

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> }

----------------------------------------Timestamp: 2011-11-12 5:57:08Message: HandlingInstanceID: a99d005d-5f8d-4613-9522-2d60efb089aaAn exception of type 'System.ArgumentNullException' 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 null.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) in 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文件,内容如下:

----------------------------------------Exception Warning: 9000 : Timestamp: 2011-11-12 5:57:08Message: HandlingInstanceID: a99d005d-5f8d-4613-9522-2d60efb089aaAn exception of type 'System.ArgumentNullException' 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 null.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) in 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

龙生 13 Jul 2012

View Details

asp.net向文本文件txt末尾追加内容

using 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

龙生 13 Jul 2012

View Details

ASP.NET Global.ascx 事件大全

Global.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

龙生 13 Jul 2012

View Details

« Previous 1 … 40 41 42 … 44 Next »