Archives

Archives / 2006 / February

  • VistaDB

    No Comments

    Yea, I'm a little slow...  But I just came accross a "need" for something just like this and found VistaDB.  Should fit the bill perfect.  Details:
     
    VistaDB 2.1 database for .NET has been released!
    This 2.1 update includes over 60 improvements, including new support for .NET 2.0 and Visual Studio 2005 VistaDB is a small-footprint, embedded SQL database alternative to Jet/Access, MSDE and SQL Server Express 2005 that enables developers to build .NET 1.1 and .NET 2.0 applications. Features SQL-92 support, small 500KB embedded footprint, free 2-User VistaDB Server for remote TCP/IP data access, royalty free distribution for both embedded and server, Copy 'n Go! deployment, managed ADO.NET Provider, data management and data migration tools. Free trial is available for download.
     
    Learn more about VistaDB
    Repost this to your blog and receive a FREE copy of VistaDB 2.1!

    Read more...

  • Compiler Warnings vs Code Analysis

    6 Comments

    public class Team
    {
          private IList<Athlete> athletes;
          ...
    }
    Compiler Warning: Field Team.athletes is never assigned to, and will always have its default value null.
    ( its assigned to in my mapper layer )
     
    public class Team
    {
          public Team()
          {
                athletes = null;
          }
          private IList<Athlete> athletes;
          ...
    }
    Code Analysis Warning: Team.Team() initializes field entries of type System.Collections.Generic.IList<Athlete> to null. Remove this initialization as it will be done automatically by the runtime.
     
    What am I doing wrong here?  Initializing athletes in the Team constructor to a new List<Athlete>() seems like a waste since its being set/initialized in my factory.
     
    Update: Kicks to Stuart for "setting" me right.
     

    Read more...