RAD Studio Code Generation Toolkit 6.0This update works for Visual Studio 2017, 2015 and 2013. RAD Studio is my preferred data access method as it creates 100% stored procedure driven data tiers. |
RAD Studio Code Generation Toolkit version 6.0 is finally here. This project was started in 2006 as a project called Data Class Builder.Net; the first version used dynamic SQL to determine the update statements for Microsoft Access or SQL Server. In 2010 the name changed to RAD Studio Code Generation Toolkit, and the code switch to only SQL Server and all data access switched to stored procedures. Now the program comes with project templates to make it simple to create new data libraries for any SQL Server project. This is my preferred data access layer over Entity Framework, Linq To SQL and NHibernate and others like them. I know Microsoft recommends Entity Framework, but Microsoft also hides extensions by default because they think everyone is stupid. I do not like all the extra SQL Entity Framework executes to perform simple fetches. Version 6.0 addressed some outstanding bugs and the user interface was updated to be more modern. DataJuggler.Net is the main engine of RAD Studio as it reads the database schema for a SQL Server database and creates the classes, data access component and Gateway methods based upon the database schema. The Object Library project created uses partial classes, thus allowing you to add custom code to your objects that won't be lost if you regenerate your project using RAD Studio. The project Stored Procedure Generator creates the procedures that perform the full CRUD methods, and they are easy to modify to create your own. I have 2 other open source projects that were built using code from RAD Studio: 1. DB Compare w/Remote Compare https://dbcompare.codeplex.com DB Compare using the same class DataJuggler.Net to read the database schema from two SQL Server databases and report any schema differences. New to version 2.0 is the ability to export a databases schema to XML and also to be able to perform a comparison of the XML exported against a SQL Server database. This makes it easy to compare local dev databases against Dev, Test and Production SQL Server databases located on remote virtual machines. 2. XML Mirror - https://xmlmirror.codeplex.com XML Mirror uses reflection and makes it simple to create C# XML Writers and Parsers. XML Mirror uses the same CSharpClassWriter as used in RAD Studio to write out the Parsers and Writers needed to load and export objects. XML Mirror made the remote compare features of DB Compare possible. Read the RAD Studio User's Guide included with the download for more information. If you want to make the switch aoo 100% stored procedure driven data tiers, download RAD Studio and take control over your data access needs. In the 7 years I have been using RAD Studio in its current form, I have not found any data needs that I can't solve using stored procedures. With Entity Framework I have ran into limitations of what can be coded in a Lamba expression. I plan on building some updated tutorials and create some benchmark tests to cmopare RAD Studio version Entity Framework in the near future. Thanks, Corby Data Juggler Software
|