This post originated from an RSS feed registered with .NET Buzz
by Frans Bouma.
Original Post: LLBLGen v1.21 has been released! (Mostly bugfixes)
Feed Title: Frans Bouma's blog
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/fbouma/Rss.aspx
Feed Description: Generator.CreateCoolTool();
A new LLBLGen v1.x has been released today! Version 1.21.2003.712 to be exact, is a QFE (Quick Fix Engineering) release, which means only minor new features are added and for the rest just bugfixes. This is the final release, no more updates will be released after this release, since the next version of LLBLGen, LLBLGen Pro, is in development and will be released later this summer. The sourcecode comes in a project that is compatible with VS.NET 2003 but not with VS.NET 2002. You need a converter to load it into VS.NET 2002.
I've decided to release this update to reward the tens of thousands of users who downloaded LLBLGen v1.x in the past year and to tell them all that they've made LLBLGen one of the most used tier generators on the planet. Thank you!
Get the executable (including the documentation) [here].
Get the sourcecode (including the documentation) [here].
Get only the documentation [here].
Changelog: Version 1.21.2003.712
ADDED: New property in base class: 'RowsAffected' (Int32), which contains the amount of rows affected after an Insert Update or Delete action. Will contain -1 when a Select action was called OR when the T-SQL option 'Include NOCOUNT' is checked, which effectually switches off row counting and thus no report can be given about the amount of rows affected by an action.
ADDED: The generation of DeleteW<foreignkey>Logic routines. SqlServer 7 doesn't support cascading deletes so you'll need these routines. SqlServer 2000 does support cascading deletes and these are the preferred way to delete orphaned FK rows since it doesn't require a transaction on the .NET level, everything will run in the DELETE statement's transaction inside SqlServer.
ADDED: Because LLBLGen v1.x can only deal with 1 schema, only the schema 'dbo' is supported, which is normally the schema of the database owner. All objects not part of this schema are not listed and no code is generated for these objects. The filter is added to prevent null pointer exceptions when an object of another schema was selected. If you do not see an object in the tables/views list, you either are not making connection as a dbo or the object itself is not owned by the dbo. Normally all objects should be created by the dbo so in most cases you are not affected by this change/addition.
FIXED: Better folder browser. The new one now also lets you create directories. Still .NET 1.0 compatible.
FIXED: Minor GUI glitches.
FIXED: Slightly better exception viewer.
FIXED: When a database connection failed, all tabs except the connection tab were removed. This was a leftover from the old v1.1 code base. Now all tabs stay in the GUI.
FIXED: When 'Include ErrorCode' was not checked, the T-SQL generator would emit a dangling ',' at the end of the last input parameter in UpdateW<foreignkey>Logic stored procedures. This is now fixed.
FIXED: The Tables/Views listview now has clickable column headers which sort the column ascending. Also fixed is the initially sorting of the listview: now the listview is sorted on object type (table/view) and then on table/view name.
FIXED: Under SqlServer 7, the INFORMATION_SCHEMA.* views, which are part of a catalog (in SqlServer 2000 they're stored in the master catalog), were also listed. These are filtered out now, together with the sysalternates view which is also a system view.
FIXED: Under SqlServer 2000 sp3 the query used by LLBLGen to determine which fields are in which tables/views is utterly slow. A new query is added which is much faster; it now avoids slow hashtable constructions which were constructed by the query optimizer of SqlServer the old query used an INNER JOIN statement.
NOTES: This release contains some code borrowed from the upcoming LLBLGen Pro (some GUI classes). This code is written using the .NET guidelines as described by Microsoft in the .NET reference manual. Therefor it might be a little awkward to switch from the old LLBLGen v1.x code which is written using Hungarian Notation and the new code written in caMel/PasCal casing. The new code is located in the new folder browser and the new small form StringInput. All other new code is written in Hungarian Notation.
NOTES: The sourcecode is for VS.NET 2003. You need a converter for VS.NET 2002 to load the project in VS.NET 2002. Blame Microsoft for their hardcoded linkage between a texteditor and a compiler version.
NOTES: The documentation is updated, but only for the new features and a small section for VB.NET users.
NOTES: Changes made by others in the gotdotnet.com workspace of LLBLGen are not included in this release.
NOTES: No new updates will be made on this code base after this release. The next version will be LLBLGen Pro, the O/R mapper/code generator for .NET.
Previous Topic
