Quantcast
Channel: EntityFramework Reverse POCO Code First Generator
Viewing all 1642 articles
Browse latest View live
↧

Edited Issue: Stored procedure return column name tidy up could bring all Null value [107]

April 23, 2015, 3:37 am
$
0
0
EF.Reverse.POCO.Generator has a code snippet to tide up stored procedure's return column name, here is code:

proc.ReturnColumns = ds.Tables[0].Columns.Cast<DataColumn>().ToList();
// Tidy up
foreach (var col in proc.ReturnColumns)
{
col.ColumnName = Regex.Replace(col.ColumnName, @"[^A-Za-z0-9\s]*", "");
col.ColumnName = Inflector.ToTitleCase(col.ColumnName).Replace(" ", "");
}

This could bring an issues that C# code cannot get correct stored procedure query result when column name has underline(s), e.g. if column name is "student_score", after tidy up, in return model class, corresponding property name is "StudentScore", in the list of query result, this property StudentScore is always NULL.
↧
Search

Updated Wiki: What's new

April 23, 2015, 4:53 am
$
0
0

Whats comming in the next release:

  1. Remove use of [GeneratedCodeAttribute] where not necessary.
  2. Case 108. Include the schema when calling stored procedures. Thanks to emdadgar2.

Whats new in v2.12.1:

  1. Case 101. SQL Server compact connection string only looks in current project. It now looks in all project paths for the SDF file, in a similar way to finding the app.config file for the connection string.
  2. Much faster TableSQL. Query plan cost is 97% vs 3%. Thanks to Glenn Orr.
  3. Much faster ForeignKeySQL. Query plan cost is 71% vs 29%.
  4. Unique indexes are now checked for. Previously, for tables without primary keys, all the NOT NULL columns used to be marked as a primary key. Now, if the table has a unique index, these unique index columns are used instead. However, the columns are still checked for being NOT NULL as entity framework will not allow a primary key to be made up of a column which can be NULLable.
  5. MakeClassesPartial flag now adds partial keyword to the stored procedure model classes.
  6. Added AdditionalContextInterfaceItems array to allow adding of extra functions to the db context interface.
  7. Fix schema prepending for Stored Procedures. Thanks to Emanov.
  8. Fix bug in MigrationStrategy when set to CreateDatabaseIfNotExists or DropCreateDatabaseIfModelChanges. Thanks toWill.
  9. Case 102. Stored procedures with no input parameters and all columns are nullable views cannot get populated in .cs. Thanks todisanxian.
  10. Calls to stored procedures are now placed in [square brackets] in case there are spaces in its name.
  11. Case 103. Check for column name C# reserved word name clashes. Thanks to swago.
  12. Do not include foreign keys which use composite keys.

Whats new in v2.11.0:

  1. Case 61. Allow excluding/modifying columns. Also permits you to run a function against each column to optionally modify the column properties (eg. to tweak the name of the generated property etc). Thanks toDavid Gardiner.
  2. Case 99. Add ability to specify additional using namespaces. Thanks to rorourke.
  3. Case 100. Apply GeneratedCodeAttribute to generated code. Thanks to David Gardiner.

Whats new in v2.10.2:

  1. Case 93. Merge logic for foreignKey column matching, previously .col=null was possible. Thanks toAHewgill.
  2. StoredProcs that return nullable binary types generate invalid "ReturnModel" code. Thanks toWallyHDisplayName.
  3. Case 96. Add a default for getutcdate(). Thanks to mbargar13.
  4. Case 94. Missing "using DatabaseGeneratedOption = System.ComponentModel.DataAnnotations.Schema.DatabaseGeneratedOption;" when targeting Framework 4.5. Thanks toalexdeblasis.
  5. StoredProcedureRename was being ignored. Thanks to slyCzar.
  6. Case 98. Corrected bridge table issue. Thanks to simooo985.

Whats new in v2.10.1:

  1. Stored Procedure arguments that are C# reserved keywords need escaping. Thanks toJimstr.
  2. Make mapping variables consistent during name clashes. An an edge case could cause different names for the reverse navigation as compared to the Map during name clashes. Thanks toFJRodriguez.
  3. Fix indentation when MakeClassesPartial is set.

Whats new in v2.10.0:

  1. Auto Migrations. To enable set MigrationConfigurationFileName to a class name, "MyDbContextDBMigrationConfiguration" for example. This enabled Entity Framework to update the schema when it is deployed in production. Thanks toFJRodriguez.
  2. Remove use of uses_native_compilation column in Stored Procedure SQL to support older database (< 2014). Thanks toNicholas Head.

Whats new in v2.9.1:

  1. GetSqlDbType was missing some types (nvarchar, and uniqueidentifier). Thanks toWally.
  2. Add in "using System.Linq" if Elements.StoredProcedures declared and not Elements.Context. Thanks toWally.

Whats new in v2.9.0:

  1. Stored procedure support !
    • This includes the ability to retrieve the RESULT from stored procs, as well as the data. A result of 0 means success, any other value is an error.
    • Include stubs for the stored procs in the FakeDbContext.
  2. Sort contents of HasForeignKey(...) by foreign key ordinal.
  3. Prevent creating maps where the left and right side of the map are the same table.
  4. Use a try/catch for WCF projects. Thanks to FJRodriguez.
  5. Include examples of CustomPluralizationEntry. Thanks to Carrie Kroutil.
  6. Allow for manual setting of the targeted .Net framework version.

Whats new in v2.8.3:

  1. Added new setting IncludeQueryTraceOn9481Flag so that you are now in control if "OPTION (QUERYTRACEON 9481)" is appended to the SQL. SqlServer 2014 is known to appear frozen / take a long time when this file is saved. If it does, set this to true (however you will also need elevated privileges).
  2. Added new setting DbContextBaseClass. You can now specify what the base class for your DbContext class is. For example ASP.NET Identity use "IdentityDbContext<ApplicationUser>", or even go so far as a custom: IdentityDbContext<CustomUser, CustomRole, int, CustomUserLogin, CustomUserRole, CustomUserClaim>. Thanks toParag Shravagi.
  3. Fixed bug: IndexOutOfRangeException thrown inside GetCurrentProject. Thanks toDavid Gardiner.
    https://efreversepoco.codeplex.com/workitem/85

Whats new in v2.8.2:

  1. This update is required to fix a problem with Sql Server 2014 as it freezes when obtaining the Foreign Keys. See here for more info. The solution was to add OPTION (QUERYTRACEON 9481). Thanks to@ErikEJ for the solution.
    Using this option flag needs a higher SQL privilege, so you may experience:
    User 'Your.Name' does not have permission to run DBCC TRACEON.
    More info (requires sysadmin rights) http://spaghettidba.com/2013/02/08/using-querytraceon-in-plan-guides/ 

Whats new in v2.8.1:

  1. Bug fix: If property had _ appended, and is used as key, it breaks template generation. Thanks toNicholas Head.

Whats new in v2.8.0:

  1. Added a new flag: AddUnitTestingDbContext. If true, this will create a Fake DbContext and a FakeDbSet<T>. This will allow easy unit testing. Can't believe I never added this sooner. See the documentation Unit Testing.

Whats new in v2.7.0:

  1. Fixed bug: Missing schema specification in ManyToMany tables. Thanks to Vtanman & Snajahi.
  2. Add a timeout when obtaining the schema info from a slow database. Thanks to DotNetWise.
  3. Changed table renaming to use a function. Thanks to DotNetWise.

Whats new in v2.6.3:

  1. Add IsUnicode(false) for the char/varchar columns. Thanks to Naomi N.
  2. Rollback a feature added in 2.5.1: For database types such as Numeric(17,0), the C# type should resolve to something in the "int" family. Thanks toSimmered.

Whats new in v2.6.2:

  1. Include another namespace if Target framework is not 4.0. Thanks to NazmulRockOn.
  2. CR/LF in extended properties caused errors. Thanks to Simmered.
  3. Use IsFixedLength() for char/nchar types. Thanks to Naomi N.

Whats new in v2.6.1:

  1. Added the same extended properties comments facility for SQL CE. Thanks to @ErikEJ

Whats new in v2.6.0:

  1. It now reads the extended properties and can add them to the poco classes in comments. See the new IncludeExtendedPropertyComments flag which is an enumeration of
[Flags]
public enum ExtendedPropertyCommentsStyle
{
  None,
  InSummaryBlock,
  AtEndOfField
};
  • ExtendedPropertyCommentsStyle.None: No extended properties are shown.
  • ExtendedPropertyCommentsStyle.InSummaryBlock: extended properties are shown above field in a ///<summary> block.
  • ExtendedPropertyCommentsStyle.AtEndOfField: extended properties are shown at the end of the field in a comment block.

The IncludeComments flag is completely independent to IncludeExtendedPropertyComments.

If you want completely comment free generate code, set IncludeComments = false, and IncludeExtendedPropertyComments = ExtendedPropertyCommentsStyle.None;

Whats new in v2.5.1:

  1. Move the call to tables.SetPrimaryKeys(); higher up. This allows support of tables with no primary keys to be able to be used. Thanks toJaved.
  2. For database types such as Numeric(17,0), the C# type should resolve to something in the "int" family. Thanks tosimmered.

Whats new in v2.5.0:

  1. Added option to strip and alter table names. Such as tblOrders to Orders, AB_Shipments to Shipments, etc. See Table renaming section.
  2. Added ability to switch off the Pluralization service.
  3. Added ability to use other Pluralization services, such as the SpanishPluralizationService as provided in the "EF6.Contrib" Nuget Package. If you are to use the SpanishPluralizationService, add the following to the top of your database.tt file: <#@ assembly name="C:\<Your path here>\packages\EF6.Contrib.1.0.5\lib\net45\EntityFramework.Contrib.dll" #> Changing the path to where your DLL is situated.

Whats new in v2.4.1:

  1.  Fixed bug: When using .HasForeignKey(...) for multi-column keys, the columns should be listed in ordinal order. Thanks toScott Hodges.

Whats new in v2.4.0

  1. Removed use of System.Data.Entity.DLL from the installation template as it is no longer required for EF 6.
  2. Moved spatial types from System.Data.Spatial to System.Data.Entity.Spatial for EF 6.
  3. Singular names and camel casing configuration were accidentally combined by using the UseCamelCase boolean. Thanks toRune Gulbrandsen.
  4. Added new flag IncludeComments. This controls the generation of comments in the output.
  5. Fixed bug in constructor where a UNIQUEIDENTIFIER column had default value. Thanks togonglei.

Whats new in v2.3.2

  1. Singularize one-to-one Reverse Navigation. Thanks to StormRider.
  2. Bugfix for IsRowVersion() for timestamp columns. Thanks to StormRider.
  3. Do not append "m" to decimal value in poco ctor if default contains an unparsable value.

Whats new in v2.3.0:

  1. SQL Server Compact 4.0 support. Thanks to ErikEJ.

Whats new in v2.2.1:

  1. Add strings to be allowed as computed columns. Thanks to JBJBJB and BrhineScot.
  2. Now includes callbacks during code generation. This means you can add attributes to classes, specify a base class, specify custom code within the class, and finally a call back for each column within the class. Thanks toSimplyFoolish. 
  3. OData doesn't support entities with geometery/geography types. Provided a flag to turn these off if entities are being generated from ODATA.  Thanks toSimplyFoolish. Flag is called DisableGeographyTypes.
  4. Fixed bug with the Pluralisation service. If your current culture was not en, then it would throw an exception. Thanks toErikEJ.

Whats new in v2.2.0:

  1. Now uses the .Net Pluralization service. Thanks to James Manning.
  2. Bug fixed when you have foreign keys between two tables where the FK/PK columns have spaces in the column name. Thanks toColin Smith.
  3. Bug fixed. Solution Folders are not searched for config settings. Thanks to scaftw.
  4. Generate navigation property based on FK name. If there are two FK links to a table, the second link would appear as linkName1. This is now detected and both the FK properties will make use of the FK name. If only one FK is used, then the FK name is not appended to the table name. Thanks to saber_solomon.
  5. Sort the generated Reverse navigation and foriegn keys in POCO classes.

Whats new in v2.1.0:

  1. Fixed bug if default constraint was not in expected format. Thanks to Filipe Fujiy.
  2. Now detects name clashes with C# keywords.
  3. Added "System." to DateTime.Now(), etc to prevent clashes with table field names.
  4. "Configuration" class names are now configurable as "Mapping", "Map", etc.
  5. Added support for Spatial.DbGeometry and Spatial.DbGeography. Thanks to Simply Foolish andJorge Bustos.
  6. Can now have custom collection type for Navigation Properties. "ObservableCollection" for example. Thanks to Simply Foolish.

Whats new in v2.0:

  1. Fixed issue when running 'Transform All T4 Templates' from Visual Studio Build Menu.Thanks to JRoselle.
  2. Changing mappings during runtime is not possible/expensive. A specific DbModelBuilder can be used for each needed database schema.Thanks to meixger.
  3. Added ability to detect and use .IsRowVersion().
  4. Added many-to-many mappings. The generated code now includes calls to .Map(). Therefore the generated code will be different to what you had previously in v1 if you have many-to-many table mappings in your database. Hence the revision change to v2.0.0 as I'm using semantic versioning.

Whats new in v1.12:

  1. VARBINARY(MAX) is now correctly assigned to byte[]. Thanks to Luke91577.
  2. Extending partial class support. Allow specification of file extension for partial classes (i.e. ".generated.cs").Thanks to AB_dreeve.
  3. Fixes issues when targeting .NET 4. .NET 4.0 doesn't include the System.ComponentModel.DataAnnotations.Schema namespace, allow specification of TargetFrameworkVersion.Thanks to AB_dreeve.

Whats new in v1.11:

  1. Including views is now working. For a view to be included, at least one column must not be nullable.Thanks to Delmo Carruzzo.
  2. Added selective generation of components (Poco, Context, UnitOfWork, PocoConfiguration). You can now build entities in your Model project, and context, configuration, unit of work in your Data project. Thanks to kscelfo.
  3. Added PrependSchemaName flag. You can now control if the schema name is prepended to the table name. Thanks to kscelfo.

Whats new in v1.10:

  1. Added UseCamelCase flag to the tt file. You can now control if you want your table and column names CamelCase or left alone: i.e. FieldPersonOrder or field_person_order

Whats new in v1.9.2:

  1. Removed the Linq de-duplication code as it is now being done in SQL. The Linq version did not include the schema name when de-duplicating FK's.

Whats new in v1.9.1:

  1. Added DISTICT to the foreign key SQL. This prevents duplicates from appearing.
    They can appear with SQL such as:
    ALTERTABLE [Mars].[Table2] WITHCHECKADDCONSTRAINT [FK_Table2_Table1]
    FOREIGNKEY([Table1Id]) REFERENCES [Mars].[Table1] ([Id])
ALTERTABLE [Mars].[Table2] CHECKCONSTRAINT [FK_Table2_Table1]

Whats new in v1.9.0:

  1. It now has the ability to read connection strings from other config files/projects.
    It starts by looking at the local project for the named connection string in the following files:
    • app.config
    • web.config
    • app.config.transform
    • web.config.transform
    • or edit the above list in the .tt and specify which file(s) to use
    If not found, it then looks for those files in all the projects within the solution.

Whats new in v1.8.0:

  1. Can now optionally generate separate files. See the new boolean flag GenerateSeparateFiles.
  2. Removed the hard coded 300 second timeout. The timeout can be specified in the connection string.

Whats new in v1.7.1:

  1. Add support for DateTime2
  2. Add support for UnitOfWork and the repository pattern. This means you can now unit test your repositories. See the source code for examples.
  3. Add IDisposable to db context.

Whats new in v1.7.0:

  1. Add .HasPrecision(precision, scale) for fields that have scale. Thanks to @choudeshell

Whats new in v1.6.0:

  1. Enhance ReadSchema performance with early table exclusion.
  2. Now supports columns with symbols and punctuation.
  3. Handles decimal default values.

Whats new in v1.5.1:

  1. A bugfix for WCF. See issue https://efreversepoco.codeplex.com/workitem/4

Whats new in v1.5.0:

  1. Ability to add WCF(DataMember, DataContract attributes) support on Entity. Requested by spatemp

Whats new in v1.4.1:

  1. Foreign keys are only included if they point to a primary key.

Whats new in v1.4.0:

  1. If a field has a default contrainst of GetDate(), add DateTime.Now() in the ctor for the field.
  2. Add support for the datetimeoffset type, including support for the default constraint sysdatetimeoffset().
  3. Add Resharper naming comments.
  4. Mappings should be marked internal. Requested by Hobbes Pirakitti
↧
↧

Created Unassigned: Nullable uniqueidentifier with default value generates exception [109]

April 23, 2015, 6:14 am
$
0
0
A table with a column having a nullable uniqueidentifier with a default value NULL:

[MyColumn] UNIQUEIDENTIFIER CONSTRAINT [DF_MyColumn] DEFAULT (NULL) NULL

will result in a Poco having the following line in the constructor:

MyColumn = Guid.Parse("NULL");

This will generate an exception.

The problem seems to be in the "CleanUpDefault" method (EF.Reverse.POCO.Core.ttinclude).

I was able to work around this thank to the new "UpdateColumn" function, but I think this should be fixed in the ttinclude.

Here's the workaround just in case:

UpdateColumn = (Column column, Table table) =>
{
if (column.PropertyType.ToLower() == "guid" && column.IsNullable && column.Default.ToLower().Contains("parse(\"null\")"))
{
column.Default = "null";
}
return column;
};
↧

Source code checked in, #563519c500da

April 24, 2015, 12:48 am
$
0
0
Remove stored procs where the return model type contains spaces and cannot be mapped
↧

Edited Issue: Nullable uniqueidentifier with default value generates exception [109]

April 24, 2015, 3:07 am
$
0
0
A table with a column having a nullable uniqueidentifier with a default value NULL:

[MyColumn] UNIQUEIDENTIFIER CONSTRAINT [DF_MyColumn] DEFAULT (NULL) NULL

will result in a Poco having the following line in the constructor:

MyColumn = Guid.Parse("NULL");

This will generate an exception.

The problem seems to be in the "CleanUpDefault" method (EF.Reverse.POCO.Core.ttinclude).

I was able to work around this thank to the new "UpdateColumn" function, but I think this should be fixed in the ttinclude.

Here's the workaround just in case:

UpdateColumn = (Column column, Table table) =>
{
if (column.PropertyType.ToLower() == "guid" && column.IsNullable && column.Default.ToLower().Contains("parse(\"null\")"))
{
column.Default = "null";
}
return column;
};
↧
↧

Commented Issue: Nullable uniqueidentifier with default value generates exception [109]

April 24, 2015, 3:07 am
$
0
0
A table with a column having a nullable uniqueidentifier with a default value NULL:

[MyColumn] UNIQUEIDENTIFIER CONSTRAINT [DF_MyColumn] DEFAULT (NULL) NULL

will result in a Poco having the following line in the constructor:

MyColumn = Guid.Parse("NULL");

This will generate an exception.

The problem seems to be in the "CleanUpDefault" method (EF.Reverse.POCO.Core.ttinclude).

I was able to work around this thank to the new "UpdateColumn" function, but I think this should be fixed in the ttinclude.

Here's the workaround just in case:

UpdateColumn = (Column column, Table table) =>
{
if (column.PropertyType.ToLower() == "guid" && column.IsNullable && column.Default.ToLower().Contains("parse(\"null\")"))
{
column.Default = "null";
}
return column;
};
Comments: All fixed and will be in the next release. Many thanks.
↧

Source code checked in, #459dc88a096e

April 24, 2015, 3:07 am
$
0
0
Case 109. Nullable uniqueidentifier with default value generates exception. Thanks to markuspeter.
↧

Updated Wiki: What's new

April 24, 2015, 3:08 am
$
0
0

Whats comming in the next release:

  1. Remove use of [GeneratedCodeAttribute] where not necessary.
  2. Case 108. Include the schema when calling stored procedures. Thanks to emdadgar2.
  3. Case 109. Nullable uniqueidentifier with default value generates exception. Thanks tomarkuspeter.

Whats new in v2.12.1:

  1. Case 101. SQL Server compact connection string only looks in current project. It now looks in all project paths for the SDF file, in a similar way to finding the app.config file for the connection string.
  2. Much faster TableSQL. Query plan cost is 97% vs 3%. Thanks to Glenn Orr.
  3. Much faster ForeignKeySQL. Query plan cost is 71% vs 29%.
  4. Unique indexes are now checked for. Previously, for tables without primary keys, all the NOT NULL columns used to be marked as a primary key. Now, if the table has a unique index, these unique index columns are used instead. However, the columns are still checked for being NOT NULL as entity framework will not allow a primary key to be made up of a column which can be NULLable.
  5. MakeClassesPartial flag now adds partial keyword to the stored procedure model classes.
  6. Added AdditionalContextInterfaceItems array to allow adding of extra functions to the db context interface.
  7. Fix schema prepending for Stored Procedures. Thanks to Emanov.
  8. Fix bug in MigrationStrategy when set to CreateDatabaseIfNotExists or DropCreateDatabaseIfModelChanges. Thanks toWill.
  9. Case 102. Stored procedures with no input parameters and all columns are nullable views cannot get populated in .cs. Thanks todisanxian.
  10. Calls to stored procedures are now placed in [square brackets] in case there are spaces in its name.
  11. Case 103. Check for column name C# reserved word name clashes. Thanks to swago.
  12. Do not include foreign keys which use composite keys.

Whats new in v2.11.0:

  1. Case 61. Allow excluding/modifying columns. Also permits you to run a function against each column to optionally modify the column properties (eg. to tweak the name of the generated property etc). Thanks toDavid Gardiner.
  2. Case 99. Add ability to specify additional using namespaces. Thanks to rorourke.
  3. Case 100. Apply GeneratedCodeAttribute to generated code. Thanks to David Gardiner.

Whats new in v2.10.2:

  1. Case 93. Merge logic for foreignKey column matching, previously .col=null was possible. Thanks toAHewgill.
  2. StoredProcs that return nullable binary types generate invalid "ReturnModel" code. Thanks toWallyHDisplayName.
  3. Case 96. Add a default for getutcdate(). Thanks to mbargar13.
  4. Case 94. Missing "using DatabaseGeneratedOption = System.ComponentModel.DataAnnotations.Schema.DatabaseGeneratedOption;" when targeting Framework 4.5. Thanks toalexdeblasis.
  5. StoredProcedureRename was being ignored. Thanks to slyCzar.
  6. Case 98. Corrected bridge table issue. Thanks to simooo985.

Whats new in v2.10.1:

  1. Stored Procedure arguments that are C# reserved keywords need escaping. Thanks toJimstr.
  2. Make mapping variables consistent during name clashes. An an edge case could cause different names for the reverse navigation as compared to the Map during name clashes. Thanks toFJRodriguez.
  3. Fix indentation when MakeClassesPartial is set.

Whats new in v2.10.0:

  1. Auto Migrations. To enable set MigrationConfigurationFileName to a class name, "MyDbContextDBMigrationConfiguration" for example. This enabled Entity Framework to update the schema when it is deployed in production. Thanks toFJRodriguez.
  2. Remove use of uses_native_compilation column in Stored Procedure SQL to support older database (< 2014). Thanks toNicholas Head.

Whats new in v2.9.1:

  1. GetSqlDbType was missing some types (nvarchar, and uniqueidentifier). Thanks toWally.
  2. Add in "using System.Linq" if Elements.StoredProcedures declared and not Elements.Context. Thanks toWally.

Whats new in v2.9.0:

  1. Stored procedure support !
    • This includes the ability to retrieve the RESULT from stored procs, as well as the data. A result of 0 means success, any other value is an error.
    • Include stubs for the stored procs in the FakeDbContext.
  2. Sort contents of HasForeignKey(...) by foreign key ordinal.
  3. Prevent creating maps where the left and right side of the map are the same table.
  4. Use a try/catch for WCF projects. Thanks to FJRodriguez.
  5. Include examples of CustomPluralizationEntry. Thanks to Carrie Kroutil.
  6. Allow for manual setting of the targeted .Net framework version.

Whats new in v2.8.3:

  1. Added new setting IncludeQueryTraceOn9481Flag so that you are now in control if "OPTION (QUERYTRACEON 9481)" is appended to the SQL. SqlServer 2014 is known to appear frozen / take a long time when this file is saved. If it does, set this to true (however you will also need elevated privileges).
  2. Added new setting DbContextBaseClass. You can now specify what the base class for your DbContext class is. For example ASP.NET Identity use "IdentityDbContext<ApplicationUser>", or even go so far as a custom: IdentityDbContext<CustomUser, CustomRole, int, CustomUserLogin, CustomUserRole, CustomUserClaim>. Thanks toParag Shravagi.
  3. Fixed bug: IndexOutOfRangeException thrown inside GetCurrentProject. Thanks toDavid Gardiner.
    https://efreversepoco.codeplex.com/workitem/85

Whats new in v2.8.2:

  1. This update is required to fix a problem with Sql Server 2014 as it freezes when obtaining the Foreign Keys. See here for more info. The solution was to add OPTION (QUERYTRACEON 9481). Thanks to@ErikEJ for the solution.
    Using this option flag needs a higher SQL privilege, so you may experience:
    User 'Your.Name' does not have permission to run DBCC TRACEON.
    More info (requires sysadmin rights) http://spaghettidba.com/2013/02/08/using-querytraceon-in-plan-guides/ 

Whats new in v2.8.1:

  1. Bug fix: If property had _ appended, and is used as key, it breaks template generation. Thanks toNicholas Head.

Whats new in v2.8.0:

  1. Added a new flag: AddUnitTestingDbContext. If true, this will create a Fake DbContext and a FakeDbSet<T>. This will allow easy unit testing. Can't believe I never added this sooner. See the documentation Unit Testing.

Whats new in v2.7.0:

  1. Fixed bug: Missing schema specification in ManyToMany tables. Thanks to Vtanman & Snajahi.
  2. Add a timeout when obtaining the schema info from a slow database. Thanks to DotNetWise.
  3. Changed table renaming to use a function. Thanks to DotNetWise.

Whats new in v2.6.3:

  1. Add IsUnicode(false) for the char/varchar columns. Thanks to Naomi N.
  2. Rollback a feature added in 2.5.1: For database types such as Numeric(17,0), the C# type should resolve to something in the "int" family. Thanks toSimmered.

Whats new in v2.6.2:

  1. Include another namespace if Target framework is not 4.0. Thanks to NazmulRockOn.
  2. CR/LF in extended properties caused errors. Thanks to Simmered.
  3. Use IsFixedLength() for char/nchar types. Thanks to Naomi N.

Whats new in v2.6.1:

  1. Added the same extended properties comments facility for SQL CE. Thanks to @ErikEJ

Whats new in v2.6.0:

  1. It now reads the extended properties and can add them to the poco classes in comments. See the new IncludeExtendedPropertyComments flag which is an enumeration of
[Flags]
public enum ExtendedPropertyCommentsStyle
{
  None,
  InSummaryBlock,
  AtEndOfField
};
  • ExtendedPropertyCommentsStyle.None: No extended properties are shown.
  • ExtendedPropertyCommentsStyle.InSummaryBlock: extended properties are shown above field in a ///<summary> block.
  • ExtendedPropertyCommentsStyle.AtEndOfField: extended properties are shown at the end of the field in a comment block.

The IncludeComments flag is completely independent to IncludeExtendedPropertyComments.

If you want completely comment free generate code, set IncludeComments = false, and IncludeExtendedPropertyComments = ExtendedPropertyCommentsStyle.None;

Whats new in v2.5.1:

  1. Move the call to tables.SetPrimaryKeys(); higher up. This allows support of tables with no primary keys to be able to be used. Thanks toJaved.
  2. For database types such as Numeric(17,0), the C# type should resolve to something in the "int" family. Thanks tosimmered.

Whats new in v2.5.0:

  1. Added option to strip and alter table names. Such as tblOrders to Orders, AB_Shipments to Shipments, etc. See Table renaming section.
  2. Added ability to switch off the Pluralization service.
  3. Added ability to use other Pluralization services, such as the SpanishPluralizationService as provided in the "EF6.Contrib" Nuget Package. If you are to use the SpanishPluralizationService, add the following to the top of your database.tt file: <#@ assembly name="C:\<Your path here>\packages\EF6.Contrib.1.0.5\lib\net45\EntityFramework.Contrib.dll" #> Changing the path to where your DLL is situated.

Whats new in v2.4.1:

  1.  Fixed bug: When using .HasForeignKey(...) for multi-column keys, the columns should be listed in ordinal order. Thanks toScott Hodges.

Whats new in v2.4.0

  1. Removed use of System.Data.Entity.DLL from the installation template as it is no longer required for EF 6.
  2. Moved spatial types from System.Data.Spatial to System.Data.Entity.Spatial for EF 6.
  3. Singular names and camel casing configuration were accidentally combined by using the UseCamelCase boolean. Thanks toRune Gulbrandsen.
  4. Added new flag IncludeComments. This controls the generation of comments in the output.
  5. Fixed bug in constructor where a UNIQUEIDENTIFIER column had default value. Thanks togonglei.

Whats new in v2.3.2

  1. Singularize one-to-one Reverse Navigation. Thanks to StormRider.
  2. Bugfix for IsRowVersion() for timestamp columns. Thanks to StormRider.
  3. Do not append "m" to decimal value in poco ctor if default contains an unparsable value.

Whats new in v2.3.0:

  1. SQL Server Compact 4.0 support. Thanks to ErikEJ.

Whats new in v2.2.1:

  1. Add strings to be allowed as computed columns. Thanks to JBJBJB and BrhineScot.
  2. Now includes callbacks during code generation. This means you can add attributes to classes, specify a base class, specify custom code within the class, and finally a call back for each column within the class. Thanks toSimplyFoolish. 
  3. OData doesn't support entities with geometery/geography types. Provided a flag to turn these off if entities are being generated from ODATA.  Thanks toSimplyFoolish. Flag is called DisableGeographyTypes.
  4. Fixed bug with the Pluralisation service. If your current culture was not en, then it would throw an exception. Thanks toErikEJ.

Whats new in v2.2.0:

  1. Now uses the .Net Pluralization service. Thanks to James Manning.
  2. Bug fixed when you have foreign keys between two tables where the FK/PK columns have spaces in the column name. Thanks toColin Smith.
  3. Bug fixed. Solution Folders are not searched for config settings. Thanks to scaftw.
  4. Generate navigation property based on FK name. If there are two FK links to a table, the second link would appear as linkName1. This is now detected and both the FK properties will make use of the FK name. If only one FK is used, then the FK name is not appended to the table name. Thanks to saber_solomon.
  5. Sort the generated Reverse navigation and foriegn keys in POCO classes.

Whats new in v2.1.0:

  1. Fixed bug if default constraint was not in expected format. Thanks to Filipe Fujiy.
  2. Now detects name clashes with C# keywords.
  3. Added "System." to DateTime.Now(), etc to prevent clashes with table field names.
  4. "Configuration" class names are now configurable as "Mapping", "Map", etc.
  5. Added support for Spatial.DbGeometry and Spatial.DbGeography. Thanks to Simply Foolish andJorge Bustos.
  6. Can now have custom collection type for Navigation Properties. "ObservableCollection" for example. Thanks to Simply Foolish.

Whats new in v2.0:

  1. Fixed issue when running 'Transform All T4 Templates' from Visual Studio Build Menu.Thanks to JRoselle.
  2. Changing mappings during runtime is not possible/expensive. A specific DbModelBuilder can be used for each needed database schema.Thanks to meixger.
  3. Added ability to detect and use .IsRowVersion().
  4. Added many-to-many mappings. The generated code now includes calls to .Map(). Therefore the generated code will be different to what you had previously in v1 if you have many-to-many table mappings in your database. Hence the revision change to v2.0.0 as I'm using semantic versioning.

Whats new in v1.12:

  1. VARBINARY(MAX) is now correctly assigned to byte[]. Thanks to Luke91577.
  2. Extending partial class support. Allow specification of file extension for partial classes (i.e. ".generated.cs").Thanks to AB_dreeve.
  3. Fixes issues when targeting .NET 4. .NET 4.0 doesn't include the System.ComponentModel.DataAnnotations.Schema namespace, allow specification of TargetFrameworkVersion.Thanks to AB_dreeve.

Whats new in v1.11:

  1. Including views is now working. For a view to be included, at least one column must not be nullable.Thanks to Delmo Carruzzo.
  2. Added selective generation of components (Poco, Context, UnitOfWork, PocoConfiguration). You can now build entities in your Model project, and context, configuration, unit of work in your Data project. Thanks to kscelfo.
  3. Added PrependSchemaName flag. You can now control if the schema name is prepended to the table name. Thanks to kscelfo.

Whats new in v1.10:

  1. Added UseCamelCase flag to the tt file. You can now control if you want your table and column names CamelCase or left alone: i.e. FieldPersonOrder or field_person_order

Whats new in v1.9.2:

  1. Removed the Linq de-duplication code as it is now being done in SQL. The Linq version did not include the schema name when de-duplicating FK's.

Whats new in v1.9.1:

  1. Added DISTICT to the foreign key SQL. This prevents duplicates from appearing.
    They can appear with SQL such as:
    ALTERTABLE [Mars].[Table2] WITHCHECKADDCONSTRAINT [FK_Table2_Table1]
    FOREIGNKEY([Table1Id]) REFERENCES [Mars].[Table1] ([Id])
ALTERTABLE [Mars].[Table2] CHECKCONSTRAINT [FK_Table2_Table1]

Whats new in v1.9.0:

  1. It now has the ability to read connection strings from other config files/projects.
    It starts by looking at the local project for the named connection string in the following files:
    • app.config
    • web.config
    • app.config.transform
    • web.config.transform
    • or edit the above list in the .tt and specify which file(s) to use
    If not found, it then looks for those files in all the projects within the solution.

Whats new in v1.8.0:

  1. Can now optionally generate separate files. See the new boolean flag GenerateSeparateFiles.
  2. Removed the hard coded 300 second timeout. The timeout can be specified in the connection string.

Whats new in v1.7.1:

  1. Add support for DateTime2
  2. Add support for UnitOfWork and the repository pattern. This means you can now unit test your repositories. See the source code for examples.
  3. Add IDisposable to db context.

Whats new in v1.7.0:

  1. Add .HasPrecision(precision, scale) for fields that have scale. Thanks to @choudeshell

Whats new in v1.6.0:

  1. Enhance ReadSchema performance with early table exclusion.
  2. Now supports columns with symbols and punctuation.
  3. Handles decimal default values.

Whats new in v1.5.1:

  1. A bugfix for WCF. See issue https://efreversepoco.codeplex.com/workitem/4

Whats new in v1.5.0:

  1. Ability to add WCF(DataMember, DataContract attributes) support on Entity. Requested by spatemp

Whats new in v1.4.1:

  1. Foreign keys are only included if they point to a primary key.

Whats new in v1.4.0:

  1. If a field has a default contrainst of GetDate(), add DateTime.Now() in the ctor for the field.
  2. Add support for the datetimeoffset type, including support for the default constraint sysdatetimeoffset().
  3. Add Resharper naming comments.
  4. Mappings should be marked internal. Requested by Hobbes Pirakitti
↧
Search

Edited Issue: Stored procedure return column name tidy up could bring all Null value [107]

April 24, 2015, 3:10 am
$
0
0
EF.Reverse.POCO.Generator has a code snippet to tide up stored procedure's return column name, here is code:

proc.ReturnColumns = ds.Tables[0].Columns.Cast<DataColumn>().ToList();
// Tidy up
foreach (var col in proc.ReturnColumns)
{
col.ColumnName = Regex.Replace(col.ColumnName, @"[^A-Za-z0-9\s]*", "");
col.ColumnName = Inflector.ToTitleCase(col.ColumnName).Replace(" ", "");
}

This could bring an issues that C# code cannot get correct stored procedure query result when column name has underline(s), e.g. if column name is "student_score", after tidy up, in return model class, corresponding property name is "StudentScore", in the list of query result, this property StudentScore is always NULL.
↧
↧

Commented Issue: Stored procedure return column name tidy up could bring all Null value [107]

April 24, 2015, 3:10 am
$
0
0
EF.Reverse.POCO.Generator has a code snippet to tide up stored procedure's return column name, here is code:

proc.ReturnColumns = ds.Tables[0].Columns.Cast<DataColumn>().ToList();
// Tidy up
foreach (var col in proc.ReturnColumns)
{
col.ColumnName = Regex.Replace(col.ColumnName, @"[^A-Za-z0-9\s]*", "");
col.ColumnName = Inflector.ToTitleCase(col.ColumnName).Replace(" ", "");
}

This could bring an issues that C# code cannot get correct stored procedure query result when column name has underline(s), e.g. if column name is "student_score", after tidy up, in return model class, corresponding property name is "StudentScore", in the list of query result, this property StudentScore is always NULL.
Comments: This is all fixed and will be in the next release. Thanks.
↧

Updated Wiki: What's new

April 24, 2015, 3:11 am
$
0
0

Whats comming in the next release:

  1. Remove use of [GeneratedCodeAttribute] where not necessary.
  2. Case 108. Include the schema when calling stored procedures. Thanks to emdadgar2.
  3. Case 109. Nullable uniqueidentifier with default value generates exception. Thanks tomarkuspeter.
  4. Case 107. Stored procedure return column name tidy up could bring all Null value. Thanks todisanxian.

Whats new in v2.12.1:

  1. Case 101. SQL Server compact connection string only looks in current project. It now looks in all project paths for the SDF file, in a similar way to finding the app.config file for the connection string.
  2. Much faster TableSQL. Query plan cost is 97% vs 3%. Thanks to Glenn Orr.
  3. Much faster ForeignKeySQL. Query plan cost is 71% vs 29%.
  4. Unique indexes are now checked for. Previously, for tables without primary keys, all the NOT NULL columns used to be marked as a primary key. Now, if the table has a unique index, these unique index columns are used instead. However, the columns are still checked for being NOT NULL as entity framework will not allow a primary key to be made up of a column which can be NULLable.
  5. MakeClassesPartial flag now adds partial keyword to the stored procedure model classes.
  6. Added AdditionalContextInterfaceItems array to allow adding of extra functions to the db context interface.
  7. Fix schema prepending for Stored Procedures. Thanks to Emanov.
  8. Fix bug in MigrationStrategy when set to CreateDatabaseIfNotExists or DropCreateDatabaseIfModelChanges. Thanks toWill.
  9. Case 102. Stored procedures with no input parameters and all columns are nullable views cannot get populated in .cs. Thanks todisanxian.
  10. Calls to stored procedures are now placed in [square brackets] in case there are spaces in its name.
  11. Case 103. Check for column name C# reserved word name clashes. Thanks to swago.
  12. Do not include foreign keys which use composite keys.

Whats new in v2.11.0:

  1. Case 61. Allow excluding/modifying columns. Also permits you to run a function against each column to optionally modify the column properties (eg. to tweak the name of the generated property etc). Thanks toDavid Gardiner.
  2. Case 99. Add ability to specify additional using namespaces. Thanks to rorourke.
  3. Case 100. Apply GeneratedCodeAttribute to generated code. Thanks to David Gardiner.

Whats new in v2.10.2:

  1. Case 93. Merge logic for foreignKey column matching, previously .col=null was possible. Thanks toAHewgill.
  2. StoredProcs that return nullable binary types generate invalid "ReturnModel" code. Thanks toWallyHDisplayName.
  3. Case 96. Add a default for getutcdate(). Thanks to mbargar13.
  4. Case 94. Missing "using DatabaseGeneratedOption = System.ComponentModel.DataAnnotations.Schema.DatabaseGeneratedOption;" when targeting Framework 4.5. Thanks toalexdeblasis.
  5. StoredProcedureRename was being ignored. Thanks to slyCzar.
  6. Case 98. Corrected bridge table issue. Thanks to simooo985.

Whats new in v2.10.1:

  1. Stored Procedure arguments that are C# reserved keywords need escaping. Thanks toJimstr.
  2. Make mapping variables consistent during name clashes. An an edge case could cause different names for the reverse navigation as compared to the Map during name clashes. Thanks toFJRodriguez.
  3. Fix indentation when MakeClassesPartial is set.

Whats new in v2.10.0:

  1. Auto Migrations. To enable set MigrationConfigurationFileName to a class name, "MyDbContextDBMigrationConfiguration" for example. This enabled Entity Framework to update the schema when it is deployed in production. Thanks toFJRodriguez.
  2. Remove use of uses_native_compilation column in Stored Procedure SQL to support older database (< 2014). Thanks toNicholas Head.

Whats new in v2.9.1:

  1. GetSqlDbType was missing some types (nvarchar, and uniqueidentifier). Thanks toWally.
  2. Add in "using System.Linq" if Elements.StoredProcedures declared and not Elements.Context. Thanks toWally.

Whats new in v2.9.0:

  1. Stored procedure support !
    • This includes the ability to retrieve the RESULT from stored procs, as well as the data. A result of 0 means success, any other value is an error.
    • Include stubs for the stored procs in the FakeDbContext.
  2. Sort contents of HasForeignKey(...) by foreign key ordinal.
  3. Prevent creating maps where the left and right side of the map are the same table.
  4. Use a try/catch for WCF projects. Thanks to FJRodriguez.
  5. Include examples of CustomPluralizationEntry. Thanks to Carrie Kroutil.
  6. Allow for manual setting of the targeted .Net framework version.

Whats new in v2.8.3:

  1. Added new setting IncludeQueryTraceOn9481Flag so that you are now in control if "OPTION (QUERYTRACEON 9481)" is appended to the SQL. SqlServer 2014 is known to appear frozen / take a long time when this file is saved. If it does, set this to true (however you will also need elevated privileges).
  2. Added new setting DbContextBaseClass. You can now specify what the base class for your DbContext class is. For example ASP.NET Identity use "IdentityDbContext<ApplicationUser>", or even go so far as a custom: IdentityDbContext<CustomUser, CustomRole, int, CustomUserLogin, CustomUserRole, CustomUserClaim>. Thanks toParag Shravagi.
  3. Fixed bug: IndexOutOfRangeException thrown inside GetCurrentProject. Thanks toDavid Gardiner.
    https://efreversepoco.codeplex.com/workitem/85

Whats new in v2.8.2:

  1. This update is required to fix a problem with Sql Server 2014 as it freezes when obtaining the Foreign Keys. See here for more info. The solution was to add OPTION (QUERYTRACEON 9481). Thanks to@ErikEJ for the solution.
    Using this option flag needs a higher SQL privilege, so you may experience:
    User 'Your.Name' does not have permission to run DBCC TRACEON.
    More info (requires sysadmin rights) http://spaghettidba.com/2013/02/08/using-querytraceon-in-plan-guides/ 

Whats new in v2.8.1:

  1. Bug fix: If property had _ appended, and is used as key, it breaks template generation. Thanks toNicholas Head.

Whats new in v2.8.0:

  1. Added a new flag: AddUnitTestingDbContext. If true, this will create a Fake DbContext and a FakeDbSet<T>. This will allow easy unit testing. Can't believe I never added this sooner. See the documentation Unit Testing.

Whats new in v2.7.0:

  1. Fixed bug: Missing schema specification in ManyToMany tables. Thanks to Vtanman & Snajahi.
  2. Add a timeout when obtaining the schema info from a slow database. Thanks to DotNetWise.
  3. Changed table renaming to use a function. Thanks to DotNetWise.

Whats new in v2.6.3:

  1. Add IsUnicode(false) for the char/varchar columns. Thanks to Naomi N.
  2. Rollback a feature added in 2.5.1: For database types such as Numeric(17,0), the C# type should resolve to something in the "int" family. Thanks toSimmered.

Whats new in v2.6.2:

  1. Include another namespace if Target framework is not 4.0. Thanks to NazmulRockOn.
  2. CR/LF in extended properties caused errors. Thanks to Simmered.
  3. Use IsFixedLength() for char/nchar types. Thanks to Naomi N.

Whats new in v2.6.1:

  1. Added the same extended properties comments facility for SQL CE. Thanks to @ErikEJ

Whats new in v2.6.0:

  1. It now reads the extended properties and can add them to the poco classes in comments. See the new IncludeExtendedPropertyComments flag which is an enumeration of
[Flags]
public enum ExtendedPropertyCommentsStyle
{
  None,
  InSummaryBlock,
  AtEndOfField
};
  • ExtendedPropertyCommentsStyle.None: No extended properties are shown.
  • ExtendedPropertyCommentsStyle.InSummaryBlock: extended properties are shown above field in a ///<summary> block.
  • ExtendedPropertyCommentsStyle.AtEndOfField: extended properties are shown at the end of the field in a comment block.

The IncludeComments flag is completely independent to IncludeExtendedPropertyComments.

If you want completely comment free generate code, set IncludeComments = false, and IncludeExtendedPropertyComments = ExtendedPropertyCommentsStyle.None;

Whats new in v2.5.1:

  1. Move the call to tables.SetPrimaryKeys(); higher up. This allows support of tables with no primary keys to be able to be used. Thanks toJaved.
  2. For database types such as Numeric(17,0), the C# type should resolve to something in the "int" family. Thanks tosimmered.

Whats new in v2.5.0:

  1. Added option to strip and alter table names. Such as tblOrders to Orders, AB_Shipments to Shipments, etc. See Table renaming section.
  2. Added ability to switch off the Pluralization service.
  3. Added ability to use other Pluralization services, such as the SpanishPluralizationService as provided in the "EF6.Contrib" Nuget Package. If you are to use the SpanishPluralizationService, add the following to the top of your database.tt file: <#@ assembly name="C:\<Your path here>\packages\EF6.Contrib.1.0.5\lib\net45\EntityFramework.Contrib.dll" #> Changing the path to where your DLL is situated.

Whats new in v2.4.1:

  1.  Fixed bug: When using .HasForeignKey(...) for multi-column keys, the columns should be listed in ordinal order. Thanks toScott Hodges.

Whats new in v2.4.0

  1. Removed use of System.Data.Entity.DLL from the installation template as it is no longer required for EF 6.
  2. Moved spatial types from System.Data.Spatial to System.Data.Entity.Spatial for EF 6.
  3. Singular names and camel casing configuration were accidentally combined by using the UseCamelCase boolean. Thanks toRune Gulbrandsen.
  4. Added new flag IncludeComments. This controls the generation of comments in the output.
  5. Fixed bug in constructor where a UNIQUEIDENTIFIER column had default value. Thanks togonglei.

Whats new in v2.3.2

  1. Singularize one-to-one Reverse Navigation. Thanks to StormRider.
  2. Bugfix for IsRowVersion() for timestamp columns. Thanks to StormRider.
  3. Do not append "m" to decimal value in poco ctor if default contains an unparsable value.

Whats new in v2.3.0:

  1. SQL Server Compact 4.0 support. Thanks to ErikEJ.

Whats new in v2.2.1:

  1. Add strings to be allowed as computed columns. Thanks to JBJBJB and BrhineScot.
  2. Now includes callbacks during code generation. This means you can add attributes to classes, specify a base class, specify custom code within the class, and finally a call back for each column within the class. Thanks toSimplyFoolish. 
  3. OData doesn't support entities with geometery/geography types. Provided a flag to turn these off if entities are being generated from ODATA.  Thanks toSimplyFoolish. Flag is called DisableGeographyTypes.
  4. Fixed bug with the Pluralisation service. If your current culture was not en, then it would throw an exception. Thanks toErikEJ.

Whats new in v2.2.0:

  1. Now uses the .Net Pluralization service. Thanks to James Manning.
  2. Bug fixed when you have foreign keys between two tables where the FK/PK columns have spaces in the column name. Thanks toColin Smith.
  3. Bug fixed. Solution Folders are not searched for config settings. Thanks to scaftw.
  4. Generate navigation property based on FK name. If there are two FK links to a table, the second link would appear as linkName1. This is now detected and both the FK properties will make use of the FK name. If only one FK is used, then the FK name is not appended to the table name. Thanks to saber_solomon.
  5. Sort the generated Reverse navigation and foriegn keys in POCO classes.

Whats new in v2.1.0:

  1. Fixed bug if default constraint was not in expected format. Thanks to Filipe Fujiy.
  2. Now detects name clashes with C# keywords.
  3. Added "System." to DateTime.Now(), etc to prevent clashes with table field names.
  4. "Configuration" class names are now configurable as "Mapping", "Map", etc.
  5. Added support for Spatial.DbGeometry and Spatial.DbGeography. Thanks to Simply Foolish andJorge Bustos.
  6. Can now have custom collection type for Navigation Properties. "ObservableCollection" for example. Thanks to Simply Foolish.

Whats new in v2.0:

  1. Fixed issue when running 'Transform All T4 Templates' from Visual Studio Build Menu.Thanks to JRoselle.
  2. Changing mappings during runtime is not possible/expensive. A specific DbModelBuilder can be used for each needed database schema.Thanks to meixger.
  3. Added ability to detect and use .IsRowVersion().
  4. Added many-to-many mappings. The generated code now includes calls to .Map(). Therefore the generated code will be different to what you had previously in v1 if you have many-to-many table mappings in your database. Hence the revision change to v2.0.0 as I'm using semantic versioning.

Whats new in v1.12:

  1. VARBINARY(MAX) is now correctly assigned to byte[]. Thanks to Luke91577.
  2. Extending partial class support. Allow specification of file extension for partial classes (i.e. ".generated.cs").Thanks to AB_dreeve.
  3. Fixes issues when targeting .NET 4. .NET 4.0 doesn't include the System.ComponentModel.DataAnnotations.Schema namespace, allow specification of TargetFrameworkVersion.Thanks to AB_dreeve.

Whats new in v1.11:

  1. Including views is now working. For a view to be included, at least one column must not be nullable.Thanks to Delmo Carruzzo.
  2. Added selective generation of components (Poco, Context, UnitOfWork, PocoConfiguration). You can now build entities in your Model project, and context, configuration, unit of work in your Data project. Thanks to kscelfo.
  3. Added PrependSchemaName flag. You can now control if the schema name is prepended to the table name. Thanks to kscelfo.

Whats new in v1.10:

  1. Added UseCamelCase flag to the tt file. You can now control if you want your table and column names CamelCase or left alone: i.e. FieldPersonOrder or field_person_order

Whats new in v1.9.2:

  1. Removed the Linq de-duplication code as it is now being done in SQL. The Linq version did not include the schema name when de-duplicating FK's.

Whats new in v1.9.1:

  1. Added DISTICT to the foreign key SQL. This prevents duplicates from appearing.
    They can appear with SQL such as:
    ALTERTABLE [Mars].[Table2] WITHCHECKADDCONSTRAINT [FK_Table2_Table1]
    FOREIGNKEY([Table1Id]) REFERENCES [Mars].[Table1] ([Id])
ALTERTABLE [Mars].[Table2] CHECKCONSTRAINT [FK_Table2_Table1]

Whats new in v1.9.0:

  1. It now has the ability to read connection strings from other config files/projects.
    It starts by looking at the local project for the named connection string in the following files:
    • app.config
    • web.config
    • app.config.transform
    • web.config.transform
    • or edit the above list in the .tt and specify which file(s) to use
    If not found, it then looks for those files in all the projects within the solution.

Whats new in v1.8.0:

  1. Can now optionally generate separate files. See the new boolean flag GenerateSeparateFiles.
  2. Removed the hard coded 300 second timeout. The timeout can be specified in the connection string.

Whats new in v1.7.1:

  1. Add support for DateTime2
  2. Add support for UnitOfWork and the repository pattern. This means you can now unit test your repositories. See the source code for examples.
  3. Add IDisposable to db context.

Whats new in v1.7.0:

  1. Add .HasPrecision(precision, scale) for fields that have scale. Thanks to @choudeshell

Whats new in v1.6.0:

  1. Enhance ReadSchema performance with early table exclusion.
  2. Now supports columns with symbols and punctuation.
  3. Handles decimal default values.

Whats new in v1.5.1:

  1. A bugfix for WCF. See issue https://efreversepoco.codeplex.com/workitem/4

Whats new in v1.5.0:

  1. Ability to add WCF(DataMember, DataContract attributes) support on Entity. Requested by spatemp

Whats new in v1.4.1:

  1. Foreign keys are only included if they point to a primary key.

Whats new in v1.4.0:

  1. If a field has a default contrainst of GetDate(), add DateTime.Now() in the ctor for the field.
  2. Add support for the datetimeoffset type, including support for the default constraint sysdatetimeoffset().
  3. Add Resharper naming comments.
  4. Mappings should be marked internal. Requested by Hobbes Pirakitti
↧

Source code checked in, #815653e744d4

April 24, 2015, 3:36 am
$
0
0
Case 106. Add support for async methods. Thanks to youngcm2
↧

Updated Wiki: What's new

April 24, 2015, 3:37 am
$
0
0

Whats comming in the next release:

  1. Remove use of [GeneratedCodeAttribute] where not necessary.
  2. Case 108. Include the schema when calling stored procedures. Thanks to emdadgar2.
  3. Case 109. Nullable uniqueidentifier with default value generates exception. Thanks tomarkuspeter.
  4. Case 107. Stored procedure return column name tidy up could bring all Null value. Thanks todisanxian.
  5. Case 106. Add support for async methods. Thanks to youngcm2.

Whats new in v2.12.1:

  1. Case 101. SQL Server compact connection string only looks in current project. It now looks in all project paths for the SDF file, in a similar way to finding the app.config file for the connection string.
  2. Much faster TableSQL. Query plan cost is 97% vs 3%. Thanks to Glenn Orr.
  3. Much faster ForeignKeySQL. Query plan cost is 71% vs 29%.
  4. Unique indexes are now checked for. Previously, for tables without primary keys, all the NOT NULL columns used to be marked as a primary key. Now, if the table has a unique index, these unique index columns are used instead. However, the columns are still checked for being NOT NULL as entity framework will not allow a primary key to be made up of a column which can be NULLable.
  5. MakeClassesPartial flag now adds partial keyword to the stored procedure model classes.
  6. Added AdditionalContextInterfaceItems array to allow adding of extra functions to the db context interface.
  7. Fix schema prepending for Stored Procedures. Thanks to Emanov.
  8. Fix bug in MigrationStrategy when set to CreateDatabaseIfNotExists or DropCreateDatabaseIfModelChanges. Thanks toWill.
  9. Case 102. Stored procedures with no input parameters and all columns are nullable views cannot get populated in .cs. Thanks todisanxian.
  10. Calls to stored procedures are now placed in [square brackets] in case there are spaces in its name.
  11. Case 103. Check for column name C# reserved word name clashes. Thanks to swago.
  12. Do not include foreign keys which use composite keys.

Whats new in v2.11.0:

  1. Case 61. Allow excluding/modifying columns. Also permits you to run a function against each column to optionally modify the column properties (eg. to tweak the name of the generated property etc). Thanks toDavid Gardiner.
  2. Case 99. Add ability to specify additional using namespaces. Thanks to rorourke.
  3. Case 100. Apply GeneratedCodeAttribute to generated code. Thanks to David Gardiner.

Whats new in v2.10.2:

  1. Case 93. Merge logic for foreignKey column matching, previously .col=null was possible. Thanks toAHewgill.
  2. StoredProcs that return nullable binary types generate invalid "ReturnModel" code. Thanks toWallyHDisplayName.
  3. Case 96. Add a default for getutcdate(). Thanks to mbargar13.
  4. Case 94. Missing "using DatabaseGeneratedOption = System.ComponentModel.DataAnnotations.Schema.DatabaseGeneratedOption;" when targeting Framework 4.5. Thanks toalexdeblasis.
  5. StoredProcedureRename was being ignored. Thanks to slyCzar.
  6. Case 98. Corrected bridge table issue. Thanks to simooo985.

Whats new in v2.10.1:

  1. Stored Procedure arguments that are C# reserved keywords need escaping. Thanks toJimstr.
  2. Make mapping variables consistent during name clashes. An an edge case could cause different names for the reverse navigation as compared to the Map during name clashes. Thanks toFJRodriguez.
  3. Fix indentation when MakeClassesPartial is set.

Whats new in v2.10.0:

  1. Auto Migrations. To enable set MigrationConfigurationFileName to a class name, "MyDbContextDBMigrationConfiguration" for example. This enabled Entity Framework to update the schema when it is deployed in production. Thanks toFJRodriguez.
  2. Remove use of uses_native_compilation column in Stored Procedure SQL to support older database (< 2014). Thanks toNicholas Head.

Whats new in v2.9.1:

  1. GetSqlDbType was missing some types (nvarchar, and uniqueidentifier). Thanks toWally.
  2. Add in "using System.Linq" if Elements.StoredProcedures declared and not Elements.Context. Thanks toWally.

Whats new in v2.9.0:

  1. Stored procedure support !
    • This includes the ability to retrieve the RESULT from stored procs, as well as the data. A result of 0 means success, any other value is an error.
    • Include stubs for the stored procs in the FakeDbContext.
  2. Sort contents of HasForeignKey(...) by foreign key ordinal.
  3. Prevent creating maps where the left and right side of the map are the same table.
  4. Use a try/catch for WCF projects. Thanks to FJRodriguez.
  5. Include examples of CustomPluralizationEntry. Thanks to Carrie Kroutil.
  6. Allow for manual setting of the targeted .Net framework version.

Whats new in v2.8.3:

  1. Added new setting IncludeQueryTraceOn9481Flag so that you are now in control if "OPTION (QUERYTRACEON 9481)" is appended to the SQL. SqlServer 2014 is known to appear frozen / take a long time when this file is saved. If it does, set this to true (however you will also need elevated privileges).
  2. Added new setting DbContextBaseClass. You can now specify what the base class for your DbContext class is. For example ASP.NET Identity use "IdentityDbContext<ApplicationUser>", or even go so far as a custom: IdentityDbContext<CustomUser, CustomRole, int, CustomUserLogin, CustomUserRole, CustomUserClaim>. Thanks toParag Shravagi.
  3. Fixed bug: IndexOutOfRangeException thrown inside GetCurrentProject. Thanks toDavid Gardiner.
    https://efreversepoco.codeplex.com/workitem/85

Whats new in v2.8.2:

  1. This update is required to fix a problem with Sql Server 2014 as it freezes when obtaining the Foreign Keys. See here for more info. The solution was to add OPTION (QUERYTRACEON 9481). Thanks to@ErikEJ for the solution.
    Using this option flag needs a higher SQL privilege, so you may experience:
    User 'Your.Name' does not have permission to run DBCC TRACEON.
    More info (requires sysadmin rights) http://spaghettidba.com/2013/02/08/using-querytraceon-in-plan-guides/ 

Whats new in v2.8.1:

  1. Bug fix: If property had _ appended, and is used as key, it breaks template generation. Thanks toNicholas Head.

Whats new in v2.8.0:

  1. Added a new flag: AddUnitTestingDbContext. If true, this will create a Fake DbContext and a FakeDbSet<T>. This will allow easy unit testing. Can't believe I never added this sooner. See the documentation Unit Testing.

Whats new in v2.7.0:

  1. Fixed bug: Missing schema specification in ManyToMany tables. Thanks to Vtanman & Snajahi.
  2. Add a timeout when obtaining the schema info from a slow database. Thanks to DotNetWise.
  3. Changed table renaming to use a function. Thanks to DotNetWise.

Whats new in v2.6.3:

  1. Add IsUnicode(false) for the char/varchar columns. Thanks to Naomi N.
  2. Rollback a feature added in 2.5.1: For database types such as Numeric(17,0), the C# type should resolve to something in the "int" family. Thanks toSimmered.

Whats new in v2.6.2:

  1. Include another namespace if Target framework is not 4.0. Thanks to NazmulRockOn.
  2. CR/LF in extended properties caused errors. Thanks to Simmered.
  3. Use IsFixedLength() for char/nchar types. Thanks to Naomi N.

Whats new in v2.6.1:

  1. Added the same extended properties comments facility for SQL CE. Thanks to @ErikEJ

Whats new in v2.6.0:

  1. It now reads the extended properties and can add them to the poco classes in comments. See the new IncludeExtendedPropertyComments flag which is an enumeration of
[Flags]
public enum ExtendedPropertyCommentsStyle
{
  None,
  InSummaryBlock,
  AtEndOfField
};
  • ExtendedPropertyCommentsStyle.None: No extended properties are shown.
  • ExtendedPropertyCommentsStyle.InSummaryBlock: extended properties are shown above field in a ///<summary> block.
  • ExtendedPropertyCommentsStyle.AtEndOfField: extended properties are shown at the end of the field in a comment block.

The IncludeComments flag is completely independent to IncludeExtendedPropertyComments.

If you want completely comment free generate code, set IncludeComments = false, and IncludeExtendedPropertyComments = ExtendedPropertyCommentsStyle.None;

Whats new in v2.5.1:

  1. Move the call to tables.SetPrimaryKeys(); higher up. This allows support of tables with no primary keys to be able to be used. Thanks toJaved.
  2. For database types such as Numeric(17,0), the C# type should resolve to something in the "int" family. Thanks tosimmered.

Whats new in v2.5.0:

  1. Added option to strip and alter table names. Such as tblOrders to Orders, AB_Shipments to Shipments, etc. See Table renaming section.
  2. Added ability to switch off the Pluralization service.
  3. Added ability to use other Pluralization services, such as the SpanishPluralizationService as provided in the "EF6.Contrib" Nuget Package. If you are to use the SpanishPluralizationService, add the following to the top of your database.tt file: <#@ assembly name="C:\<Your path here>\packages\EF6.Contrib.1.0.5\lib\net45\EntityFramework.Contrib.dll" #> Changing the path to where your DLL is situated.

Whats new in v2.4.1:

  1.  Fixed bug: When using .HasForeignKey(...) for multi-column keys, the columns should be listed in ordinal order. Thanks toScott Hodges.

Whats new in v2.4.0

  1. Removed use of System.Data.Entity.DLL from the installation template as it is no longer required for EF 6.
  2. Moved spatial types from System.Data.Spatial to System.Data.Entity.Spatial for EF 6.
  3. Singular names and camel casing configuration were accidentally combined by using the UseCamelCase boolean. Thanks toRune Gulbrandsen.
  4. Added new flag IncludeComments. This controls the generation of comments in the output.
  5. Fixed bug in constructor where a UNIQUEIDENTIFIER column had default value. Thanks togonglei.

Whats new in v2.3.2

  1. Singularize one-to-one Reverse Navigation. Thanks to StormRider.
  2. Bugfix for IsRowVersion() for timestamp columns. Thanks to StormRider.
  3. Do not append "m" to decimal value in poco ctor if default contains an unparsable value.

Whats new in v2.3.0:

  1. SQL Server Compact 4.0 support. Thanks to ErikEJ.

Whats new in v2.2.1:

  1. Add strings to be allowed as computed columns. Thanks to JBJBJB and BrhineScot.
  2. Now includes callbacks during code generation. This means you can add attributes to classes, specify a base class, specify custom code within the class, and finally a call back for each column within the class. Thanks toSimplyFoolish. 
  3. OData doesn't support entities with geometery/geography types. Provided a flag to turn these off if entities are being generated from ODATA.  Thanks toSimplyFoolish. Flag is called DisableGeographyTypes.
  4. Fixed bug with the Pluralisation service. If your current culture was not en, then it would throw an exception. Thanks toErikEJ.

Whats new in v2.2.0:

  1. Now uses the .Net Pluralization service. Thanks to James Manning.
  2. Bug fixed when you have foreign keys between two tables where the FK/PK columns have spaces in the column name. Thanks toColin Smith.
  3. Bug fixed. Solution Folders are not searched for config settings. Thanks to scaftw.
  4. Generate navigation property based on FK name. If there are two FK links to a table, the second link would appear as linkName1. This is now detected and both the FK properties will make use of the FK name. If only one FK is used, then the FK name is not appended to the table name. Thanks to saber_solomon.
  5. Sort the generated Reverse navigation and foriegn keys in POCO classes.

Whats new in v2.1.0:

  1. Fixed bug if default constraint was not in expected format. Thanks to Filipe Fujiy.
  2. Now detects name clashes with C# keywords.
  3. Added "System." to DateTime.Now(), etc to prevent clashes with table field names.
  4. "Configuration" class names are now configurable as "Mapping", "Map", etc.
  5. Added support for Spatial.DbGeometry and Spatial.DbGeography. Thanks to Simply Foolish andJorge Bustos.
  6. Can now have custom collection type for Navigation Properties. "ObservableCollection" for example. Thanks to Simply Foolish.

Whats new in v2.0:

  1. Fixed issue when running 'Transform All T4 Templates' from Visual Studio Build Menu.Thanks to JRoselle.
  2. Changing mappings during runtime is not possible/expensive. A specific DbModelBuilder can be used for each needed database schema.Thanks to meixger.
  3. Added ability to detect and use .IsRowVersion().
  4. Added many-to-many mappings. The generated code now includes calls to .Map(). Therefore the generated code will be different to what you had previously in v1 if you have many-to-many table mappings in your database. Hence the revision change to v2.0.0 as I'm using semantic versioning.

Whats new in v1.12:

  1. VARBINARY(MAX) is now correctly assigned to byte[]. Thanks to Luke91577.
  2. Extending partial class support. Allow specification of file extension for partial classes (i.e. ".generated.cs").Thanks to AB_dreeve.
  3. Fixes issues when targeting .NET 4. .NET 4.0 doesn't include the System.ComponentModel.DataAnnotations.Schema namespace, allow specification of TargetFrameworkVersion.Thanks to AB_dreeve.

Whats new in v1.11:

  1. Including views is now working. For a view to be included, at least one column must not be nullable.Thanks to Delmo Carruzzo.
  2. Added selective generation of components (Poco, Context, UnitOfWork, PocoConfiguration). You can now build entities in your Model project, and context, configuration, unit of work in your Data project. Thanks to kscelfo.
  3. Added PrependSchemaName flag. You can now control if the schema name is prepended to the table name. Thanks to kscelfo.

Whats new in v1.10:

  1. Added UseCamelCase flag to the tt file. You can now control if you want your table and column names CamelCase or left alone: i.e. FieldPersonOrder or field_person_order

Whats new in v1.9.2:

  1. Removed the Linq de-duplication code as it is now being done in SQL. The Linq version did not include the schema name when de-duplicating FK's.

Whats new in v1.9.1:

  1. Added DISTICT to the foreign key SQL. This prevents duplicates from appearing.
    They can appear with SQL such as:
    ALTERTABLE [Mars].[Table2] WITHCHECKADDCONSTRAINT [FK_Table2_Table1]
    FOREIGNKEY([Table1Id]) REFERENCES [Mars].[Table1] ([Id])
ALTERTABLE [Mars].[Table2] CHECKCONSTRAINT [FK_Table2_Table1]

Whats new in v1.9.0:

  1. It now has the ability to read connection strings from other config files/projects.
    It starts by looking at the local project for the named connection string in the following files:
    • app.config
    • web.config
    • app.config.transform
    • web.config.transform
    • or edit the above list in the .tt and specify which file(s) to use
    If not found, it then looks for those files in all the projects within the solution.

Whats new in v1.8.0:

  1. Can now optionally generate separate files. See the new boolean flag GenerateSeparateFiles.
  2. Removed the hard coded 300 second timeout. The timeout can be specified in the connection string.

Whats new in v1.7.1:

  1. Add support for DateTime2
  2. Add support for UnitOfWork and the repository pattern. This means you can now unit test your repositories. See the source code for examples.
  3. Add IDisposable to db context.

Whats new in v1.7.0:

  1. Add .HasPrecision(precision, scale) for fields that have scale. Thanks to @choudeshell

Whats new in v1.6.0:

  1. Enhance ReadSchema performance with early table exclusion.
  2. Now supports columns with symbols and punctuation.
  3. Handles decimal default values.

Whats new in v1.5.1:

  1. A bugfix for WCF. See issue https://efreversepoco.codeplex.com/workitem/4

Whats new in v1.5.0:

  1. Ability to add WCF(DataMember, DataContract attributes) support on Entity. Requested by spatemp

Whats new in v1.4.1:

  1. Foreign keys are only included if they point to a primary key.

Whats new in v1.4.0:

  1. If a field has a default contrainst of GetDate(), add DateTime.Now() in the ctor for the field.
  2. Add support for the datetimeoffset type, including support for the default constraint sysdatetimeoffset().
  3. Add Resharper naming comments.
  4. Mappings should be marked internal. Requested by Hobbes Pirakitti
↧
↧

Edited Feature: Add support for async methods [106]

April 24, 2015, 3:38 am
$
0
0
I added to the interface the following: I have attached the changes.
```
Task<int> SaveChangesAsync();
Task<int> SaveChangesAsync(CancellationToken cancellationToken);
```
↧

Commented Feature: Add support for async methods [106]

April 24, 2015, 3:38 am
$
0
0
I added to the interface the following: I have attached the changes.
```
Task<int> SaveChangesAsync();
Task<int> SaveChangesAsync(CancellationToken cancellationToken);
```
Comments: This has been added and will be in the next release. I check for framework v4.5 and above and will add in Async.
↧
Search

Source code checked in, #b59d2a0a2a27

April 24, 2015, 4:45 am
$
0
0
Changed the stored procedure parameters to be nullable. Thanks to Suraj Ramalingam.
↧

Updated Wiki: What's new

April 24, 2015, 4:49 am
$
0
0

Whats comming in the next release:

  1. Remove use of [GeneratedCodeAttribute] where not necessary.
  2. Case 108. Include the schema when calling stored procedures. Thanks to emdadgar2.
  3. Case 109. Nullable uniqueidentifier with default value generates exception. Thanks tomarkuspeter.
  4. Case 107. Stored procedure return column name tidy up could bring all Null value. Thanks todisanxian.
  5. Case 106. Add support for async methods. Thanks to youngcm2.
  6. Changed the stored procedure parameters to be nullable. Thanks to Suraj Ramalingam.

Whats new in v2.12.1:

  1. Case 101. SQL Server compact connection string only looks in current project. It now looks in all project paths for the SDF file, in a similar way to finding the app.config file for the connection string.
  2. Much faster TableSQL. Query plan cost is 97% vs 3%. Thanks to Glenn Orr.
  3. Much faster ForeignKeySQL. Query plan cost is 71% vs 29%.
  4. Unique indexes are now checked for. Previously, for tables without primary keys, all the NOT NULL columns used to be marked as a primary key. Now, if the table has a unique index, these unique index columns are used instead. However, the columns are still checked for being NOT NULL as entity framework will not allow a primary key to be made up of a column which can be NULLable.
  5. MakeClassesPartial flag now adds partial keyword to the stored procedure model classes.
  6. Added AdditionalContextInterfaceItems array to allow adding of extra functions to the db context interface.
  7. Fix schema prepending for Stored Procedures. Thanks to Emanov.
  8. Fix bug in MigrationStrategy when set to CreateDatabaseIfNotExists or DropCreateDatabaseIfModelChanges. Thanks toWill.
  9. Case 102. Stored procedures with no input parameters and all columns are nullable views cannot get populated in .cs. Thanks todisanxian.
  10. Calls to stored procedures are now placed in [square brackets] in case there are spaces in its name.
  11. Case 103. Check for column name C# reserved word name clashes. Thanks to swago.
  12. Do not include foreign keys which use composite keys.

Whats new in v2.11.0:

  1. Case 61. Allow excluding/modifying columns. Also permits you to run a function against each column to optionally modify the column properties (eg. to tweak the name of the generated property etc). Thanks toDavid Gardiner.
  2. Case 99. Add ability to specify additional using namespaces. Thanks to rorourke.
  3. Case 100. Apply GeneratedCodeAttribute to generated code. Thanks to David Gardiner.

Whats new in v2.10.2:

  1. Case 93. Merge logic for foreignKey column matching, previously .col=null was possible. Thanks toAHewgill.
  2. StoredProcs that return nullable binary types generate invalid "ReturnModel" code. Thanks toWallyHDisplayName.
  3. Case 96. Add a default for getutcdate(). Thanks to mbargar13.
  4. Case 94. Missing "using DatabaseGeneratedOption = System.ComponentModel.DataAnnotations.Schema.DatabaseGeneratedOption;" when targeting Framework 4.5. Thanks toalexdeblasis.
  5. StoredProcedureRename was being ignored. Thanks to slyCzar.
  6. Case 98. Corrected bridge table issue. Thanks to simooo985.

Whats new in v2.10.1:

  1. Stored Procedure arguments that are C# reserved keywords need escaping. Thanks toJimstr.
  2. Make mapping variables consistent during name clashes. An an edge case could cause different names for the reverse navigation as compared to the Map during name clashes. Thanks toFJRodriguez.
  3. Fix indentation when MakeClassesPartial is set.

Whats new in v2.10.0:

  1. Auto Migrations. To enable set MigrationConfigurationFileName to a class name, "MyDbContextDBMigrationConfiguration" for example. This enabled Entity Framework to update the schema when it is deployed in production. Thanks toFJRodriguez.
  2. Remove use of uses_native_compilation column in Stored Procedure SQL to support older database (< 2014). Thanks toNicholas Head.

Whats new in v2.9.1:

  1. GetSqlDbType was missing some types (nvarchar, and uniqueidentifier). Thanks toWally.
  2. Add in "using System.Linq" if Elements.StoredProcedures declared and not Elements.Context. Thanks toWally.

Whats new in v2.9.0:

  1. Stored procedure support !
    • This includes the ability to retrieve the RESULT from stored procs, as well as the data. A result of 0 means success, any other value is an error.
    • Include stubs for the stored procs in the FakeDbContext.
  2. Sort contents of HasForeignKey(...) by foreign key ordinal.
  3. Prevent creating maps where the left and right side of the map are the same table.
  4. Use a try/catch for WCF projects. Thanks to FJRodriguez.
  5. Include examples of CustomPluralizationEntry. Thanks to Carrie Kroutil.
  6. Allow for manual setting of the targeted .Net framework version.

Whats new in v2.8.3:

  1. Added new setting IncludeQueryTraceOn9481Flag so that you are now in control if "OPTION (QUERYTRACEON 9481)" is appended to the SQL. SqlServer 2014 is known to appear frozen / take a long time when this file is saved. If it does, set this to true (however you will also need elevated privileges).
  2. Added new setting DbContextBaseClass. You can now specify what the base class for your DbContext class is. For example ASP.NET Identity use "IdentityDbContext<ApplicationUser>", or even go so far as a custom: IdentityDbContext<CustomUser, CustomRole, int, CustomUserLogin, CustomUserRole, CustomUserClaim>. Thanks toParag Shravagi.
  3. Fixed bug: IndexOutOfRangeException thrown inside GetCurrentProject. Thanks toDavid Gardiner.
    https://efreversepoco.codeplex.com/workitem/85

Whats new in v2.8.2:

  1. This update is required to fix a problem with Sql Server 2014 as it freezes when obtaining the Foreign Keys. See here for more info. The solution was to add OPTION (QUERYTRACEON 9481). Thanks to@ErikEJ for the solution.
    Using this option flag needs a higher SQL privilege, so you may experience:
    User 'Your.Name' does not have permission to run DBCC TRACEON.
    More info (requires sysadmin rights) http://spaghettidba.com/2013/02/08/using-querytraceon-in-plan-guides/ 

Whats new in v2.8.1:

  1. Bug fix: If property had _ appended, and is used as key, it breaks template generation. Thanks toNicholas Head.

Whats new in v2.8.0:

  1. Added a new flag: AddUnitTestingDbContext. If true, this will create a Fake DbContext and a FakeDbSet<T>. This will allow easy unit testing. Can't believe I never added this sooner. See the documentation Unit Testing.

Whats new in v2.7.0:

  1. Fixed bug: Missing schema specification in ManyToMany tables. Thanks to Vtanman & Snajahi.
  2. Add a timeout when obtaining the schema info from a slow database. Thanks to DotNetWise.
  3. Changed table renaming to use a function. Thanks to DotNetWise.

Whats new in v2.6.3:

  1. Add IsUnicode(false) for the char/varchar columns. Thanks to Naomi N.
  2. Rollback a feature added in 2.5.1: For database types such as Numeric(17,0), the C# type should resolve to something in the "int" family. Thanks toSimmered.

Whats new in v2.6.2:

  1. Include another namespace if Target framework is not 4.0. Thanks to NazmulRockOn.
  2. CR/LF in extended properties caused errors. Thanks to Simmered.
  3. Use IsFixedLength() for char/nchar types. Thanks to Naomi N.

Whats new in v2.6.1:

  1. Added the same extended properties comments facility for SQL CE. Thanks to @ErikEJ

Whats new in v2.6.0:

  1. It now reads the extended properties and can add them to the poco classes in comments. See the new IncludeExtendedPropertyComments flag which is an enumeration of
[Flags]
public enum ExtendedPropertyCommentsStyle
{
  None,
  InSummaryBlock,
  AtEndOfField
};
  • ExtendedPropertyCommentsStyle.None: No extended properties are shown.
  • ExtendedPropertyCommentsStyle.InSummaryBlock: extended properties are shown above field in a ///<summary> block.
  • ExtendedPropertyCommentsStyle.AtEndOfField: extended properties are shown at the end of the field in a comment block.

The IncludeComments flag is completely independent to IncludeExtendedPropertyComments.

If you want completely comment free generate code, set IncludeComments = false, and IncludeExtendedPropertyComments = ExtendedPropertyCommentsStyle.None;

Whats new in v2.5.1:

  1. Move the call to tables.SetPrimaryKeys(); higher up. This allows support of tables with no primary keys to be able to be used. Thanks toJaved.
  2. For database types such as Numeric(17,0), the C# type should resolve to something in the "int" family. Thanks tosimmered.

Whats new in v2.5.0:

  1. Added option to strip and alter table names. Such as tblOrders to Orders, AB_Shipments to Shipments, etc. See Table renaming section.
  2. Added ability to switch off the Pluralization service.
  3. Added ability to use other Pluralization services, such as the SpanishPluralizationService as provided in the "EF6.Contrib" Nuget Package. If you are to use the SpanishPluralizationService, add the following to the top of your database.tt file: <#@ assembly name="C:\<Your path here>\packages\EF6.Contrib.1.0.5\lib\net45\EntityFramework.Contrib.dll" #> Changing the path to where your DLL is situated.

Whats new in v2.4.1:

  1.  Fixed bug: When using .HasForeignKey(...) for multi-column keys, the columns should be listed in ordinal order. Thanks toScott Hodges.

Whats new in v2.4.0

  1. Removed use of System.Data.Entity.DLL from the installation template as it is no longer required for EF 6.
  2. Moved spatial types from System.Data.Spatial to System.Data.Entity.Spatial for EF 6.
  3. Singular names and camel casing configuration were accidentally combined by using the UseCamelCase boolean. Thanks toRune Gulbrandsen.
  4. Added new flag IncludeComments. This controls the generation of comments in the output.
  5. Fixed bug in constructor where a UNIQUEIDENTIFIER column had default value. Thanks togonglei.

Whats new in v2.3.2

  1. Singularize one-to-one Reverse Navigation. Thanks to StormRider.
  2. Bugfix for IsRowVersion() for timestamp columns. Thanks to StormRider.
  3. Do not append "m" to decimal value in poco ctor if default contains an unparsable value.

Whats new in v2.3.0:

  1. SQL Server Compact 4.0 support. Thanks to ErikEJ.

Whats new in v2.2.1:

  1. Add strings to be allowed as computed columns. Thanks to JBJBJB and BrhineScot.
  2. Now includes callbacks during code generation. This means you can add attributes to classes, specify a base class, specify custom code within the class, and finally a call back for each column within the class. Thanks toSimplyFoolish. 
  3. OData doesn't support entities with geometery/geography types. Provided a flag to turn these off if entities are being generated from ODATA.  Thanks toSimplyFoolish. Flag is called DisableGeographyTypes.
  4. Fixed bug with the Pluralisation service. If your current culture was not en, then it would throw an exception. Thanks toErikEJ.

Whats new in v2.2.0:

  1. Now uses the .Net Pluralization service. Thanks to James Manning.
  2. Bug fixed when you have foreign keys between two tables where the FK/PK columns have spaces in the column name. Thanks toColin Smith.
  3. Bug fixed. Solution Folders are not searched for config settings. Thanks to scaftw.
  4. Generate navigation property based on FK name. If there are two FK links to a table, the second link would appear as linkName1. This is now detected and both the FK properties will make use of the FK name. If only one FK is used, then the FK name is not appended to the table name. Thanks to saber_solomon.
  5. Sort the generated Reverse navigation and foriegn keys in POCO classes.

Whats new in v2.1.0:

  1. Fixed bug if default constraint was not in expected format. Thanks to Filipe Fujiy.
  2. Now detects name clashes with C# keywords.
  3. Added "System." to DateTime.Now(), etc to prevent clashes with table field names.
  4. "Configuration" class names are now configurable as "Mapping", "Map", etc.
  5. Added support for Spatial.DbGeometry and Spatial.DbGeography. Thanks to Simply Foolish andJorge Bustos.
  6. Can now have custom collection type for Navigation Properties. "ObservableCollection" for example. Thanks to Simply Foolish.

Whats new in v2.0:

  1. Fixed issue when running 'Transform All T4 Templates' from Visual Studio Build Menu.Thanks to JRoselle.
  2. Changing mappings during runtime is not possible/expensive. A specific DbModelBuilder can be used for each needed database schema.Thanks to meixger.
  3. Added ability to detect and use .IsRowVersion().
  4. Added many-to-many mappings. The generated code now includes calls to .Map(). Therefore the generated code will be different to what you had previously in v1 if you have many-to-many table mappings in your database. Hence the revision change to v2.0.0 as I'm using semantic versioning.

Whats new in v1.12:

  1. VARBINARY(MAX) is now correctly assigned to byte[]. Thanks to Luke91577.
  2. Extending partial class support. Allow specification of file extension for partial classes (i.e. ".generated.cs").Thanks to AB_dreeve.
  3. Fixes issues when targeting .NET 4. .NET 4.0 doesn't include the System.ComponentModel.DataAnnotations.Schema namespace, allow specification of TargetFrameworkVersion.Thanks to AB_dreeve.

Whats new in v1.11:

  1. Including views is now working. For a view to be included, at least one column must not be nullable.Thanks to Delmo Carruzzo.
  2. Added selective generation of components (Poco, Context, UnitOfWork, PocoConfiguration). You can now build entities in your Model project, and context, configuration, unit of work in your Data project. Thanks to kscelfo.
  3. Added PrependSchemaName flag. You can now control if the schema name is prepended to the table name. Thanks to kscelfo.

Whats new in v1.10:

  1. Added UseCamelCase flag to the tt file. You can now control if you want your table and column names CamelCase or left alone: i.e. FieldPersonOrder or field_person_order

Whats new in v1.9.2:

  1. Removed the Linq de-duplication code as it is now being done in SQL. The Linq version did not include the schema name when de-duplicating FK's.

Whats new in v1.9.1:

  1. Added DISTICT to the foreign key SQL. This prevents duplicates from appearing.
    They can appear with SQL such as:
    ALTERTABLE [Mars].[Table2] WITHCHECKADDCONSTRAINT [FK_Table2_Table1]
    FOREIGNKEY([Table1Id]) REFERENCES [Mars].[Table1] ([Id])
ALTERTABLE [Mars].[Table2] CHECKCONSTRAINT [FK_Table2_Table1]

Whats new in v1.9.0:

  1. It now has the ability to read connection strings from other config files/projects.
    It starts by looking at the local project for the named connection string in the following files:
    • app.config
    • web.config
    • app.config.transform
    • web.config.transform
    • or edit the above list in the .tt and specify which file(s) to use
    If not found, it then looks for those files in all the projects within the solution.

Whats new in v1.8.0:

  1. Can now optionally generate separate files. See the new boolean flag GenerateSeparateFiles.
  2. Removed the hard coded 300 second timeout. The timeout can be specified in the connection string.

Whats new in v1.7.1:

  1. Add support for DateTime2
  2. Add support for UnitOfWork and the repository pattern. This means you can now unit test your repositories. See the source code for examples.
  3. Add IDisposable to db context.

Whats new in v1.7.0:

  1. Add .HasPrecision(precision, scale) for fields that have scale. Thanks to @choudeshell

Whats new in v1.6.0:

  1. Enhance ReadSchema performance with early table exclusion.
  2. Now supports columns with symbols and punctuation.
  3. Handles decimal default values.

Whats new in v1.5.1:

  1. A bugfix for WCF. See issue https://efreversepoco.codeplex.com/workitem/4

Whats new in v1.5.0:

  1. Ability to add WCF(DataMember, DataContract attributes) support on Entity. Requested by spatemp

Whats new in v1.4.1:

  1. Foreign keys are only included if they point to a primary key.

Whats new in v1.4.0:

  1. If a field has a default contrainst of GetDate(), add DateTime.Now() in the ctor for the field.
  2. Add support for the datetimeoffset type, including support for the default constraint sysdatetimeoffset().
  3. Add Resharper naming comments.
  4. Mappings should be marked internal. Requested by Hobbes Pirakitti
↧
↧

Edited Issue: Stored procedure return column name tidy up could bring all Null value [107]

April 24, 2015, 12:47 pm
$
0
0
EF.Reverse.POCO.Generator has a code snippet to tide up stored procedure's return column name, here is code:

proc.ReturnColumns = ds.Tables[0].Columns.Cast<DataColumn>().ToList();
// Tidy up
foreach (var col in proc.ReturnColumns)
{
col.ColumnName = Regex.Replace(col.ColumnName, @"[^A-Za-z0-9\s]*", "");
col.ColumnName = Inflector.ToTitleCase(col.ColumnName).Replace(" ", "");
}

This could bring an issues that C# code cannot get correct stored procedure query result when column name has underline(s), e.g. if column name is "student_score", after tidy up, in return model class, corresponding property name is "StudentScore", in the list of query result, this property StudentScore is always NULL.
↧

Source code checked in, #53dd84ccd982

April 25, 2015, 7:14 am
↧

Source code checked in, #1d222dffa829

April 25, 2015, 7:14 am
$
0
0
Added tag v2.12.2 for changeset 53dd84ccd982
↧
Viewing all 1642 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>