CodeSmith Samples

UPDATED WIKI: Home

ericjsmith — Wed, 14 May 2008 15:48:11 GMT

Project Moved

For various reasons, we have decided to move this project to Google Code. Please do not post issues or patches here, post them on the google code project. Here is the new project site:

http://codesmith.googlecode.com/

Project Description
This project contains all of the CodeSmith sample templates and projects. We have created this project so that the CodeSmith community can always have access to the latest updates as well as contribute patches and samples.

CodeSmith Tools Website
http://www.codesmithtools.com/

PLINQO

PLINQO, which stands for Professional LINQ to Objects, is a collection of CodeSmith templates that are meant to replace and extend the LINQ to SQL designers that are included with Visual Studio 2008.

Features

Generate or update a LINQ to SQL dbml file from a database schema.

Includes all tables, stored procedures, functions, and views with the ability to exclude objects based on regex patterns.
Ability to automatically remove object prefix and suffixes (ie. tbl_ and usp_).
Dbml file can still be customized with the normal Visual Studio 2008 designer.
Dbml file can be refreshed based on the current database schema without losing customizations. (See Safe Attributes)

Generation of the LINQ to SQL DataContext class.
Generation of the LINQ to SQL entity classes.

Generates one file per entity instead of one massive file.
Generates partial classes where custom code can be written and won't be overwritten.
Generated entity files are added to the project as code behind files to their corresponding custom entity files.

Generation of entity manager classes.

Adds customizable business rules engine to enforce entity validation, business and security rules.
Provides access to common queries based on primary keys, foreign keys, and indexes.
Common queries are exposed as IQueryable so they can be extended.

All templates can be customized to meet your needs.

http://community.codesmithtools.com/blogs/pwelter/archive/2007/08/08/plinqo.aspx

Source code checked in

pwelter34 — Wed, 14 May 2008 15:47:54 GMT

Project Moved http://codesmith.googlecode.com/

UPDATED WIKI: Home

ericjsmith — Wed, 14 May 2008 15:47:10 GMT

Project Moved

For various reasons, we have decided to move this project to Google Code. Here is the new project site:

http://codesmith.googlecode.com/

PLINQO

Generate or update a LINQ to SQL dbml file from a database schema.

Includes all tables, stored procedures, functions, and views with the ability to exclude objects based on regex patterns.
Ability to automatically remove object prefix and suffixes (ie. tbl_ and usp_).
Dbml file can still be customized with the normal Visual Studio 2008 designer.
Dbml file can be refreshed based on the current database schema without losing customizations. (See Safe Attributes)

Generation of the LINQ to SQL DataContext class.
Generation of the LINQ to SQL entity classes.

Generates one file per entity instead of one massive file.
Generates partial classes where custom code can be written and won't be overwritten.
Generated entity files are added to the project as code behind files to their corresponding custom entity files.

Generation of entity manager classes.

Adds customizable business rules engine to enforce entity validation, business and security rules.
Provides access to common queries based on primary keys, foreign keys, and indexes.
Common queries are exposed as IQueryable so they can be extended.

All templates can be customized to meet your needs.

http://community.codesmithtools.com/blogs/pwelter/archive/2007/08/08/plinqo.aspx

UPDATED WIKI: Home

ericjsmith — Wed, 14 May 2008 15:44:56 GMT

Project Moved

For various reasons, we have decided to move this project to Google Code. Here is the new project site:

http://codesmith.googlecode.com/

PLINQO

Generate or update a LINQ to SQL dbml file from a database schema.

Includes all tables, stored procedures, functions, and views with the ability to exclude objects based on regex patterns.
Ability to automatically remove object prefix and suffixes (ie. tbl_ and usp_).
Dbml file can still be customized with the normal Visual Studio 2008 designer.
Dbml file can be refreshed based on the current database schema without losing customizations. (See Safe Attributes)

Generation of the LINQ to SQL DataContext class.
Generation of the LINQ to SQL entity classes.

Generates one file per entity instead of one massive file.
Generates partial classes where custom code can be written and won't be overwritten.
Generated entity files are added to the project as code behind files to their corresponding custom entity files.

Generation of entity manager classes.

Adds customizable business rules engine to enforce entity validation, business and security rules.
Provides access to common queries based on primary keys, foreign keys, and indexes.
Common queries are exposed as IQueryable so they can be extended.

All templates can be customized to meet your needs.

http://community.codesmithtools.com/blogs/pwelter/archive/2007/08/08/plinqo.aspx

Patch Applied

ericjsmith — Wed, 14 May 2008 14:49:40 GMT

ericjsmith has applied patch #346.

Comment:
Fix applied.

Patch Applied

ericjsmith — Wed, 14 May 2008 14:49:24 GMT

ericjsmith has applied patch #693.

Comment:
Fix applied

Patch Applied

ericjsmith — Wed, 14 May 2008 14:49:13 GMT

ericjsmith has applied patch #694.

Comment:
Fix applied

Patch Applied

ericjsmith — Wed, 14 May 2008 14:48:58 GMT

ericjsmith has applied patch #1123.

Comment:
Fix applied

UPDATED WIKI: Home

ericjsmith — Wed, 14 May 2008 05:00:34 GMT

Project Moved

For various reasons, we have decided to move this project to Google Code. Here is the new project site:
http://codesmith.googlecode.com/

Project Description
This project contains all of the CodeSmith sample templates and projects. We have created this project so that the CodeSmith community can always have access to the latest updates as well as contribute patches and samples.

CodeSmith Tools Website
http://www.codesmithtools.com/

PLINQO

Generate or update a LINQ to SQL dbml file from a database schema.

Includes all tables, stored procedures, functions, and views with the ability to exclude objects based on regex patterns.
Ability to automatically remove object prefix and suffixes (ie. tbl_ and usp_).
Dbml file can still be customized with the normal Visual Studio 2008 designer.
Dbml file can be refreshed based on the current database schema without losing customizations. (See Safe Attributes)

Generation of the LINQ to SQL DataContext class.
Generation of the LINQ to SQL entity classes.

Generates one file per entity instead of one massive file.
Generates partial classes where custom code can be written and won't be overwritten.
Generated entity files are added to the project as code behind files to their corresponding custom entity files.

Generation of entity manager classes.

Adds customizable business rules engine to enforce entity validation, business and security rules.
Provides access to common queries based on primary keys, foreign keys, and indexes.
Common queries are exposed as IQueryable so they can be extended.

All templates can be customized to meet your needs.

http://community.codesmithtools.com/blogs/pwelter/archive/2007/08/08/plinqo.aspx

CREATED ISSUE: Misc XML Comment Errors in Rules Class Constructors

odelljl — Thu, 01 May 2008 14:48:21 GMT

The following classes have XML comment errors in theor constructors:

IpAddressRule: <see cref="DefaultUseNamerRule"/> should be <see cref="IpAddressRule"/> (twice)

NowRule: <see cref="DefaultNowRule"/> should be <see cref="NowRule"/> (twice)

UseNamerRule: <see cref="DefaultUseNamerRule"/> should be <see cref="DefaultUseNamerRule"/> (twice)

CREATED ISSUE: RegexRule class in wrong namespace

odelljl — Thu, 01 May 2008 14:08:24 GMT

RegexRule is in the CodeSmith.Data.Rules namespace. It looks like to be consistent with the other Validation rules it should be in the CodeSmith.Data.Rules.Validation namespace.

This issue was identified in the version of LINQ to SQL Support delivered with CodeSmith 4.1.4.

CREATED ISSUE: DBML Error Switching to Designer

nratcliff — Wed, 30 Apr 2008 02:22:33 GMT

The templates are generating the DBML file specifying a utf-16 encoding. I'm not sure why the 3.5 betas used utf-16, but they've changed it to utf-8 in the RTM.

I've tried to figure out how to fix this in the template, but I'm not having much luck.

Source code checked in

ericjsmith — Thu, 24 Apr 2008 01:57:57 GMT

Removed file/folder

CREATED ISSUE: Default Value Generation for a Date/SQLMetal Consistency

odelljl — Tue, 22 Apr 2008 14:28:17 GMT

When there database defines a default value for a date:

[CreatedOnDate] [datetime] NOT NULL DEFAULT (getdate()),
J
SQLMetal will generate:

private System.Nullable<System.DateTime> _LastUpdatedOnDate = default(System.Nullable<System.DateTime>);

PLINQO is generating:

private System.DateTime _createdOnDate;

Should the default get picked up to be consistent with SQLMetal?

COMMENTED ISSUE: DBML Designer errors after generation with VS2008

MarcelGosselin — Fri, 18 Apr 2008 04:32:40 GMT

I get errors throughout my dbml designer.cs file after generation. The errors state that functions have already been used/declared in the generated entity classes.
Comments: ** Comment from web user: MarcelGosselin **

I just uploaded a patch fixing the issue with the byte order mark. (Patch with ID 1123)

Patch Uploaded

MarcelGosselin — Fri, 18 Apr 2008 04:31:19 GMT

MarcelGosselin has uploaded a patch.

Description:
This patch fixes the issue with the generated DBML file that could not be opened in VisualStudio because of byte-order mark and UTF-16
Cannot load '...\Petshop.dbml': Error encountered, check Error List window for details.
There is no Unicode byte order mark. Cannot switch to Unicode.

Only replace the function Save(Database db, string fileName) in Template\LinqToSql\Internal\Schema.cs by the one attached. There are 2 main changes:
1- now uses MemoryStream/XmlWriter rather than StringBuilder/StringWriter because the XmlWriterSettings.Encoding property was not used at all with previous combination.
2- the encoding set on the XmlWriterSettings is now different so it does not try to set a UTF8 BOM.

Source code checked in

ericjsmith — Fri, 18 Apr 2008 02:57:16 GMT

Source code checked in

ericjsmith — Fri, 18 Apr 2008 02:57:01 GMT

Source code checked in

ericjsmith — Fri, 18 Apr 2008 02:56:03 GMT

NEW POST: Unicode Byte Order

wdevine — Thu, 17 Apr 2008 20:27:25 GMT

Hello Larry,

I think you're running into the issue where the .dbml file that is generated has utf-16 as its encoding instead of utf-8. If you open your .dbml with the xml editor instead of the default of the designer (Or using something like notepad) and change the utf-16 to utf-8 I think you should be able then open it in the designer.

Hope that helps,

Bill