Archives

Archives / 2005 / October

  • WilsonORMapper v4.2 Released -- Includes Command Interception and Lookup Queries

    2 Comments

    Update: WilsonORMapper v4.2.0.0 (10/15/2005) includes the following:   

    • Added support for Intercepting Database Commands using IInterceptCommand,
    • which can be used for Logging (Log4Net or custom) or modifying actual Sql.
    • Added support for Outer Joins to populate Lookup values in single query.
    • Added Generic ObjectHolder<T> for strongly typed lazy-load many-to-ones.
    • Jeff Lanning added OPath Sorts on Many-to-One Relations and more Functions.
    • Added TotalCount Property to IObjectPage for ObjectSet, List, and Reader.
    • Output Parameters are now Supported on GetObjectSet/XXX and ExecuteScalar.
    • GetObject on ObjectSet/List now returns Null when the Key is not Contained.
    • Exceptions are fully Serializable, Default DateFormat is yyyy-MM-dd HH:mm:ss.
    • Bug Fix for some scenarios where Multiple Many-To-Many Deletes were Failing.
    • Bug Fix so InitialState.Updated will Work with Deletes and not just Updates.
    • Bug Fix so that the LocalStore works correctly for Multi-Threaded scenarios.
    • Thanks to Mark Kamoski (http://www.WebLogicArts.com) for ORHelper options
    • for mapping types, lazy-load false, date-time stamps, and escape keywords.
    This version is also synced up with the .NET v2.0 RC and later builds for nullable types (should hopefully work as is with RTM when it comes out), although you can add a V2BETA2 compilation constant to continue to work with Beta 2.  There are also some sample IInterceptorCommand implementations included in the downloads, to demonstrate how to add support for either Log4Net or a custom log file routine of your own.  I've also updated the example app to demonstrate the new outer join "lookup" feature (thanks to Steve Eichert for the encouragement and beta testing), and I've added versions for 2005 with generics and nullable types.

    Read more...

  • Web Deployment Projects to fix Lack of Web Project Files

    4 Comments

    I just saw a demo of a new feature that the MS ASP.NET team will be releasing as an add-on to VS 2005 -- it should be available at launch too.  Its called Web Deployment Projects and its basically allowing you to handle a lot of the scenarios we used to be able to do with web project files -- and more.  Under the cover its just a standard MSBuild file, so its already well documented and very extensible, but its also going to hook in the new aspnet_merge tool and provide a basic UI for common scenarios.  Things you'll be able to do include specifying whether or not you want one assembly per page, folder, or entire web project -- and you'll be able to specify several naming options for those assemblies too.  You'll also be able to have different build configuration options like you can today in VS 2003 -- but even better than today you'll be able to have the build process link or replace parts of your web.config file with configuration specific web.config pieces (like separate connection strings for debug, staging, and release).  You'll also be able to specify things like assembly signing and you'll be able to tell it the asp.net compiler to follow the IIS metabase paths so that sub-webs are effectively excluded.  It looks like its very much on track to give us everything we were missing from VS 2003, and more, as well as giving as an extensible solution for anything else we can dream up since this is just an MSBuild file like all the other project files.  And of course this will be completely optional, so all those that have liked the simplicity of not having a web project file will in no way be forced to use this new web deployment project.  Very cool stuff -- and I'm very glad that MS had listened to those of us that had issues with the lack of the web project.

    Read more...