Huagati DBML/EDMX Tools
Tools for Linq to SQL and ADO.NET Entity Framework in Visual Studio 2008/.net 3.5,
and Visual Studio 2010/.net 4.0
Huagati DBML/EDMX Tools is an add-in for Visual Studio that adds functionality to the Linq-to-SQL / DBML diagram designer, and to the ADO.NET Entity Framework designer in Visual Studio 2008 and 2010 (beta 2).
This add-in saves its users hours of precious development time by automating repetitive tasks: synchronize your Linq-to-SQL models with the underlying database and any database schema changes, mass-rename Linq-to-SQL and Entity Framework generated entity classes and their members to use .net naming conventions, generate documentation comments for L2S and EF entity classes from the database, generate SQL-DDL scripts from Linq-to-SQL and Entity Framework models, etc. See the detailed feature list below.
 Click here to download Huagati DBML/EDMX Tools for Visual Studio 2008 / .net 3.5 and for Visual Studio 2010β2 / .net 4.0β2.
Current version: 1.85 released on 13 January 2010
After downloading, click here to retrieve a free 20-day trial license key, or click on the "Download/Licensing" tab below to see all licensing options.
Features for Linq-to-SQL
Huagati DBML/EDMX Tools adds a new DBML/EDMX Tools menu to Visual Studio's menu bar
...and a toolbar providing quick and easy access to the add-in features
Update Linq-to-SQL diagram from database automatically updates Linq-to-SQL designer diagrams and generated classes with database changes:
- New Tables/Views -> creates new classes
- Dropped Tables/Views -> removes corresponding classes
- New Columns -> adds new properties
- Dropped Columns -> removes corresponding properties
- Columns with changed nullability -> updates member properties accordingly
- Columns with data type changes -> updates member properties accordingly
- New Foreign Keys -> adds associations and navigation properties
- Dropped Foreign Keys -> removes corresponding associations and navigation properties
- Changed Primary Keys -> updates member properties accordingly
- New stored procedures or user defined functions -> adds member methods to the datacontext class
- Dropped stored procedures or user defined functions -> removes member methods from the datacontext class
- Changed signature (parameters or return value/return type) from stored procedures and UDFs -> updates the signature accordingly in the datacontext
Exclusion lists for tables, columns, foreign keys, types/classes, members/properties and associations/navigation properties allows flexible rules for what to sync and what to not sync.
Customizable rules for auto-generated properties allow columns with default constraints such as NewID, NewSequentialID, GetDate, or custom default constraints to be treated as auto-generated.
Compare Linq-to-SQL diagram with database detects changes and differences between the Linq-to-SQL designer (DBML) and the database and outputs a list of the changes;
- New Tables
- Dropped Tables
- New Columns
- Dropped Columns
- Columns with changed nullability
- Columns with data type changes
- New Foreign Keys
- Dropped Foreign Keys
- Changed Primary Keys
- New stored procedures or user defined functions
- Dropped stored procedures or user defined functions
- Modified stored procedures or user defined functions
The Update/Compare options dialog gives the user control over what kinds of database changes to take into account in the update and compare functions, and customization of many of the update/compare rules.
Standardize Linq-to-SQL class and member names mass updates names of entities and members in Linq-to-SQL designer diagrams and generated classes:
- Remove/add prefixes/suffixes, e.g. remove leading tbl_, int_, str_
- Use TitleCaseNames for classes and properties if the database names are all lowercase
- Remove underscores_in_names
- Control pluralization / singularization
The renaming options dialog gives the user control over what naming rules to use when mass-updating class- and property names.
Generate DDL with model <-> db differences compares the Linq-to-SQL model with the underlying database and generates SQL DDL corresponding to any differences detected; new/dropped tables, new/dropped columns, primary key changes, new/dropped foreign keys/associations.
Update Linq-to-SQL documentation from database retrieves free-text table and column descriptions, and index definitions from the database and updates the xml documentation and description attributes for Linq-to-SQL generated entity classes and member properties with the same information for inline documentation in Visual Studio's code editor.
After using the documentation add-in on a Linq-to-SQL designer, the generated documentation is displayed in tooltips in the Visual Studio code editor.
Generate Required/Optional interfaces adds member properties to all entity classes, providing quick and easy access to required (non-nullable) vs optional (nullable) members.
After using the optional/required interface generation add-in feature on a Linq-to-SQL designer, all entity classes have new _opt/_req properties providing access to optional and required members respectively.
Diagram layout views is a dropdown on the DBML Tools toolbar that allow a Linq-to-SQL model to have more than one diagram layout. New layouts are added using the add view button (  ).
The DBML Diagram View dropdown makes it easy to switch layout views in the Linq-to-SQL designer.
SQL Server 2000, 2005 or 2008 (any edition) is required for the Linq-to-SQL features.
|