Till current design, LINQS helps users to translate .NET objects between different types.

In the recent released LINQS 0.0.7, we translate seeds to "object declarations", and then translate object declarations to "entity descriptions", and then translate entity descriptions to SQL Server database declarations or ASP.NET website definitions.

While doing these translate transactions, LINQS doesn't keep information about the translation source. So we couldn't know is a database declaration tranlated from a seed or just defined by user.

The feature will added to LINQS in the near future, then we can do more complex tasks.

References:

1. LINQS: Entity resolving solutions, open source, http://codeplex.com/LINQS.
2. LINQS 0.0.7: The recent LINQS release on May 5, 09, http://linqs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=27009.
3. "seed": In the legend of LINQS, we call application or database descriptions writen in programing language a "seed", seed declarations are friendly for programers and easy for maintenance.
4. Object declarations: .Net objects and types model mappings.
5. Entity descriptions: Entity model mappings, the central logic of LINQS when talk with database programs.