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

Updated Wiki: What's new

$
0
0

Comming in v3.0.0:

  1. Support for any database. MySQL, Oracle, etc. This may take a while...

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

Viewing all articles
Browse latest Browse all 1642

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>