Sunday, April 30, 2006

Our EntitySpaces 1.3 release currently requires VB.NET folks to generate both C# and VB.NET classes. The 1.3 release works like this:

VB,NET Inheritance Tree
VB.NET Custom ==> C# Generated -> EntitySpaces.Core.dll

As of our 1.4 release VB.NET users will no longer have to generate and compile a C# class library.

New VB.NET Inheritance Tree
VB.NET Custom ==> VB.NET Generated -> EntitySpaces.Core.dll

We now have mirror image templates for C# and VB.NET. If you are a VB.NET programmer using EntitySpaces your life just got so much easier. We're still unit testing but everything looks great so far. This will also help DNN users as well.

posted on Saturday, April 29, 2006 11:30:55 PM (Eastern Standard Time, UTC-05:00)  #    Comments [1]
 Friday, April 21, 2006

The target date for EntitySpaces release 1.4 is scheduled for May 31st, 2006. We cannot guarantee the May 31st date but we've been pretty good at hitting our goals. The list below is what we are planning for the 1.4 release.

  • MySQL - A MySql EntitySpaces provider for 4.x and 5.x will be available. The provider will support MySQL stored procedures and views for MySQL 5.x.
  • Hierarchical support will be added. This will be done via lazy load and support many-to-one, one-to-many, and many-to-many relationships.
  • DotNetNuke
    • DNN stored procedure and table creation templates will be complete
    • A full DotNetNuke module using EntitySpaces will be provided along with all of the source code.
  • DataBinding support will be improved
  • A template will be provided that will generate ASPX pages using the GridView control

Of course, many other user suggested enhancements and bug fixes will make it into the 1.4 release. We have also purchased Demo Builder which is a great tool for making presentations. Scott will be making a series of presentations in fact on DotNetNuke and how to build modules using EntitySpaces that will come out before the 1.4 release.

Don't let that stop you from buying 1.3 today, with the price of oil going up like it is it may cost us more to ship it to you .... So buy in now while it's cheap (that's supposed to be humor)

posted on Friday, April 21, 2006 6:52:52 PM (Eastern Standard Time, UTC-05:00)  #    Comments [0]
 Monday, April 17, 2006

The EntitySpaces team has decided to give a free, one year, Professional version of the EntitySpaces architecture for .NET to the first three (accepted) DotNetNuke developers who build modules that use EntitySpaces. To be considered, you must send a proposal to support@entityspaces.net. Not all proposals will be accepted. We will be judging based on the following criteria:

  • Your proposal must describe how your DotNetNuke Module will use EntitySpaces to read and write to the database.
  • We must be able to host your module on our site, which means it will have to be a standard install.
  • The module must come with documentation that describes how you built it and you're experiences with EntitySpaces.

 

The contest ends May 31, 2006, so send in your proposal, and get in the running for your free version of EntitySpaces. Applicants will need to use the trial version to develop their module.

posted on Monday, April 17, 2006 10:29:52 AM (Eastern Standard Time, UTC-05:00)  #    Comments [0]

We just released EntitySpaces 1.3, with lots of new features, and fixes here are the complete release notes:

EntitySpaces - Release Notes for 1.3 

  • Fixed spaces in parameter names for SqlServer, Access, and Oracle.
  • Changes for text based Load(), ExecuteNonExec(), ExecuteReader(),  and ExecuteScalar() that handle both token {0} logic and named esParameter logic for SqlServer, Access, and Oracle.
  • Fixed Catalog|Schema naming in SqlServer and Oracle Enterprise  providers.
  • Fixed GUID (uniqueidentifier) handling in SQL Server, if the default is newid() they are marked as output parameters and automatically brought back in the object.
  • Added [Serialization] to the esStrings nested class in the esEntity generated classes so that Infragistics grids bind correctly.
  • Fixed error in the Dynamic SQL generation for Delete statements when composite primary keys were involved, this was fixed for Oracle, Sql Server and Access, it was using a comma where " AND " should have been.
  • The templates now inject the EntitySpaces version number into the header of the generated classes.
  • There is a new checkbox in the templates that allows you to ignore the schema and catalog in the metadata class and drive it entirely by the connection string. Checking this box is recommended if you are using SQL Server.
  • You can manually override the schema and provider in the connection string as follows:

this.MyEmployeesCollection = new EmployeesCollection();
this.MyEmployeesCollection.es.Connection.Catalog = "MyNorthwind";
this.MyEmployeesCollection.es.Connection.Schema = "User";

  • Added  some key attributes on some of the properties. 
    1. esEntity.StringFormat  -  [BrowsableAttribute( false )]
    2. esEntity.SpecialBinder -  [BrowsableAttribute( false )]
    3. esEntity.strFomat - [NonSerialized]

The Generated Entity & Collection Objects

    1. str -  [BrowsableAttribute( false )]
    2. Query -  [BrowsableAttribute( false )]
  • There are two new templates for DotNetNuke. We will be working hard in this area for the next release, any feedback on these templates by DNN folks is appreciated.



NUnit Test Suite

  • Table with 'dot' in name 
  • Columns with spaces in name 
  • Columns with underscores in name. 
  • Token {0} and named esParameter logic 
  • Inserts/updates for table with memo field. 
  • Guid Primary Keys


Documentation: 

  • Improved compiled help in esEntity and esEntityCollection areas. 
  • Tests Getting Started document.


Installation: 

New Installs:

  • Uninstall any Beta or Trial version before installing EntitySpaces.
  • Install the Binary first.
  • Source and Providers can be installed in any order after that. (They are separate downloads.)
  • You do not need to install 1.2 first.
  • The 1.3 downloads are full installs.

Upgrades:

  • Upgrading does not require uninstalling 1.2.
  • You should install 1.3 over the top of your 1.2 installation.
  • Install the Binary first.
  • Source and Providers can be installed in any order after that. (They are separate downloads.)
  • You will need to regenerate your "Generated" classes after you install.

 

If you are a DotNetNuke developer and you are looking for a kick ass O/R Mapping solution you should definately check it out. We have a free 45 day trial available to all registered users.

posted on Monday, April 17, 2006 10:19:57 AM (Eastern Standard Time, UTC-05:00)  #    Comments [0]