Enterprise Library External Resources
A couple of very cool MSDN Webcasts coming up next week on the Validation Application Block and Policy Injection Application Block.
Read More
The other day I talked about how much I like the idea of caching being thought of as a crosscutting concern and using the new CachingCallHandler in Enterprise Library 3.0 to neatly tuck away the caching behavior out of my class so that only business logic and rules are exposed.
Read More
I think the CachingCallHandler we are going to see in the final release of Enterprise Library 3.0 is a great use of Aspect-Oriented Programming. I love the idea of declaratively specifying caching using the [CachingCallHandler] Attribute.
Read More
I had a blast presenting at the Orlando Code Camp this weekend. One of my presentations, Enterprise Library 3.0 – New and Improved!, discussed several topics, but focused on the new Validation Application Block and Policy Injection Application Block.
Read More
The Policy Injection Application Block introduces AOP-like functionality into your winform and web applications by intercepting normal method calls and running handlers before and after method execution as defined by you through configuration. It does this by handing you a proxy class during factory creation that represents the class you asked for...
Read More
The Policy Injection Application Block ( PIAB ) is new in Enterprise Library 3.0 and may change the way you use Enterprise Library and think about development in general.
Read More
Environmental Overrides allow you to manage different Enterprise Library Configuration Settings for different configuration environments: Development, Test, Staging, Production, etc. So often you want to have a default configuration environment that acts a base for all environments but then adjust / override certain settings that may be particular to a certain environment.
Read More
Here is a quick tip to fix conversion errors when using the ASP.NET PropertyProxyValidator Web Control that comes with the Validation Application Block in Enterprise Library 3.0.
Read More
One of the really cool features in the Validation Application Block is the ASP.NET and Winform Integration so you don't have to specify redundant validation rules both at the UI and within the business layer. The Validation Application Block comes with web and winform controls that allow the UI to get its validation rules from the business layer, saving you the headache of duplicating validation rules in multiple places.
Read More
There may be cases where proper business object validation is complex and/or cannot be handled with the validators alone but you still want to use the Validation Application Block to provide consistent business object validation in your application. In cases like this, you can use Self Validation, which gives you full control of the validation and the same consistent use of the Validation Application Block.
Read More
Enterprise Library 3.0 DAAB has a new database class, called SqlCeDatabase, that provides direct support for SQL Server Compact Edition. You can check the existence of a table in the database and get a count of the number of records as follows...
Read More
In Enterprise Library 3.0, the DAAB now supports batch updates by providing an overload to the Database.UpdateDataSet method that allows you to specify a batch update size as a Nullable<int>.
Read More
In the past 3 Validation Application Block Tutorials for Enterprise Library 3.0 I decorated my classes with ValidatorAttributes to specify validation rules. In this tutorial I specify the validation rules in the app.config file.
Read More
Up until now we have been using the Validation Facade Class and ValidationFactory Class in the Validation Application Block to validate an instance of Subscriber against only one set of rules. However, it is often more realistic to want to validate your class using multiple sets of rules. Maybe with the subscriber class we have using to date, we have a set of rules that define a valid subscriber, but we also have another set of rules that determine whether the subscriber can be persisted to the database.
Read More
In Part I of the Validation Application Block that comes with Enterprise Library 3.0, I showed how to decorate your classes with ValidatorAttributes and use the Validation Facade Class to validate an instance of a class. In this tutorial, I show you how to use the ValidationFactory Class to achieve the same functionality.
Read More
An introduction to the Validation Application Block that comes with Enterprise Library 3.0. In this Enterprise Library 3.0 Tutorial I show how to decorate your classes with ValidatorAttributes, use the Validation Facade Class to validate an instance of a class, check for validity, and iterate a collection of ValidationResults to display any validation errors that occurred during validation.
Read More
I just created an example of using the Logging Application Block to log to a database.
Read More
I mentioned the DatabaseConfigurationView Class on the MSDN Message Boards today as a way to get various Enteprise Library DAAB Settings and ConnectionString information as a read-only view. It helps you read the Data Access Application Block Settings, Connection Strings, and Provider Mappings in your configuration file / source, but you can't modify it and save it back to configuration.
Read More
It is very easy to read the default connection string name used by the Enterprise Library Data Access Application Block. There are many ways to do it, but this is the simplest in my opinion if you use the application's web.config or app.config file to store your DAAB Settings.
Read More
A question that comes up often enough in the Enterprise Library Forums for me to write this tutorial is - “Can you use the Enterprise Library Data Access Application Block with Typed DataSets?” The answer is yes :)
Read More
Most developers don't realize that the Enterprise Library Data Access Application Block ( DAAB ) can connect to any database that has a .NET Data Provider. One of the common questions is - “Does Enterprise Library support Microsoft Access?“ The answer is yes! You can use OLEDB or ODBC to connect to the Microsoft Access Database using the Data Access Application Block.
Read More
The Enterprise Library 2.0 Cryptography Application Block can assist you with hashing and comparing hashed passwords. You can select from a number of hash providers in the .NET 2.0 Framework.
Read More
The Cryptography Application Block in Enterprise Library 2.0 provides both hashing and encryption services to your winform and web applications. It is a convenience wrapper for the hashing and encryption included in the .NET 2.0 Framework.
Read More
If you are a winform developer, smart client developer, or have an application that runs both as a smart client and web applications, I could see the benefit of the Caching Application Block.
Read More
The Logging Application Block in Enterprise Library 2.0 ( Download ) is probably as popular as the Data Access Application Block. The Logging Application Block allows one to monitor the health of one's winform and web applications by logging various tracing information to a datastore that can later be massaged and analyzed.
Read More
Programmatically use the Enterprise Library 2.0 Logging Application Block without a configuration file.
Read More
Let's use the Enterprise Library 2.0 Logging Application Block in an ASP.NET 2.0 Website using the most simplistic, yet very important case of logging unhandled exceptions. If you log nothing else in your ASP.NET websites, make sure you log unhandled exceptions so that you have some idea of the health of your application.
Read More
The Enterprise Library 2.0 Logging Application Block makes logging various application events in your winform and web applications a snap. Before we dig into implementation specifics of the Logging Application Block, we first need to understand the importance and role of TraceListeners.
Read More
The Enterprise Library 2.0 Data Access Application Block can help you with a lot of your data access plumbing in your .NET applications as well as provide a database agnostic solution for .NET applications that need to target multiple databases.
Read More
The Configuration Application Block in Enterprise Library 1.0 has been replaced with an IConfigurationSource interface and two concrete classes that implement the interface, SystemConfigurationSource and FileConfigurationSource. There is also a SqlConfigurationSource provided in one of the QuickStarts to show you how to build your own concrete implementation of IConfigurationSource, but it is not included in the core architecture.
Read More
Join the members of the Enterprise Library team to learn about the core architecture of the newest release of Enterprise Library, which is version 2.0. We discuss a range of topics that include configuration, dependency injection, instrumentation, and the provider model.
Read More