entlib Forum Rss Feed

New Post: DatabaseFactory.CreateDatabase problem in DAAB 6.0

firedancer — Tue, 21 May 2013 06:38:24 GMT

Hi Randy! :)

I have included the following line in a static constructor in my class:

DatabaseFactory.SetDatabaseProviderFactory(new DatabaseProviderFactory());

... and everything works fine as usual.

Thank You :)

Hugs,
Serena

New Post: Entlib6 DAAB - Using accessors to execute stored procedures with optional parameters?

randylevy — Mon, 20 May 2013 15:41:09 GMT

BBauer42 wrote:

Prior to your code sample you say I can "use parameter names and not set the optional parameters". Do you have an example of this? Is it possible or am I misinterpreting your response?

I was just listing the ways in general on how to invoke stored procedures with optional parameters. My example shows how to to this following the pattern used by accessors.

Of course, there are many ways to get where you want to go. Another way would be to use the Enterprise Library mappers directly:

    DatabaseFactory.SetDatabaseProviderFactory(new DatabaseProviderFactory());

    Database db = DatabaseFactory.CreateDatabase();

    using (DbCommand cmd = db.DbProviderFactory.CreateCommand())
    {
        cmd.CommandText = "REPAIRTICKET_Select";
        cmd.CommandType = CommandType.StoredProcedure;

        if (repairTicket != null)
        {
            db.AddInParameter(cmd, "@RepairTicket", DbType.String, repairTicket);
        }

        IRowMapper<REPAIRTICKET> mapper = MapBuilder<REPAIRTICKET>.BuildAllProperties();

        using (var reader = db.ExecuteReader(cmd))
        {
            while (reader.Read())
            {
                yield return mapper.MapRow(reader);
            }
        }
    }

I would prefer to use ExecuteReader instead of ExecuteDataSet if you don't actually need a DataSet.

~~
Randy Levy
entlib.support@live.com
Enterprise Library support engineer
Support How-to

New Post: Distributed Caching using Enterprise Library Caching Application Block W.O. using database

randylevy — Mon, 20 May 2013 15:00:29 GMT

The Caching Application Block has been retired in Enterprise Library 6. Going forward the recommendation for caching in new applications would be, depending on the requirements, to use the .NET 4+ System.Runtime.Caching or Windows Server AppFabric Caching.

~~
Randy Levy
entlib.support@live.com
Enterprise Library support engineer
Support How-to

New Post: Entlib6 DAAB - Using accessors to execute stored procedures with optional parameters?

BBauer42 — Mon, 20 May 2013 12:12:44 GMT

Prior to your code sample you say I can "use parameter names and not set the optional parameters". Do you have an example of this? Is it possible or am I misinterpreting your response?

Also, it seems easier for me to just use something like ExecuteDataSet() and get the DataTable that was returned, then use AutoMapper to translate the table into a collection of objects. This is what I have in place now and is preferable to using the accessors thus far. Thanks.

New Post: Distributed Caching using Enterprise Library Caching Application Block W.O. using database

murad_sun — Mon, 20 May 2013 09:58:21 GMT

Hi, and thanks for the post.

But what about EF6, Is there any updates for AppFabric Cache Manager for EL6 ?

Thanks

New Post: MSEntlib6 finally out...

PiotrLuczak — Sun, 19 May 2013 23:32:13 GMT

I've been waiting very long time to see that, and here it is, a completely updated version, designed to integrate with the latest .NET features, much improving on features that already existed, and providing even more robust functionality for use with Windows Azure, WPF, WCF, and ASP.NET. There are very few other frameworks so mature and well designed.

It'll take me some time to get up to speed with the new features, but as with previous versions, that time is well worth it. After a quick evaluation I'm gonna introduce it to my team for use with next major releases of our products.

Thanks, Patterns and Practices team!

Best Regards,
Piotr

New Post: Can a 3rd party library effectively use EntLib?

r_keith_hill — Sun, 19 May 2013 01:14:57 GMT

Thanks for the pointers!

New Post: Class LoggingExceptionHandler not present in version 5.0.505 ?

randylevy — Sat, 18 May 2013 23:44:05 GMT

What version of Enterprise Library were you upgrading from? Are you seeing a runtime error executing the application?

The LoggingExceptionHandler (or LoggingExceptionHandlerData for configuration) is contained in the assembly Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging so that assembly needs to be deployed.

~~
Randy Levy
entlib.support@live.com
Enterprise Library support engineer
Support How-to

New Post: Can a 3rd party library effectively use EntLib?

randylevy — Sat, 18 May 2013 15:47:49 GMT

The answer is that a 3rd party library can definitely use Enterprise Library.

You are right -- the most complicated scenarios would be if the consuming application was also using Enterprise Library. This isn't really specific to Enterprise Library but for all There are a variety of approaches that you could take to mitigate this issues such as installing in the GAC (multiple versions can live side by side in the GAC), specifying the codebase, or a custom assembly resolver.

Of course, this all adds complication if you want to support all potential scenarios (sometimes it's hard to know how people will use your library!).

If your library is exposing the logging functionality externally (and not just using it internally for errors or tracing) then you should consider how that is done since you are imposing requirements (and dependencies) on your users. You may consider letting users to bring their own logger but that implies knowing how to use all supported loggers (plus there could be other potential issues -- what if a user disposes of the logger you are using?).

There is a project, Common.Logging, which provides a common interface (as well as adapters) that supports Enterprise Library, log4net, and NLog. That might help you since it sounds very similar to what you mention.

~~
Randy Levy
entlib.support@live.com
Enterprise Library support engineer
Support How-to

New Post: Can a 3rd party library effectively use EntLib?

r_keith_hill — Sat, 18 May 2013 05:56:54 GMT

It seems that the appropriate place to use EntLib is at the application level. However if you're a 3rd party library ISV and would like to enable your library to do logging, is it possible to still use the EntLib Logging App Block? Ironically, it is probably more of a problem if the consuming application also uses EntLib since the EntLib versions could be incompatible.

I think one solution would be to define an ILogging interface in the library and then log to it instead of a specific logging framework. The library would provide the user a way to plugin an adapter object that implements the interface (and that internally probably delegates to their choice of logging framework). Is there something in EntLib that facilitates this scenario?

New Post: Class LoggingExceptionHandler not present in version 5.0.505 ?

DennesTorres — Fri, 17 May 2013 21:57:43 GMT

Hi,

When I changed de version of entlib in my application to 5.0.505 the following block in web.config started to complain that LoggingExceptionHandler doesn't exists.

How this class changed between entlib versions ? What should I use to replace this class in the following block ?

<exceptionHandling>

<exceptionPolicies>
  <add name="GlobalExceptionLogger">
    <exceptionTypes>
      <add type="System.Exception, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" postHandlingAction="None" name="Exception">
        <exceptionHandlers>
          <add logCategory="General" eventId="100" severity="Error" title="Enterprise Library Exception Handling" formatterType="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.TextExceptionFormatter, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.505.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" priority="0" type="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.LoggingExceptionHandler, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging, Version=5.0.505.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" name="Logging Handler"/>
        </exceptionHandlers>
      </add>
    </exceptionTypes>
  </add>
</exceptionPolicies>

</exceptionHandling>

Thank you !

New Post: Retry logic for windows azure

randylevy — Fri, 17 May 2013 07:59:10 GMT

There are many resources A good place to start is the Developer's Guide -- Transient Fault Handling. There is also a video that has a demo.

Also, look at the Hands-On Labs for Enterprise Library 5.0 Integration Pack for Windows Azure which has some labs with the Transient Fault Handling Application Block.

~~
Randy Levy
entlib.support@live.com
Enterprise Library support engineer
Support How-to

New Post: Hierarchical category support in Logging Application Block?

randylevy — Fri, 17 May 2013 07:47:36 GMT

This feature was not implemented as part of Enterprise Library 6. You can see the suggestions at UserVoice.

~~
Randy Levy
entlib.support@live.com
Enterprise Library support engineer
Support How-to

New Post: Hierarchical category support in Logging Application Block?

karldodd — Fri, 17 May 2013 07:31:39 GMT

Hello,

It seems that logging application block does not support hierarchical category or category wildcard (e.g. category = "CompanyA.Common.*"). Many people regard this as a major short coming of entlib logging comparing to log4net & NLog.

Is it still true for entlib 6?

Thanks,
Karl

New Post: Entlib6 DAAB - Using accessors to execute stored procedures with optional parameters?

randylevy — Fri, 17 May 2013 07:05:03 GMT

The issue is that the accessors use an object array which is positional but if you are dealing with optional stored procedure parameters you need to supply all values with optional parameters being set to null or use parameter names and not set the optional parameters.

Here is one way to get what you want -- there may be others. In this approach the stored procedure parameters are discovered, then a custom IParameterMapper is used to indicate what parameter values will be set (in the correct order) and then a Custom SprocAccessor is created to handle the command object used for discovery.

    DatabaseFactory.SetDatabaseProviderFactory(new DatabaseProviderFactory());

    var db = DatabaseFactory.CreateDatabase();

    using (DbCommand cmd = db.GetStoredProcCommand("REPAIRTICKET_Select"))
    {
        db.DiscoverParameters(cmd);
        NamedParameterMapper parameterMapper = new NamedParameterMapper("@RepairTicket");
        var ticketData = new CustomSprocAccessor<REPAIRTICKET>(db, cmd, parameterMapper).Execute(repairTicket);
    }

    public class NamedParameterMapper : IParameterMapper
    {
        private string[] parametersToUse;

        public NamedParameterMapper(params string[] parametersToUse)
        {
            this.parametersToUse = parametersToUse;
        }

        public void AssignParameters(DbCommand command, object[] parameterValues)
        {
            int parameterValueIndex = 0;

            for (int i = 0; i < command.Parameters.Count; i++)
            {
                if (parametersToUse.Contains(command.Parameters[i].ParameterName, StringComparer.OrdinalIgnoreCase) &&
                    command.Parameters[i].Direction == System.Data.ParameterDirection.Input)
                {
                    command.Parameters[i].Value = parameterValues[parameterValueIndex++];
                }
            }
        }
    }

    public class CustomSprocAccessor<TResult> : SprocAccessor<TResult> where TResult : new()
    {
        private DbCommand command;
        IParameterMapper parameterMapper;

        public CustomSprocAccessor(Database db, DbCommand command, IParameterMapper parameterMapper) 
            : base (db, command.CommandText, parameterMapper, MapBuilder<TResult>.BuildAllProperties())
        {
            this.command = command;
            this.parameterMapper = parameterMapper;
        }

        public override IEnumerable<TResult> Execute(params object[] parameterValues)
        {
            parameterMapper.AssignParameters(command, parameterValues);
            return base.Execute(command);
        }
    }

You could probably add a bit more abstraction through extension methods (similar to how the block does).

~~
Randy Levy
entlib.support@live.com
Enterprise Library support engineer
Support How-to

New Post: Remote Service Trace Listener using SSL

lax4u — Thu, 16 May 2013 20:39:17 GMT

Thanks, thats is exactly what i was looking for

New Post: Enterprise Library 6 - Documentation and Samples

randylevy — Thu, 16 May 2013 14:53:19 GMT

The documentation along with supporting samples are targeted to be released this month.

See Just released - Microsoft Enterprise Library 6 for a discussion of the release.

~~
Randy Levy
entlib.support@live.com
Enterprise Library support engineer
Support How-to

New Post: Activation error occured while trying to get instance of type Database, key ""

randylevy — Thu, 16 May 2013 14:49:49 GMT

Everything looks fine. Are you sure that the app.config is deployed along with the .exe (e.g. as myapp.exe.config)? Otherwise, if you could supply a sample project it would help determine what the issue is.

~~
Randy Levy
entlib.support@live.com
Enterprise Library support engineer
Support How-to

New Post: Enterprise Library 6 - Documentation and Samples

BBauer42 — Thu, 16 May 2013 13:00:17 GMT

When are the new code samples and updated documentation going to be available? The "Developer's Guide to Microsoft Enterprise Library-Preview.pdf" is obviously not complete. Neither is the .chm.

I find it odd they could release the library without the updated documentation but I suppose that is a reflection of the current chaotic state of Microsoft.

Its also confusing that the homepage here and the MSDN say the April 13th release is an "Official Release" but the downloads link here shows it as a beta. Is this a beta release or a production release?

New Post: Entlib6 DAAB - Using accessors to execute stored procedures with optional parameters?

BBauer42 — Thu, 16 May 2013 12:36:54 GMT

I'm working with Enterprise Library 6 and using the Data Access Application Block. I am having trouble using accessors to execute stored procedures with optional parameters. For example, lets say I have a simple stored procedure to select a repair ticket by the ticket number, the group number, or both the ticket and group number.

CREATE PROCEDURE [Repair].[REPAIRTICKET_Select]
    @RepairTicket   nvarchar(6) = NULL,
    @GroupNumber    nvarchar(5) = NULL
AS
BEGIN
    
    SET NOCOUNT ON;

    SELECT * FROM [Repair].[REPAIRTICKET]
    WHERE (@RepairTicket IS NULL OR (RepairTicket = @RepairTicket))
      AND (@GroupNumber IS NULL OR (GroupNumber = @GroupNumber))
    OPTION (RECOMPILE)

END

This doesn't seem to play well with the .ExecuteSprocAccessor<T>() unless I'm missing something. When I try to retrieve a ticket from the SQL Database (by ONLY the RepairTicket NOT the Group) with the following I get a number of parameters mismatch error.

var ticketData = sqlDB.ExecuteSprocAccessor<REPAIRTICKET>("Repair.REPAIRTICKET_Select", repairTicket).ToList();

I have to actually pass the group in as null to get the accessor to work.

var ticketData = sqlDB.ExecuteSprocAccessor<REPAIRTICKET>("Repair.REPAIRTICKET_Select", repairTicket, null).ToList();

This is fine for this stored procedure. However, I have other update sprocs that have 20+ optional parameters. I don't want to have to explicitly pass null to the .ExecuteSprocAccessor's object[] parameters. Not to mention how error prone this would be. I would have to be looking at the sproc and making sure of the parameter order every time.

It would be much nicer if I could just pass the single parameter in my first example by name to the accessor and leave off any null parameters. Is this possible? Thanks in advance.