Re: Enterprise Library Application Blocks question...

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Craig,

Yes, the APIs have changed from the first incarnation to now, to be more
in line with the current best practices using .NET 2.0.

The functionality provided by the originals is still there, as a matter
of fact, you should still have it. The application blocks (then and now)
come with complete source code, so there is no reason why even if the old
blocks dont work with .NET 2.0 (which I don't think is the case, since there
were not that many breaking changes in the data API, from what I recall)
that you can't tweak the code so that they do.

My recommendation, however, would be to work with the new blocks if you
can.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx

"craig" <e@xxxxxxxx> wrote in message
news:Oce7J$6QGHA.196@xxxxxxxxxxxxxxxxxxxxxxx
I was just wondering if anyone else may have incorporated the original
Microsoft Exception Management Application Block (EMAB) or Data Access
Application Block (DAAB) into one of their applications when the blocks
were frist released several years ago?

In the process of trying to upgrage an application to CLR 2.0, I thought
it would make sense to also get the latest application blocks. The are
now called the Enterprise Library Application Blocks and it appears that
the latest is January 2006. However, when I examined them, I realized
that their public APIs appear to have changed dramatically relative to the
originals. This raises the question....what happened to the functionality
provided by the originals?? Has this been incorporated into the .Net
Framework? Is that functionality now considered obsolete, replaced with a
"pattern and practice" that is completely different?? I can't find any
documentation that speaks to this.

Does anyone have any insight?

Thanks!!



.

Relevant Pages

  • Re: Enterprise Library Application Blocks question...
    ... Yes, the APIs have changed from the first incarnation to now, to be ... The functionality provided by the originals is still there, ... Microsoft Exception Management Application Block (EMAB) or Data Access ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Polygon tessellation
    ... don't see a problem with "mixing" APIs. ... You're not running OGL, you're just ... using an auxiliary functionality that doesn't even require an OGL context. ...
    (microsoft.public.win32.programmer.directx.graphics)
  • Re: Can there be any doubt at this point that queries were a bad idea?
    ... quirks many years ago and it would be dead by now. ... delivery of high-level functionality, not smoothing over browser ... DOM 3 Events and other DOM specifications are controlled by the w3c. ... The authors of the w3c specifications will continue to produce the same quality APIs that we are all sorely familiar with, and as such, dom adapters will be necessary. ...
    (comp.lang.javascript)
  • Re: Geometric pens compiler error
    ... compiles and runs fine under VC6 in XP, but I get compiler errors in EVC4. ... error C2065: 'PS_GEOMETRIC': undeclared identifier ... Windows CE provides a subset of the Win32 APIs found on a desktop PC, ... Since the OS doesn't provide this support the MFC CPen class can't provide an object orientated wrapper around the functionality, and this is why the documentation you referenced explictly mentions the additional contructor overload isn't available on Windows CE. ...
    (microsoft.public.windowsce.embedded)
  • Re: Polygon tessellation
    ... I guess this is just par for the course -- everything in Direct3D is always ... don't see a problem with "mixing" APIs. ... just using an auxiliary functionality that doesn't even require an OGL ... you could look at the source code for the mesa glu to learn how to write ...
    (microsoft.public.win32.programmer.directx.graphics)