All geek questions in one place

Enterprise Library 5.0 Compatibility with Enterprise Library 4.1?

Is Enterprise Library 5.0 compatible with Enterprise Library 4.1? Can I just change the link and make it work?

+4
source share
2 answers

Final answer: possible .

It really depends on the script and how you used the blocks. In the best case, you can replace the assembly links, change the configuration, and work.

From Microsoft Enterprise 5.0 5.0 Change Log:

Major architectural changes in the Corporate Library to use dependency injection mechanism. [...] The corporate library no longer uses the static facades and static classes that were used in previous versions. However, these facades and classes are still included in the corporate library for backward compatibility with existing application code, and you can continue to use the previous approach to create a corporate library of objects.

Of course, things rarely work like that, so to help solve any problems and go through a migration approach, you should definitely read:

+4
source

In a nutshell, we tried to maintain backward compatibility of the API with the API as much as possible. And for most users, the upgrade path will be largely a change of links and re-creation.

The architectural refactoring mentioned above includes major changes in the internal guts. However, you should not be affected unless you have written custom blocks. BTW, an EntLib5.0 extension guide (including how to write custom blocks) will be available soon.

The two links above (change log and migration guide) will help you with your migration. So far, most of the people I spoke with have commented on a fairly simple and straightforward experience.

Please let me know what you had and if you had problems.

Respectfully,
Grigory Melnik
Corporate Library Manufacturer

+3
source

Source: https://habr.com/ru/post/1310569/

More articles:


All Articles