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

Commented Unassigned: Problem generating Stored Procedures [139]

February 10, 2016, 2:21 am
$
0
0
Hi,

I modified the main .tt script in order to have the code generated in separate files and distinct kind of elements separated in folders as described here:

// Elements to generate ***************************************************************************************************************
// Add the elements that should be generated when the template is executed.
// Multiple projects can now be used that separate the different concerns.
ElementsToGenerate = Elements.Poco | Elements.Context | Elements.UnitOfWork | Elements.PocoConfiguration | Elements.StoredProcedures;

// Use these namespaces to specify where the different elements now live. These may even be in different assemblies.
// Please note this does not create the files in these locations, it only adds a using statement to say where they are.
// I show how this works on the video from 26:08 onwards.
// The way to do this is to add the "EntityFramework Reverse POCO Code First Generator" into each of these folders.
// Then set the .tt to only generate the relevant section you need by setting
// ElementsToGenerate = Elements.Poco; in your Entity folder,
// ElementsToGenerate = Elements.Context | Elements.UnitOfWork; in your Context folder,
// ElementsToGenerate = Elements.PocoConfiguration; in your Maps folder.
// PocoNamespace = "YourProject.Entities";
// ContextNamespace = "YourProject.Context";
// UnitOfWorkNamespace = "YourProject.Context";
// PocoConfigurationNamespace = "YourProject.Maps";
// You also need to set the following to the namespace where they now live:
PocoNamespace = "";
ContextNamespace = "";
UnitOfWorkNamespace = "";
PocoConfigurationNamespace = "";


So far it works pretty well, but the stored procedures only get generated if I include them in the "Context" folder. It would be nice to have them in another folder called "StoredProcs", together with the return models. It looks like to have them in another folder requires two (possibly clashing) MyDBContext files.

Is it posible to do this ?? Is it possible to have the stored proc calls each in a separate class file ??

Thanks,

Daniel

Comments: I have changed the stored proc generation to be a boolean value now. Which makes much more sense.
↧
Search

Edited Feature: Problem generating Stored Procedures [139]

February 10, 2016, 2:22 am
$
0
0
Hi,

I modified the main .tt script in order to have the code generated in separate files and distinct kind of elements separated in folders as described here:

// Elements to generate ***************************************************************************************************************
// Add the elements that should be generated when the template is executed.
// Multiple projects can now be used that separate the different concerns.
ElementsToGenerate = Elements.Poco | Elements.Context | Elements.UnitOfWork | Elements.PocoConfiguration | Elements.StoredProcedures;

// Use these namespaces to specify where the different elements now live. These may even be in different assemblies.
// Please note this does not create the files in these locations, it only adds a using statement to say where they are.
// I show how this works on the video from 26:08 onwards.
// The way to do this is to add the "EntityFramework Reverse POCO Code First Generator" into each of these folders.
// Then set the .tt to only generate the relevant section you need by setting
// ElementsToGenerate = Elements.Poco; in your Entity folder,
// ElementsToGenerate = Elements.Context | Elements.UnitOfWork; in your Context folder,
// ElementsToGenerate = Elements.PocoConfiguration; in your Maps folder.
// PocoNamespace = "YourProject.Entities";
// ContextNamespace = "YourProject.Context";
// UnitOfWorkNamespace = "YourProject.Context";
// PocoConfigurationNamespace = "YourProject.Maps";
// You also need to set the following to the namespace where they now live:
PocoNamespace = "";
ContextNamespace = "";
UnitOfWorkNamespace = "";
PocoConfigurationNamespace = "";


So far it works pretty well, but the stored procedures only get generated if I include them in the "Context" folder. It would be nice to have them in another folder called "StoredProcs", together with the return models. It looks like to have them in another folder requires two (possibly clashing) MyDBContext files.

Is it posible to do this ?? Is it possible to have the stored proc calls each in a separate class file ??

Thanks,

Daniel

↧
↧

Commented Feature: Support other database, such as MySQL, Oracle, etc [57]

February 10, 2016, 2:23 am
$
0
0
Make use of the EF schema reader to obtain the schema from other databases such as MySQL, etc.
Comments: Note to self: The Scaffold-DbContext command calls DatabaseOperations.ReverseEngineerAsync() in Microsoft.EntityFrameworkCore.Commands.dll
↧

Commented Unassigned: user defined table types for stored procedures are not supported [147]

February 10, 2016, 12:41 pm
$
0
0

see discussion at :

https://efreversepoco.codeplex.com/discussions/645780


Comments: The latest version broke the table type stuff for me v2.18.0 I now get sql errors like : The table type parameter '@tb_samples' must have a valid type name. The table type parameter '@tb_sites' must have a valid type name. old ``` public int p_UpdateTrend(DataTable tb_samples) { var tb_samplesParam = new SqlParameter { ParameterName = "@tb_samples", SqlDbType = SqlDbType.Structured, Direction = ParameterDirection.Input, Value = tb_samples, TypeName = "dbo.tb_samples_type" }; if (tb_samplesParam.Value == null) tb_samplesParam.Value = DBNull.Value; var procResultParam = new SqlParameter { ParameterName = "@procResult", SqlDbType = SqlDbType.Int, Direction = ParameterDirection.Output }; Database.ExecuteSqlCommand("EXEC @procResult = [dbo].[p_UpdateTrend] @tb_samples", tb_samplesParam, procResultParam); return (int) procResultParam.Value; } ``` new ''' public int p_UpdateTrend(System.Data.DataTable tbsamples) { var tbsamplesParam = new System.Data.SqlClient.SqlParameter { ParameterName = "@tb_samples", SqlDbType = System.Data.SqlDbType.Structured, Direction = System.Data.ParameterDirection.Input, Value = tbsamples }; if (tbsamplesParam.Value == null) tbsamplesParam.Value = System.DBNull.Value; var procResultParam = new System.Data.SqlClient.SqlParameter { ParameterName = "@procResult", SqlDbType = System.Data.SqlDbType.Int, Direction = System.Data.ParameterDirection.Output }; Database.ExecuteSqlCommand("EXEC @procResult = [dbo].[p_UpdateTrend] @tb_samples", tbsamplesParam, procResultParam); return (int) procResultParam.Value; } ''' I see that this bit is missing in the new version : TypeName = "dbo.tb_samples_type"
↧

Reopened Unassigned: user defined table types for stored procedures are not supported [147]

February 10, 2016, 12:41 pm
$
0
0

see discussion at :

https://efreversepoco.codeplex.com/discussions/645780


↧
↧

New Post: table specifies primary key different from base table

February 10, 2016, 2:50 pm
$
0
0
Simon:

I truly appreciate you taking the time to reply to both my posts.

My superiors have reviewed the mechanics of making this transition and decided the life of the project does not justify moving forward. The various customizations required to make this work, while not complex, certainly result in "tricks" being distributed between the template and core files thus complicating future maintenance.

I enjoyed investigating you tool.

Thank you,
jeff
↧

Created Unassigned: Stored procedure with only one result set generates multiple resultsets class. [179]

February 11, 2016, 12:41 am
$
0
0
First of all I'd like to say this POCO generator is a great tool. Really good job.
I'm using version 2.18.0 and I have found little bug.
I have stored procedure that returns only one resultset. It looks for example like this:

```
CREATE PROCEDURE [tst].[SP_Test]
@par int;

AS

BEGIN
IF (@par > 10000)
BEGIN
SELECT
UIC
, TITLE
FROM [tst].[SomeTbl1]
WHERE [TYPE] IN ('T1', 'T3')
ORDER BY HIERARCHY
END
ELSE BEGIN
SELECT
UIC
, TITLE
FROM [tst].[SomeTbl2]
WHERE [TYPE] IN ('T4', 'T5')
ORDER BY HIERARCHY
END
END
```

But generated class for this stored procedure looks like this:

```
public partial class SP_Test
{
public class ResultSetModel1
{
public System.String UIC { get; set; }
public System.String TITLE { get; set; }
}
public System.Collections.Generic.List<ResultSetModel1> ResultSet1;

public class ResultSetModel2
{
public System.String UIC { get; set; }
public System.String TITLE { get; set; }
}
public System.Collections.Generic.List<ResultSetModel2> ResultSet2;
}
```

I found some walkaround. I declare another table (@tbl) and make selection to this table.
At the end I make final selection right from this table.
It looks like this:

```
ALTER PROCEDURE [prrn].[prrn_get_Test]
@par int;

AS

BEGIN
DECLARE @tbl table (UIC int, TITLE nvarchar(500))

IF (@par > 10000)
BEGIN
INSERT INTO @tbl
SELECT
UIC
, TITLE
FROM [tst].[SomeTbl1]
WHERE [TYPE] IN ('T1', 'T3')
ORDER BY HIERARCHY
END
ELSE BEGIN
INSERT INTO @tbl
SELECT
UIC
, TITLE
FROM [tst].[SomeTbl2]
WHERE [TYPE] IN ('T4', 'T5')
ORDER BY HIERARCHY
END

SELECT *
FROM @tbl
END
```

And this walkaround generates class which is perfectly ok.
It looks like this:

```
public partial class SP_Test
{
public System.Int32? UIC { get; set; }
public System.String TITLE { get; set; }
}
```

But It's a little bit ugly, hacky way.
↧

Commented Unassigned: user defined table types for stored procedures are not supported [147]

February 11, 2016, 1:24 am
$
0
0

see discussion at :

https://efreversepoco.codeplex.com/discussions/645780


Comments: Whoops! Thanks for spotting this.
↧
Search

Commented Unassigned: user defined table types for stored procedures are not supported [147]

February 11, 2016, 6:15 am
$
0
0

see discussion at :

https://efreversepoco.codeplex.com/discussions/645780


Comments: See if this [changeset](https://efreversepoco.codeplex.com/SourceControl/changeset/a9a0f8487ae5) works ok now. If it does, I'll create another release to fix this bug.
↧
↧

Commented Unassigned: user defined table types for stored procedures are not supported [147]

February 11, 2016, 7:31 am
$
0
0

see discussion at :

https://efreversepoco.codeplex.com/discussions/645780


Comments: Thanks! that fixes the problem
↧

Commented Unassigned: user defined table types for stored procedures are not supported [147]

February 11, 2016, 9:47 am
$
0
0

see discussion at :

https://efreversepoco.codeplex.com/discussions/645780


Comments: Brill. I'll make a release.
↧

Updated Wiki: What's new

February 11, 2016, 9:49 am
$
0
0

Whats coming in the next major release:

  1. Data Annotations.

Whats new in v2.18.1:

  1. Minor bug fix for case 147 regarding user defined table types and stored procedures. Thanks tomhwlng

Whats new in v2.18.0:

  1. Case 158. Use correct case for table alias in case of case sensitive collation setting on database. Thanks toLuoti.
  2. Use an @ Symbol if default constraint contains a new line character.
  3. Case 173. ReadStoredProcReturnObject throws an exception if a parameter contains a user defined type. Thanks toAndyGJP.
  4. Case 177. bit with string as default value always returns true. Thanks to thbaan.
  5. Case 176. Adding Visual Studio Installer Setup Project to Solution causes issues. Thanks tobbieb.
  6. Case 174 Using DB "newsequentialid()" to help with indexing. Thanks to mbargar13.
  7. Remove Elements.StoredProcedures enum, and replace it with IncludeStoredProcedures boolean flag.
  8. Case 172. Minimise usings to the bare minimum required.
  9. Case 169. WCF flag does not add [DataContract] and [DataMember] to stored proc return model. Thanks toDontEatYellowSnow.

Whats new in v2.17.2:

  1. Regex schema filtering.
  2. Case 166. Remove "Elements.StoredProcedures" causes build errors. Thanks to bbieb.
  3. Support for HierarchyId.
  4. Prevent the use of tables which contain periods '.' as these are invalid within entity framework.
  5. Case 167. Fix ColumnFilter fully qualified name check is schema.table.columnName. Thanks toAndyGJP.

Whats new in v2.17.1:

  1. Case 162. Still using Async if TargetFrameworkVersion = "4.0". Thanks to cowpy520.
  2. Case 163. Handle views and table names with periods. Thanks to flodpanter.
  3. Changed NotNullable to be List<string> and include object. Thanks to philboyd.
  4. Include System.Collections.Generic if generating stored procedures.
  5. Finally sorted out Stored Procedure generation. You can now split out the interface/context/poco's with included stored procedures.
    For example, if you had 4 separate projects (extreme example) you can generate these with:
    • Configuration project: ElementsToGenerate = Elements.PocoConfiguration;
    • Context project: ElementsToGenerate = Elements.Context | Elements.StoredProcedures;
    • Entities project: ElementsToGenerate = Elements.Poco | Elements.StoredProcedures;
    • Interface project: ElementsToGenerate = Elements.UnitOfWork | Elements.StoredProcedures;

Whats new in v2.17.0:

  1. Case 156. Should get null instead of "NULL" for varchar DEFAULT NULL. Thanks toyyjdelete.
  2. Case 147: Add support for stored procedure user defined types. Thanks to mhwlng and Mathias.
  3. Add Find and FindAsync methods to FakeDbSet. Thanks to SoichiSaito.
  4. Changed the default for the IncludeExtendedPropertyComments to be InSummaryBlock so that if extended properties are present in the database, they provide intellisense for you.

Whats new in v2.16.1:

  1. Allow ColumnFilterExclude to target a specific Table.Schema.Column by including escaped dots in regex:
    "^Table\.dbo\.column$". Thanks to Paul Lively.
  2. Added support for EF6 Migration ContextKey. Thanks to ac_4.
  3. Case 154. Add precision and scale when using numeric parameters for stored procedures. Thanks to0v3rCl0ck.
  4. Case 148: No new line after each property "public DbSet" in DbContext. Thanks tosankan1gb.

Whats new in v2.16.0:

  1. Case 130. A new exciting feature: Support for multiple result sets returned from stored procedures.
  2. Fix bug: Stored Procedure with Nullable DateTime2 has invalid cast. Thanks toNeal Culiner.
  3. Mapping tables cannot include spaces in their name, so make them a regular table. Thanks toAndrey Stepanov Pro-Log.
  4. Made it possible to create a many-to-many relationship with the same table on each side. Thanks to Jon Califf.
  5. Case 151. ZapPassword doesn't replace passwords that don't have a trailing semicolon. Thanks toBrad Westness.
  6. Do not include excluded columns in POCO constructor. Thanks to Bacchus.
  7. Case 127. Fix bug where @ was removed from stored proc C# reserved word parameter. Thanks topinger.
  8. Case 144. Code clean up and bug fix. Thanks to jeffinflection.
  9. Better handling for property name clashes in columns. E.g. [user_id], [UserId], [user id] would all map to UserId
  10. Implemened fake functionality for SaveChangesAsync()
  11. Case 140. Include <auto-generated /> in the generated code when outputting separate files. Thanks toNeilCross andGeoArion.
  12. Case 53. Ignore read-only columns for determining mapping tables. Thanks to rvlieshout andpaultjls.
  13. Custom data annotations for ReverseNavigationProperty and ForeignKeys. Thanks toPetrettoS
  14. Corrected indent formatting of output

Whats new in v2.15.2:

  1. Make the FakeMyDbContext partial when MakeClassesPartial = true. Thanks to Police Officer.
  2. Case 140. Include <auto-generated /> in the generated code. Thanks to NeilCross andGeoArion.
  3. Case 142. Handle composite foreign keys. Thanks to GeoArion.
  4. Case 143. Add use of [DbFunctionDetails] attribute to specify schema name for TVF functions. Thanks tooatley.

Whats new in v2.15.1:

  1. Fix bug with stored procedure nullable parameters. Thanks to DannyGB.

Whats new in v2.15.0:

  1. For NTEXT fields, use .IsMaxLength(). Thanks to lucwuyts.
  2. Pass in false for the isFake parameter to WriteStoredProcFunctionSetSqlParameters when not generating a fake. Thanks toSur1969333.
  3. Ignore defaults we cannot interpret, such as "CREATE DEFAULT ..." (we would need SQL to C# compiler). Thanks tobooler.
  4. Case 133. Use full path for System.Threading.Tasks.Task to avoid clashes with table name 'Task'. Thanks toDominikDito.
  5. Case 89. Use DbSet instead of IDbSet. Thanks to 0v3rCl0ck.

Whats new in v2.14.3:

  1. Pluralize / Singularize just the last word if separated by underscore (schema_table) . Thanks toPetrettoS.
  2. Case 129. The Copyright use Western European Encoding for non-ascii char '©', and can not be recognized on other Encoding. I changed the copyright symbol to plain text. Thanks toyyjdelete.
    Copyright symbol
  3. Include schema name for enum definitions. Thanks to TheEdge3.
  4. Include .HasColumnType("sql type") in the configuration mappings. Thanks to lucwuyts.
  5. Added a parameterless constructor for the EntityTypeConfiguration classes. This is useful when you use your own context and use something likemodelBuilder.Configurations.AddFromAssembly(Assembly.GetExecutingAssembly()); when creating the model. Thanks tolucwuyts.
  6. If MakeClassesPartial=true, include a ctor even if there is no ICollection to initialise, so the call is made to InitializePartial();. Thanks tolucwuyts.

Whats new in v2.14.2:

  1. Case 128. Fixed Many-to-Many mapping for tables in different schemas. Thanks tocjmorelock.
  2. Include System.Data.SqlTypes if generating stored procedures as it's required for the INullable interface.

Whats new in v2.14.1:

  1. Handle stored procedure DBNull parameters. Thanks to rorourke.
  2. Handle stored procedure DBNull return values.
  3. Remove property restriction for HasDatabaseGeneratedOption. Thanks to fjrodriguez.

Whats new in v2.14.0:

  1. Handle a string default using the SPACE() keyword. Thanks to BBauer42.
  2. Case 125. Enable Computed Columns for type bool. Thanks to d1ner.
  3. Override Stored Procedure Return Types. Thanks to Leonard Lobel.
  4. Overloaded Stored Procedure Methods without procResult Output Parameter. Thanks toLeonard Lobel.
  5. Add enum property types support for columns. Thanks to Leonard Lobel.
  6. Added support for Azure databases. If the database is Azure, then sys.extended_properties is not used.
  7. Added support for Table Valued Functions. Thanks to Leonard Lobel. See the new variableIncludeTableValuedFunctions.
    The generator now produces strongly-typed wrappers for making TVF calls. They surface very much like stored procedures in the context, but the wrapper methods are implemented quite differently.
    Like stored procs, TVFs can be parameterized and can encapsulate custom server-side logic. But TVFs are alsocomposable, while stored procs aren’t. Meaning a LINQ query against a stored proc executes the where clause of the LINQ query on the client, whereas a LINQ query against a TVF translates the where clause of the LINQ query into a WHERE clause in T-SQL to run on the server.
    If the stored proc has a WHERE clause, then that will be executed on the server, but will then get filtered down further on the client, meaning that unneeded data was returned from the server. If the TVF has a WHERE clause, then that will also be executed on the server, but it will then get filtered down even further on the server with an “outer” WHERE clause generated by EF, meaning that no unneeded data gets returned from the server.
    If you want to use this new feature, you must also install the EntityFramework.CodeFirstStoreFunctions Nuget Package created byPawel Kadluczka (moozzyk) ex-EF team at Microsoft. Source code and documentation is herecodefirstfunctions.codeplex.com.
  8. Handle table names with underscores - singularise just the last word. i.e. Handle table names such as "IMPORTANT_THINGS" and just singuarlise the last 'word' to "ImportantThing". Thanks toDavid Gardiner.
  9. Added full namespace to database static initializer line to prevent some users experiencing compiler errors. Thanks toPaul McIlreavy.

Whats new in v2.13.1:

  1. Case 122. Bug Fix. Make use of the PrimaryKeyOrdinal for sorting when generating primary keys. Thanks tosamiljan.
  2. Fixed bug. In cases where a column had multiple foreign keys, only one foreign key was used. Thanks toChristopher Stamm.

Whats new in v2.13.0:

  1. { get; internal set; } for stored generated fields has been changed to { get; set; }. In some situations you may want to assign it manually, and another when serializing across a WCF service. The ID is lost when serializing because it was marked internal. Thanks to fjrodriguez.
  2. Bug fix: Exception was thrown when culture specific decimal separator was not '.'. Thanks toAndrew A. Evdokimov.
  3. Added the ability to specify base interfaces for the database context interface. See DbContextInterfaceBaseClasses. Thanks toDannyGB.
  4. Check for not nullable stored procedure parameters, such as string and byte[].

Whats new in v2.12.3:

  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.
  7. Case 110. Do not remove stored procedure where it has no return fields. Thanks toemdadgar2.

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
↧

Released: V2.18.1 (Feb 09, 2016)

February 11, 2016, 9:59 am
$
0
0
Whats new in v2.18.1:
  1. Case 158. Use correct case for table alias in case of case sensitive collation setting on database. Thanks to Luoti.
  2. Use an @ Symbol if default constraint contains a new line character.
  3. Case 173. ReadStoredProcReturnObject throws an exception if a parameter contains a user defined type. Thanks to AndyGJP.
  4. Case 177. bit with string as default value always returns true. Thanks to thbaan.
  5. Case 176. Adding Visual Studio Installer Setup Project to Solution causes issues. Thanks to bbieb.
  6. Case 174 Using DB "newsequentialid()" to help with indexing. Thanks to mbargar13.
  7. Remove Elements.StoredProcedures enum, and replace it with IncludeStoredProcedures boolean flag.
  8. Case 172. Minimise usings to the bare minimum required.
  9. Case 169. WCF flag does not add DataContract and DataMember to stored proc return model. Thanks to DontEatYellowSnow.
↧
↧

Updated Release: V2.18.1 (Feb 09, 2016)

February 11, 2016, 9:59 am
$
0
0
Whats new in v2.18.1:
  1. Case 158. Use correct case for table alias in case of case sensitive collation setting on database. Thanks to Luoti.
  2. Use an @ Symbol if default constraint contains a new line character.
  3. Case 173. ReadStoredProcReturnObject throws an exception if a parameter contains a user defined type. Thanks to AndyGJP.
  4. Case 177. bit with string as default value always returns true. Thanks to thbaan.
  5. Case 176. Adding Visual Studio Installer Setup Project to Solution causes issues. Thanks to bbieb.
  6. Case 174 Using DB "newsequentialid()" to help with indexing. Thanks to mbargar13.
  7. Remove Elements.StoredProcedures enum, and replace it with IncludeStoredProcedures boolean flag.
  8. Case 172. Minimise usings to the bare minimum required.
  9. Case 169. WCF flag does not add DataContract and DataMember to stored proc return model. Thanks to DontEatYellowSnow.
↧

Closed Unassigned: user defined table types for stored procedures are not supported [147]

February 11, 2016, 10:01 am
$
0
0

see discussion at :

https://efreversepoco.codeplex.com/discussions/645780


Comments: Released in v2.18.1. Thanks for all your help!
↧
Search

Source code checked in, #a9a0f8487ae5

February 11, 2016, 6:14 am
$
0
0
Case 147. Fixed bug introduced in v2.18.0. datatable is now system.data.datatable. Thanks to mhwlng.
↧

Source code checked in, #876ace6ae70c

February 11, 2016, 9:58 am
↧
↧

Source code checked in, #c75367b943b3

February 11, 2016, 9:58 am
$
0
0
Added tag v2.18.1 for changeset 876ace6ae70c
↧

Created Unassigned: Same stored procedure name on different schema generates only one method with duplicated parameters [180]

February 12, 2016, 3:48 am
$
0
0
Let's say you have three stored procedure with the same name on different schema and one parameter:

```
Alpha.proc_DoSomething @Parameter datetime
Beta.proc_DoSomething @Parameter datetime
Omega.proc_DoSomething @Parameter datetime
```

Only one method is generated prepending the first schema name, and adding three parameters instead of one:

```
int Alpha_ProcDoSomething(System.DateTime? parameter, System.DateTime? parameter, System.DateTime? parameter);
```

Of course this won't compile, and you don't have all the methods you need.

Expected result:

```
int Alpha_ProcDoSomething(System.DateTime? parameter);

int Beta_ProcDoSomething(System.DateTime? parameter);

int Gamma_ProcDoSomething(System.DateTime? parameter);
```

I suspect the problem is on a query while retrieving the metadata.
↧

Edited Issue: Same stored procedure name on different schema generates only one method with duplicated parameters [180]

February 14, 2016, 9:57 am
$
0
0
Let's say you have three stored procedure with the same name on different schema and one parameter:

```
Alpha.proc_DoSomething @Parameter datetime
Beta.proc_DoSomething @Parameter datetime
Omega.proc_DoSomething @Parameter datetime
```

Only one method is generated prepending the first schema name, and adding three parameters instead of one:

```
int Alpha_ProcDoSomething(System.DateTime? parameter, System.DateTime? parameter, System.DateTime? parameter);
```

Of course this won't compile, and you don't have all the methods you need.

Expected result:

```
int Alpha_ProcDoSomething(System.DateTime? parameter);

int Beta_ProcDoSomething(System.DateTime? parameter);

int Gamma_ProcDoSomething(System.DateTime? parameter);
```

I suspect the problem is on a query while retrieving the metadata.
↧
Viewing all 1642 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>