Sarvjith: See Tom Hollander's (EntLib Program/Product Manager (?) Manager) blog post: http://weblogs.asp.net/tomholl/archive/2005/02/14/372512.aspx
It's in the works ... and labeled as vNext. HTH - Adwait -- Adwait Ullal e: mailto:[EMAIL PROTECTED] w: http://www.adwait.com j: http://finance.groups.yahoo.com/group/AdwaitsDotNetJobs b: http://dotnetjunkies.com/WebLog/adwait On Thu, 24 Feb 2005 13:06:51 +0100, Chakravarty, Sarvajith <[EMAIL PROTECTED]> wrote: > Enterprise Library works only with .Net framework 1.1 > Are they coming out with a version which works on .Net framework 2.0? > > This has become an issue for me as I am doing all my development on > whidbey! > > Regards, > Sarvajith > > -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] > Sent: Monday, 21 February 2005 4:43 PM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] Exception Handling > > True. > I will suggest you to use Exception Handling Application Block (now > bundled > in Microsoft Enterprise Library) available at > http://msdn.microsoft.com/library/en-us/dnpag2/html/ehab.asp . It will > provide you with option of either handling the exception and/or simply > re-throwing it. This application block is also integrated with logging > application block so you can take advantage of that as well. > > Hammad Rajjoub, > > Dot Net Professional and Technical Evangelist. > http://dotnetwizards.blogspot.com > mailto://[EMAIL PROTECTED] > hello://0300-9287485 > > Doing "IT" with .NET... > > -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Wilson > Sent: Monday, February 21, 2005 12:05 PM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] Exception Handling > > Alex > > The best way I found to implement this into an application framework is > to > write a error logging class in it's own assembly (middle tier) that logs > to > db, file system, or event log. The assembly should also include a method > to > format your error message for logging. > > Then in each UI layer, write you error handling code (as global error > catching differs from web to windows), and call your logging class from > there. > > Hope this helps. > > Regards > Doug Wilson > Applications Integration - IT Dept > > -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Alexandre > Rocco > Sent: 19 February 2005 05:09 PM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: [ADVANCED-DOTNET] Exception Handling > > I have a somewhat good understanding of exceptions on the .net framework > and > how they work and bubble up through applications. > > One doubt I came up these days was where should I put the exception > handling > code to log the errors/information in the application. I searched a bit > on > the net and found some info regarding this, but seems to me that this > rule > is directly connected to the architecture of the app. > > In my particular case, I have an application consisted of a DAL (data > access > layer) and a BLL (business logic layer) and then 3 different apps that > consumes this "API". From what I have learned reading some articles, I > should put exception handling code on the application that uses this > API. > But since I have 3 of them, I think it may be duplicated work. > > Another approach could be handle the exceptions on the API and then > rethrow > the exception up, so the client code can react accordingly. > > Any suggestions or thougts on that? Any pointers would be appreciated. > > Thanks, > Alexandre Rocco > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentor. http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > DISCLAIMER: > "The information contained in this message is confidential and may be > protected by legal privilege. It is intended only for > the person(s) named as addressee. The dissemination, > distribution,copying or disclosure of this message, or its contents is > strictly prohibited unless authorized by Meezan Bank Limited. If you > have received this message in error, please return it > to the sender at the above address". > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentorŪ http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > =================================== This list is hosted by DevelopMentorŪ http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
