The Microsoft Enterprise Library is a set of tools and programming libraries for the Microsoft .NET Framework. It provides an API to facilitate best practices in core areas of programming including data access, security, logging, exception handling and others.
Enterprise Library is provided as pluggable binaries and source code, which can be freely used and customized by developers for their own purposes.
You can find many samples/tutorials on Enterprise Library in the following link.
Please remember to click “Mark as Answer” on the post that helps you and to unmark it if a marked post does not actually answer your question.
Thank you!
----------------------
"Microsoft Community Contributor Award 2011"
When you have to access database from your code. What do you typically do - Create ADO Connection, set connection string and then open connection. When you have to query, you have to follow another series of steps. Correct?
Now, EL provides a framework that cuts this task for you. You just have to use EL and it will open and do most of the stuff (mentioned above) that you do for database. All you have to focus on is the writing SQL queries and whatever is crux of the project.
Now this is just an example wherein you can utilize EL for database operations.
EL does much more than just that.
From MSDN:
The Microsoft Enterprise Library is a collection of reusable software components (application blocks) designed to assist software developers with common enterprise development cross-cutting concerns (such as logging, validation, data access, exception handling,
and many others).
So if you have to do look for logging in your application, you can use EL.
If you have to provide validation, data access or a standardized exception handling (provides many options like files, emails,event logs etc) then you can look at EL.
Can we use the same EL for multiple applications? If so, each database will have different connection string, tables, ado connection etc? Then how can we use the same EL in different applications (Concerning only database activities).
If we can implement Create ADO Connection, set connection string and then open connection in one particular Class and access through it then, how EL exactly works here.
Yes, you can. All you have to do is to download and install EL. Once that is done, just add a reference and you are all set.
rohitpundlik
If so, each database will have different connection string, tables, ado connection etc?
Yes, each database can have its own independent setting. This is done through configuration settings (web.config/app/config) which you can do manually or you can use EL configuration tool.
rohitpundlik
Then how can we use the same EL in different applications (Concerning only database activities).
Each application will have its own configuration file.
rohitpundlik
If we can implement Create ADO Connection, set connection string and then open connection in one particular Class and access through it then, how EL exactly works here.
You can write your own framework or leverage what EL already provides. It is a reusable component that has been written and tested by experts in Avanade and Microsoft. You can surely rely on this. If you really want to know what is beneath it, then you can
look at the source code too - its shipped with EL.
Last but not the least, EL is much more than just a database component. It provides a framework for validation, exception handling, logging etc.
I strongly recommend that you read the documentation to get familiar to it.
Is that means we will create .DLL file and use it through out multiple applications as and when required?
So as per my perception EL is basically used to cut down the basic and common activities to be written again and again. If i am wrong please correct me
Ok, understood that EL is already in DLL format and we need to add the reference through VS2008
But whatever the business logic we will write in the Data Access, exception handling, logging etc can i make a DLL file for it and use it through out the applications?
rohitpundlik
Contributor
3102 Points
934 Posts
Enterprise Library
Nov 22, 2010 05:07 PM|LINK
Hi All,
What is enterprise library and how to implement it?
Rohit Pundlik
Please mark as answer if this helps you...
santa_1975
Star
8574 Points
1499 Posts
Re: Enterprise Library
Nov 23, 2010 03:25 AM|LINK
Hi,
The Microsoft Enterprise Library is a set of tools and programming libraries for the Microsoft .NET Framework. It provides an API to facilitate best practices in core areas of programming including data access, security, logging, exception handling and others.
Enterprise Library is provided as pluggable binaries and source code, which can be freely used and customized by developers for their own purposes.
You can find many samples/tutorials on Enterprise Library in the following link.
http://www.pnpguidance.net/category/EnterpriseLibrary.aspx
Hope this helps.
Thank you!
----------------------
"Microsoft Community Contributor Award 2011"
rohitpundlik
Contributor
3102 Points
934 Posts
Re: Enterprise Library
Nov 23, 2010 03:25 PM|LINK
Hi All,
I didnt still understand what is enterprise library and why it should be used.
Can anyone explain any simple ways
Rohit Pundlik
Please mark as answer if this helps you...
sachingusain
Star
8786 Points
1702 Posts
Re: Enterprise Library
Nov 23, 2010 06:13 PM|LINK
When you have to access database from your code. What do you typically do - Create ADO Connection, set connection string and then open connection. When you have to query, you have to follow another series of steps. Correct?
Now, EL provides a framework that cuts this task for you. You just have to use EL and it will open and do most of the stuff (mentioned above) that you do for database. All you have to focus on is the writing SQL queries and whatever is crux of the project.
Now this is just an example wherein you can utilize EL for database operations.
EL does much more than just that.
From MSDN:
The Microsoft Enterprise Library is a collection of reusable software components (application blocks) designed to assist software developers with common enterprise development cross-cutting concerns (such as logging, validation, data access, exception handling, and many others).
So if you have to do look for logging in your application, you can use EL.
If you have to provide validation, data access or a standardized exception handling (provides many options like files, emails,event logs etc) then you can look at EL.
http://msdn.microsoft.com/en-us/library/ff648951.aspx
Thanks.
rohitpundlik
Contributor
3102 Points
934 Posts
Re: Enterprise Library
Nov 24, 2010 04:55 AM|LINK
Can we use the same EL for multiple applications? If so, each database will have different connection string, tables, ado connection etc? Then how can we use the same EL in different applications (Concerning only database activities).
If we can implement Create ADO Connection, set connection string and then open connection in one particular Class and access through it then, how EL exactly works here.
Rohit Pundlik
Please mark as answer if this helps you...
sachingusain
Star
8786 Points
1702 Posts
Re: Enterprise Library
Nov 24, 2010 11:07 AM|LINK
Yes, you can. All you have to do is to download and install EL. Once that is done, just add a reference and you are all set.
Yes, each database can have its own independent setting. This is done through configuration settings (web.config/app/config) which you can do manually or you can use EL configuration tool.
Each application will have its own configuration file.
You can write your own framework or leverage what EL already provides. It is a reusable component that has been written and tested by experts in Avanade and Microsoft. You can surely rely on this. If you really want to know what is beneath it, then you can look at the source code too - its shipped with EL.
Last but not the least, EL is much more than just a database component. It provides a framework for validation, exception handling, logging etc.
I strongly recommend that you read the documentation to get familiar to it.
Thanks.
rohitpundlik
Contributor
3102 Points
934 Posts
Re: Enterprise Library
Nov 25, 2010 05:28 AM|LINK
Is that means we will create .DLL file and use it through out multiple applications as and when required?
So as per my perception EL is basically used to cut down the basic and common activities to be written again and again. If i am wrong please correct me
Rohit Pundlik
Please mark as answer if this helps you...
sachingusain
Star
8786 Points
1702 Posts
Re: Enterprise Library
Nov 25, 2010 02:15 PM|LINK
EL is already compiled and shipped in DLL format. You just have to include it in reference and get on with it.
And, yes you are correct. It provides a uniform out of the box way of doing things.
Thanks.
rohitpundlik
Contributor
3102 Points
934 Posts
Re: Enterprise Library
Nov 26, 2010 05:50 AM|LINK
Ok, understood that EL is already in DLL format and we need to add the reference through VS2008
But whatever the business logic we will write in the Data Access, exception handling, logging etc can i make a DLL file for it and use it through out the applications?
Rohit Pundlik
Please mark as answer if this helps you...
kiran ghadge
Member
186 Points
71 Posts
Re: Enterprise Library
Nov 26, 2010 05:57 AM|LINK
Enterprise Library is library from Microsoft Corp.
In that library there are various block for user such as database connection,encryption,decryption.cryptography
we can modify those blocks as per our need. u can connect to any number of databases using EL.
is very useful n hady to use that library.
if you want that libraries visit
http://msdn.microsoft.com/en-us/library/ff632023.aspx
u will get all details from this link
Kiran Ghadge