2.2.104 08-Nov-24
- Supported Visual Studio 2022 version 17.12 Preview
- Fixed an issue with integration in Visual Studio 2015 and earlier versions
Entity Framework support
- Updated support for Entity Framework Core 8 to version 8.0.10
- Updated support for Entity Framework Core 6 to version 6.0.35
Entity Developer
- Fixed an issue where the Update From Database Wizard reset navigation property names in EF Core models
2.2.21 06-Jun-24
Entity Framework support
- Updated support for Entity Framework Core 8 to version 8.0.6
- Updated support for Entity Framework Core 7 to version 7.0.20
- Updated support for Entity Framework Core 6 to version 6.0.31
2.2.20 29-May-24
- Supported Visual Studio 2022 version 17.11 Preview
Entity Framework support
- Updated support for Entity Framework Core 8 to version 8.0.5
- Updated support for Entity Framework Core 7 to version 7.0.19
- Updated support for Entity Framework Core 6 to version 6.0.30
2.1.10 17-Jan-24
- .NET 8 compatibility
- Visual Studio 2022 is supported
- Visual Studio 2022 version 17.9 Preview is supported
Entity Framework support
- Entity Framework Core 8.0.0 is supported
- Entity Framework Core 7.0.14 is supported
- Entity Framework Core 6.0.25 is supported
- The bug with generating literals for constants in LINQ queries in EF Core 2 and higher is fixed
- The bug with throwing the "Unable to resolve service for type TypeMappingSourceDependencies" error by the Scaffold-DbContext command in EF Core 6 and higher is fixed
- The bug with throwing the StackOverflowException in EF Core 6 and higher is fixed
Entity Developer
- EF Core 8 is added to the list of available Entity Framework versions in Create Model Wizard and Model Settings in EF Core Model
- .NET 8 is added to the list of available Target Framework versions in Create Model Wizard and Model Settings in EF and EF Core models
- The new extended property Do Not Generate OnConfiguring Method is added for the model in EF Core Model
- The bug with unnecessary generation of the GetByKey() method in a repository for entities without primary key (QueryType=True) in EF Core is fixed
- The bug with wrongly turned on without the ability to turn off options "Detect Many-to-Many associations" and "Detect Table-Per-Type inheritances" in Model Settings of EF Core 1, 2, 3 models is fixed
- The bug with the availability of the "Table-Per-Type Hierarchy (TPT)" option in the "Model Refactoring" dialog of EF Core 1, 2, 3 models is fixed
- The bug with the availability of the "Table-Per-Concrete-Type Hierarchy (TPC)" option in the "Model Refactoring" dialog of EF Core 1, 2, 3, 5, 6 models is fixed
- The hang of Visual Studio 2022 when saving the model is fixed
2.0.0 16-Nov-23
- .NET Core is supported
- .NET 5, .NET 6, and .NET 7 compatibility
- The NuGet package 'Devart.Data.Sugar' with .NET Core compliant assemblies is uploaded to www.nuget.org
Entity Framework support
- EF Core 5, EF Core 6, and EF Core 7 are supported
- The NuGet package 'Devart.Data.Sugar.EFCore' with .NET Core compliant assemblies is uploaded to www.nuget.org
1.9.1814 01-Jun-23
Entity Developer
- The behavior is changed: the primitive properties by default have Inheritance Modifier = None
- The bug with the detection of non-existent changes while updating a model from a database is fixed
- The bug with missing model context namespace in EntityFrameworkUnitOfWork.cs produced by the Repository And Unit of Work template (C#) in EF Core is fixed
1.9.1797 01-Mar-23
Entity Framework support:
- Entity Framework Core 3.1.32 is supported.
Entity Developer
- The new extended properties Do Not Generate Serializable Attribute and Do Not Serialize are added for complex types in EF Core Model
- The bug with applying the Generate Serializable Attributes and Serialization Library settings of the EF Core template to the generated complex types is fixed
1.9.1796 30-Jun-22
Entity Framework support:
- Entity Framework Core 3.1.25 is supported.
1.9.1579 25-Jan-22
Entity Developer
- The behavior is changed: turning off the "Save connection to" option in Model Settings of EF Core Model wipes out connection string literal from the generated code
1.9.1555 21-Dec-21
Entity Developer
- The model validation is improved: the errors are generated for all entities with QueryType=True in EF Core Model when EF Core version=EF Core 1 in Model Settings
- The bug with wrong automatic assigning QueryType=True for views added to EF Core Model, when EF Core version=EF Core 1 in Model Settings, is fixed
- The bug with throwing System.NullReferenceException when saving the changed value of the "Save connection to" option in Model Settings of EF Core Model is fixed
Entity Framework support
- Entity Framework Core 3.1.22 is supported
1.9.1527 09-Nov-21
Entity Developer
- The bug with parsing discriminator value as string, even when its type is different, in TPH inheritance of EF Core Model is fixed
Entity Framework support
- Entity Framework Core 3.1.21 is supported
1.9.1514 21-Oct-21
- Visual Studio 2019 Preview support is discontinued
Entity Developer
- The bug with launching Entity Developer after applying Windows 10 Update KB5006670 and Windows 11 Update KB5006674 is fixed
Entity Framework support
- Entity Framework Core 3.1.20 is supported
1.9.1498 28-Sep-21
Entity Developer
- The new property Validation Framework is implemented in the Data Transfer Object template for generating DataAnnotations attributes
- The new option "Save connection to" is implemented in Model Settings of EF Core Model to provide the ability to store the connection string in "Model file", "Entity Developer storage", "Environment variable"
- The new option "Enum Output" is added to the EF Core template to specify output for the generated enums
- The new property Generate UnitOfWork Repository Properties (by default, True) is implemented in the Repository and Unit Of Work template of EF Core Model for accessing the collections of entities
- The representation of one-to-one association with non-nullable properties on both ends is changed from 1 -> 1 to 0..1 -> 1 on a diagram in EF Core Model
- The bug throwing "Unknown property 'DoNotSerialize'.", when complex types and VB.NET template are used in EF Core Model, is fixed
- The bug with code generation for the Constrained option of Association Editor in the case of 0..1 -> 1 association in EF Core Model is fixed
Entity Framework support
- Entity Framework Core 3.1.19 is supported
1.9.1457 30-Jul-21
Entity Framework support
- Entity Framework Core 3.1.17 is supported
1.9.1443 08-Jul-21
- Visual Studio 2019 version 16.11 Preview 2.0 is supported
Entity Framework support
- Entity Framework Core 3.1.16 is supported
1.9.1420 03-Jun-21
Entity Developer
- The new extended property Use Generic DbContextOptions Constructor Argument is added to model properties of EF Core Model
- The new extended property Do Not Generate Constructor With DbContextOptions Argument is added to model properties of EF Core Model
- The bug with generating the Equals method for entities with Record Type=True by C# EF Core template is fixed
- The bug with cleaning values of Length and Precision/Scale column's attributes by Update From Database Wizard in EF Core Model is fixed
- The bug with ignoring template's Validation Error Messages values in the generated code, when class property's Validate Expression is initialized and Validate Format is set to a non-default value, is fixed
- The bug with creating app.config in Visual Studio .NET Framework projects, when the "Rewrite connection string during regeneration" option is turned off in Model Settings, is fixed
Entity Framework support
- Entity Framework Core 3.1.15 is supported
- The EF6 provider registration used with .NET Framework compliant assemblies is improved: the [DbConfigurationType(typeof(SugarEntityProviderServicesConfiguration))] attribute set for DbContext descendant allows now calling the DbContext constructor, that accepts a connection string, with no need to register a custom IDbConnectionFactory implementation
1.9.1381 09-Apr-21
Entity Developer
- The new hotkey Alt+E is implemented in Property Editor for opening Column Editor in EF Core Model
- The bug with throwing "bufferAdapter is not a VsTextDocData" when saving a model in .NET Core, .NET Standard, .NET 5, .NET 6 projects of Visual Studio 2019 is fixed
- The bug with missing .NET Framework, .NET Core 1, .NET Core 2 options for the Target Framework property in Model Settings of EF Core Model in a standalone Entity Developer is fixed
- The bug with preserving Target Framework=.NET Framework in Model Settings of EF Core Model in a standalone Entity Developer is fixed
1.9.1375 01-Apr-21
- Visual Studio 2019 version 16.10 Preview is supported
Entity Developer
- The new options "Private setter for store generated properties" and "Constructor parameter" are added to Model Settings in EF Core for controlling visibility of setter for store generated properties
- The new options "Don't show this message again" in the prompt window and "Prompt before generating code when there are model validation warnings" in the menu Options are implemented in a standalone Entity Developer to provide the ability not to stop code generation by warnings
- The new extended property Do Not Generate Default Constructor is added to EF Core Model for model, classes, and complex types
- The new extended property Do Not Generate Mapping is added to EF Core Model for class properties
- The JSON (Newtonsoft.Json, Microsoft.Text.Json) and YAML (YamlDotNet) serializations are supported in EF Core (via EF Core template) and EF6 (via DbContext template):
- The new template property Serialization Library is added for specifying the library used for serialization
- The new template property Serialize Original Column Names is added for controlling the appearance of original column names in serialization
- The new template property Serialize Navigation Properties is added for controlling the appearance of navigation properties in serialization
- The new template property Serialize Null Value is added for managing the behavior of nullable properties
- The new extended property Do Not Serialize is added for properties and navigation properties to exclude them from serialization
- The new extended property Serialization Name is added for properties and navigation properties to set custom names in serialization
- The Data Transfer Object template is improved:
- The new template property Serialization Library is added for specifying library used for serialization, possible values are Data Contract, JSON (Newtonsoft.Json), JSON (Microsoft.Text.Json), YamlDotNet
- The new extended property Do Not Serialize is added for properties and navigation properties to exclude them from serialization
- The new extended property Serialization Name is added for properties and navigation properties to set custom names in serialization
- The behavior is changed: WCF Data Contract Attributes is set to False by default now
- The following properties are marked as obsolete:
- the Generate Data Contracts property of the EF Core template
- the Do Not Generate Data Contract Attribute extended property of navigation properties in EF Core Model
- the WCF Data Contract Attributes property of the DbContext and Data Transfer Object templates
- the WCF DataMember Attribute on Navigation Properties property of the DbContext and Data Transfer Object templates
- The bug with detecting the existing classes with QueryType=True by Update From Database Wizard in EF Core Model is fixed
Entity Framework support
- Entity Framework Core 3.1.13 is supported
- The bug with throwing the "Unexpected symbol 'FETCH'" error when using paging in EF Core 3 is fixed
1.9.1351 18-Feb-21
- The new command line option /disablegac that disables adding assemblies to GAC is added
Entity Developer
- The behavior is changed in Entity Developer embedded into Visual Studio: lower versions in the EF Core version property of Model Settings are not hidden any more
- C# code generation is improved: the using directives are generated instead of full namespaces in the names of attributes for DataAnnotations, NHibernate Validator, and Enterprise Library validation frameworks
- Code generation is improved: OnModelCreating(modelBuilder) of the base class is invoked now if the Base Context Type property of EF Core Model is initialized
Entity Framework support
- Entity Framework Core 3.1.12 is supported
1.9.1327 14-Jan-21
Entity Developer
- The new attribute DisplayName is implemented for model objects' extended properties which are available via template properties
- The new options --ContextNamespace and --DefaultNamespace are added to the Create-Model command of Console Entity Developer
- The new extended model property Base Context Type is added for specifying a parent class for the generated context in EF Core Model
- The new extended properties Base Type for complex types and Base Complex Type for model are implemented in EF Core Model
- The %type name% keyword is supported in the Base Type extended property of entities and complex types, and in Base Complex Type, Base Entity Type, Base Context Type extended model properties for setting generic base type in EF Core Model
- Display names of extended properties in EF Core Model are updated: Entity Base is renamed to Base Type in class properties, Entity Base is renamed to Base Entity Type in model properties, Context Base is renamed to Base Context Type in model properties
- The bug with setting additional keyboard mapping scheme via menu Options on Windows with German display language is fixed
Entity Framework support
- Entity Framework Core 3.1.11 is supported
1.9.1307 17-Dec-20
- Compatible with other dotConnect providers
1.9.1297 03-Dec-20
- Visual Studio 2019 version 16.9 Preview is supported
- The bug with updating projects that reference EF6 provider assembly via Upgrade Wizard is fixed
Entity Developer
- The Model Refactoring functionality is supported for classes in EF Core Model
- The behavior is changed in a standalone Entity Developer: by default the Target Framework model property in EF Core Model is set to .NET 5 instead of .NET Framework
- The bug with saving non-default value of Target Framework model property in EF6 model modified with a standalone Entity Developer is fixed
Entity Framework support
- Entity Framework Core 3.1.10 is supported
- The bug with throwing "MaxLength must be greater than zero" by the code generated with the DbContext template (Fluent Mapping=True) in EF4/EF5/EF6 is fixed
1.9.1274 29-Oct-20
- The bug with Visual Studio 2019 integration, when both v16.7 RTM and v16.8 Preview are installed on the same computer, is fixed
Entity Developer
- The bug with reading templates from *.edps by console Entity Developer is fixed
Entity Framework support
- Entity Framework Core 3.1.9 is supported
1.9.1254 01-Oct-20
- Visual Studio 2019 version 16.8 Preview is supported
Entity Developer
- The bug with throwing "EntityProperty does not contain a definition for IsSpatialType", when custom template from previous versions is used, in EF Core Model is fixed
- The bug with applying On Delete Action=Cascade set in Association Editor to the Generate Database Script functionality in EF Core Model is fixed
- The bug with reading settings from *.edps by console Entity Developer is fixed
1.9.1245 17-Sep-20
- The SendCallStack property is added to the Devart.Common.DbMonitor class for possibility to turn off resource-demanding logging of CallStack
- The Filter property is added to the Devart.Common.DbMonitor class for possibility to choose events being logged
- The Devart.Common.DbMonitor class is improved: now values of the DateTime parameters sent to the dbMonitor tool are supplemented with milliseconds
- The bug with updating projects in folders below the main project by Upgrade Wizard is fixed
Entity Developer
- The error message in console Entity Developer is improved: now the text includes the list of all available templates if the specified name of template was incorrect
- The bug with saving a new model, which has never been saved before, after some time of work in a standalone Entity Developer is fixed
- The bug with generating mapping for the properties with Shadow=True in EF Core Model is fixed
Entity Framework support
- Entity Framework Core 3.1.8 is supported
- The bug with throwing "The method or operation is not implemented." when using the DbContext template / Fluent Mapping=True in EF4/EF6 is fixed
1.9.1211 30-Jul-20
Entity Developer
- The bug with throwing System.NullReferenceException when opening *.edmx with invalid associations is fixed
1.9.1201 16-Jul-20
- The bug with retrieving metadata from the Cases table is fixed
1.9.1181 17-Jun-20
- Visual Studio 2019 version 16.7 Preview is supported
- The bug with retrieving metadata from the Cases table is fixed
Entity Developer
- The new property Collection Property Type is added to EF template "DbContext" and EF Core template "EF Core" to determine .NET type used as a property type for the Many end of associations
- The new property Collection Initialization Type is added to EF template "DbContext" and EF Core template "EF Core" to determine .NET type used for initialization of the Many end of association; if it is set to None, then no initialization is generated
- The new property "Nullable Reference Types" is added to C# templates of EF, EF Core models to specify whether C# 8 nullable reference types and non-nullable reference types must be generated
- The new partial method is added to the OnModelCreating(DbModelBuilder modelBuilder) method generated by DbContext template of EF model
- The EF Core model deserialization is improved: Entity Developer shows the full list of detected errors and tries to load the model with invalid elements or ignores such elements if their deserialization is not possible
- Console Entity Developer improvements:
- The bug with enumerating values separated with comma and without whitespace in --Templates, --Schemas, --Tables parameters is fixed
- The DbProviderFactories registration is implemented in Create Model Wizard for EF6 models and .NET Framework provider assemblies
- The new property Target Framework is added to Create Model Wizard and Model Settings of EF6 models
- The compatibility issue with JetBrains ReSharper is fixed
- The behavior is changed: the definition of auto-implemented property is put now on the single line with
- C# DbContext template of Devart Entity Model when ImplementINotifyPropertyChanging=False and ImplementINotifyPropertyChanged=False and PropertyChangePartialMethods=False
- C# EF Core template of Devart EF Core Model when PropertyChangeNotifiers=False and PropertyChangePartialMethods=False
- The behavior is changed: the names of system types are generated without "System." prefix now in EF Core models; for example, it is DateTime instead of System.DateTime
- The behavior is changed: now the EF Core template generates an additional partial class for the context class when "File Per Class" and "Generate Partial Class" are set to True
- The bug with missing default value in the generated code basing on DEFAULT value in a data, when any of ImplementINotifyPropertyChanging, ImplementINotifyPropertyChanged, PropertyChangePartialMethods options of DbContext template in EF is turned on, is fixed
- The bug with generating .HasMany end of one-to-many association in EF Core Model is fixed
- The bug with generating TPH mapping in EF Core 3 model is fixed
- The bug with false appearing the "Table or view '...' has no primary key columns, and the entity key for the corresponding storage entity was calculated automatically from other fields." warning in the Error List window is fixed
- The bug with generating new Guid() with Primitive Default Value Generation=Literal in EF, EF Core models is fixed
Entity Framework support
- Entity Framework 6.4.4 is supported
- The translation of the DateTime.AddMinutes() method in LINQ query into SQL statement in EF Core is supported
- The bug with adding / subtracting DateTime and TimeSpan, DateTimeOffset and TimeSpan values in LINQ query in EF Core 3 is fixed
1.9.1127 02-Apr-20
- The bug with reading the service_end_date column from the Products table is fixed
Entity Developer
- Command-line interface is implemented in a standalone Entity Developer
- The new property Context Name is added to Model Properties in EF Core Model
- The new property Target Framework is added to Model Properties in EF Core Model
- The provider registration is improved: requirement to put provider registration entry in the config file is not obligatory anymore
- Create Model Wizard is improved: now it allows installing multiple NuGet packages on the final step
- Model file tree in .NET Core / .NET Standard projects is improved: all generated code files and model files are nested under the same node in Solution Explorer
Entity Framework support
- Entity Framework Core 3.1.3 is supported
1.9.1098 20-Feb-20
Entity Developer
- The bug with returning multiple result sets in code generated by the EF Core template is fixed
Entity Framework support
- Entity Framework Core 3.1.1 is supported
1.9.1056 23-Dec-19
- Visual Studio 2019 version 16.5 Preview is supported
Entity Developer
- The behavior is changed: read-only mapping is generated for all columns with UPDATE and without INSERT permissions in data source
- The bug with creating one-to-one association basing on an optional FK in EF Core Model is fixed
- The bug with code generation for oneOrZero-to-one and one-to-many associations based on an optional FK in EF Core Model is fixed
Entity Framework support
- Entity Framework 6.4 is supported
- Entity Framework Core 3.1 is supported
- The new \Entity\EFCore3\Devart.Data.Sugar.Entity.EFCore.dll assembly compiled with EF Core 3.1 and .NET Framework 4.6.1 is added
- The bug with applying .ValueGeneratedOnAdd() to the string, guid, byte[] properties with .Key() and without .HasDefaultValueSql() in EF Core is fixed
1.8.1034 21-Nov-19
Entity Developer
- The Self-Contained Entity Configuration property is added to VB.NET version of EF Core template
- The Entities Configuration Output property is added to VB.NET version of EF Core template
- The code generation for the class properties with Alternate Key=True by VB.NET version of EF Core template is supported in EF Core model
- The bug with code generation, when Raw SQL Query is initialized in class properties, in EF Core 3 model is fixed
- The bug with generating .HasNoKey(), when Self-Contained Entity Configuration is set to True in properties of EF Core template, in EF Core 3 model is fixed
- The bug with generating alternate keys, when Self-Contained Entity Configuration is set to True in C# version of EF Core template, in EF Core model is fixed
1.8.1019 31-Oct-19
- Visual Studio 2019 version 16.4 Preview is supported
Entity Developer
- The bug with throwing the EntityFrameworkCoreVersion error in Create Model Wizard in a standalone Entity Developer is fixed
Entity Framework support
- Entity Framework Core 2.2.6 is supported
1.8.1014 24-Oct-19
Entity Developer
- The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported
- The compatibility issue with JetBrains ReSharper is fixed
1.8.985 12-Sep-19
- The integration with Visual Studio 2019 is improved: now the installation detects both 2019 Release and 2019 Preview versions
Entity Developer
- The behaviour is changed: a plural form of names ending with "s" now has a longer version (for example, status -> statuses)
- The bug with copying a property with Primary Key=True / Entity Key=True to a complex type is fixed
- The bug with naming of a composing unique key by Create Model Wizard / Update From Database Wizard in EF Core is fixed
- The bug with invalid attempt to cast unsupported Visual Studio project to type 'VSLangProj.VSProject' is fixed
Entity Framework support
- The bug with using the same database connection in several EF Core contexts is fixed
- The bug with applying a value converter to .Where expression with .Contains on nullable enum in EF Core 2 is fixed
1.8.952 25-July-19
- Compatible with other dotConnect providers
1.8.937 04-July-19
Entity Developer
- The ability to disable generation of the byte order mark (BOM) in the beginning of code files in a standalone Entity Developer is implemented
- The bug with design time copy/cut/paste functionality for entities is fixed
- The bug with invalid integer to enum conversion by a generated method, which is based on SQL query and returns a collection of entities, in EF Core 2 is fixed
Entity Framework support
- The bug with applying a filter to the nullable property with implicit EnumToStringConverter via LINQ queries in EF Core 2 is fixed
- The bug with missing brackets around SELECT inside the generated CASE statement in EF Core 2 is fixed
- The bug with nullable parameters in EF Core 2 is fixed
- The bug with reopening connections in EF Core 2 is fixed
1.8.917 06-Jun-19
- Deprecated design-time Synchronous API calls are no longer used with Visual Studio 2019 and Visual Studio 2017
Entity Framework support
- Entity Framework Core 2.2.4 is supported
1.8.881 11-Apr-19
- Visual Studio 2019 is supported
1.7.872 28-Mar-19
- Visual Studio 2019 Release Candidate 4 is supported
Entity Framework support
- Entity Framework Core 2.2.3 is supported
1.7.843 14-Feb-19
Entity Developer
- The bug with generating fluent mapping for the one-to-one association by the DbContext template in EF4/EF5/EF6 is fixed
1.7.822 10-Jan-19
Entity Developer
- The multiple select functionality in EF Core Model is improved: now it allows setting PrimaryKey, ValueGenerated, Concurrency for several properties simultaneously
- The bug with using ASP.NET Core Web Application (.NET Framework) and Azure Functions v1 (.NET Framework) projects in Visual Studio 2017 is fixed
Entity Framework support
- Entity Framework Core 2.2.1 is supported
1.7.793 29-Nov-18
Entity Developer
- The new Generate GeneratedCode Attributes option (by default, False) is added to the DbContext template in EF4/EF5/EF6 and the EF Core template
- The new Generate Dummy Comments option (by default, False) is added to the DbContext template in EF4/EF5/EF6
- The code formatting is fixed in the DbContext template in EF4/EF5/EF6 and the EF Core template
- The bug with generating fluent mapping for the TPC inheritance by VB.NET version of DbContext template in EF4/EF5/EF6 is fixed
1.7.768 25-Oct-18
Entity Developer
- The bug with adding references to the provider assemblies when creating Entity Framework models is fixed
Entity Framework support
- Entity Framework Core 2.1.4 is supported
- The bug with throwing "Collection was modified; enumeration operation may not execute" by EF Core provider in multithreaded applications is fixed
1.7.744 20-Sep-18
Entity Developer
- Using an extended property of type OutputInfo is supported
- Code generated for nullable properties is simplified: now T? is generated instead of System.Nullable<T>
- An additional constructor that accepts DbContextOptions as an argument is added to the DbContext class descendant in the VB.NET version of the DbContext template for EF Core
- The bug with "No database provider has been configured for this DbContext." in the DbContext template for EF Core is fixed
- The bug with code generation for nullable properties for EF1/EF4/EF5/EF6 is fixed
Entity Framework support
- Entity Framework Core 2.1.3 is supported
1.7.731 30-Aug-18
Entity Developer
- The bug with setting password as clear text in connection string when "Persist Security Info=False;" is fixed
Entity Framework support
- Entity Framework Core 2.1.2 is supported
1.7.717 09-Aug-18
Entity Framework support
- The behavior is changed: the default value of config.QueryOptions.UseCSharpNullComparisonBehavior is true now in EF Core
- The bug with SQL generation for comparing column with parameter in EF Core 2 is fixed
1.7.705 19-Jul-18
- Compatible with other dotConnect providers
1.7.687 21-Jun-18
Entity Developer
- Entity Framework Core 2.1 is supported
- Query type support is added: classes now have the Query Type property, and if it is set to true, this class is generated as a query type
- Lazy loading for Entity Framework Core 2.1 is supported:
- Model now has the Use Lazy-Loading Proxies property, which enables lazy loading on the model level
- Navigation properties now have the Lazy property, which enables lazy loading for a specific navigation property
- Properties now have the Constructor Parameter property, for configuring a parameterized constructor of the class
- The "Include Environment Variables" property, determining whether context configuration will be extended with environment variables when a connection string from the appsettings.json file is used, is added to the EF Core template
- The "Json File Base Path" property, specifying the base path for file-based providers when a connection string from the appsettings.json file is used, is added to the EF Core template
Entity Framework support
- Entity Framework Core 2.1.1 is supported
1.6.667 24-May-18
Entity Framework support
- Entity Framework Core 1.1.5 is supported
- Entity Framework Core 2.0.3 is supported
1.6.649 27-Apr-18
Entity Developer
- The new Controller Area extended class property is added to EF Core Model
- The check of conditions for setting optionsBuilder.Use... in the generated OnConfiguring method by the EF Core template is improved
1.6.630 29-Mar-18
Entity Developer
- The new SQL Type, Size, Precision, Scale options are added to the Parameters tab in Method Editor of EF Core Model
- The process of synchronizing methods and parameters with database stored procedures in EF Core Model is improved
- The bug with adding entry to appsettings.json, when "Use the following connection string from App.Config" and "Rewrite connection string during regeneration" in Model Settings are turned on, is fixed
- The bug with throwing the "Multiple constructors accepting all given argument types have been found in type '...'. There should only be one applicable constructor." error by the code generated with the MVC Controller template in ASP.NET Core Web Application is fixed
- The bug with missing DataMember attribute on the Many end of an association, when using the EF Core template with "Generate Data Contracts=True", is fixed
- The bug with the Retrieve Data functionality on the base class of TPH inheritance is fixed
- The bug with the Find Next functionality of T4 Editor embedded into Visual Studio is fixed
- The bug with throwing the "IDE not supported" exception by Entity Developer in Visual Studio 2017 of versions 15.6.* is fixed
Entity Framework support
- Entity Framework Core 2.0.2 is supported
1.6.601 15-Feb-18
- The behaviour is changed: now SugarLoader uses Bulk API
Entity Developer
- Support for ASP.NET Core MVC is added to the Data Annotations Metadata template
- The bug with applying the DevartEFCoreGenerator custom tool in Visual Basic .NET Core projects is fixed
1.6.576 11-Jan-18
Entity Developer
- The ModelNameAsFilesPrefix property is implemented in the RepositoryAndUnitOfWork template
- The code generation for async method calls in the EF Core template is improved
- Support for ASP.NET Core MVC is added to the MVC Controller template
Entity Framework support
- Entity Framework Core 1.1.4 is supported
- Entity Framework Core 2.0.1 is supported
1.6.547 23-Nov-17
Entity Developer
- The new "Detect function-based column default value" option is implemented in Model Settings of EF Core model
- The code generation for async method calls is added to the EF Core template
- The usage of long identifiers (up to 140 symbols) for naming model objects is supported
Entity Framework support
- Entity Framework 6.2 is supported
- The bug with using multiple .Include() in EF Core 2 is fixed
- The bug with processing conditions in LINQ queries with joins in EF Core is fixed
1.6.529 30-Oct-17
Entity Developer
- Entity Framework Core 2.0 is supported
- The Retrieve Data functionality via Model Explorer for EF Core 2 is implemented
- The bug with escaping invalid XML characters in the comments generated by templates is fixed
Entity Framework support
- Entity Framework Core 1.1.3 is supported
- Entity Framework Core 2.0 is supported
1.6.496 06-Sep-17
- The integration with Visual Studio 2017 is improved: the installation is now silent, without VSIX Installer prompt window
Entity Developer
- The Devart Visual Studio packages registration into Visual Studio 2017 is improved: the packages are now available for all Windows accounts
- The bug with losing Toolbar and docking customizations of a standalone designer during reinstall is fixed
Entity Framework support
- The bug with using a variable with null value in LINQ query in EF Core is fixed
1.6.474 03-Aug-17
Entity Developer
- The new Raw SQL Query class property and SQL method property with the corresponding editors are implemented in Entity Framework Core
- The bug with generating code for the PropertyChanging event is fixed
- The bug with applying Custom Tool by Devart Entity Model (*.edml) in VS 2017 .NET Core projects is fixed
- The bug with quoting default table and column names in EF Core is fixed
- The bug with registering DevartEntityDeploy on the workstation with just Build Tools for Visual Studio 2017 installed is fixed
Entity Framework support
- The bug with comparison and binary operations in EF Core is fixed
1.6.462 13-Jul-17
Entity Developer
- The behaviour is changed: IsRequired(false / true) for navigation properties is always generated in EF Core fluent mapping now
- The bug with throwing "Can't load provider assembly." by EF6 model in a standalone Entity Developer is fixed
- The bug with serializing user defined extended properties for associations is fixed
- The bug with a Devart provider not found in Entity Developer as a standalone application when the provider is installed without placing Devart assemblies to the GAC is fixed
Entity Framework support
- The bug with ignoring some string columns, which include too big MaxLength value, by EDM Wizard is fixed
1.6.447 22-Jun-17
- The compatibility with Visual Studio 2017 Updates is improved
- The bug with using the 'Do not install assemblies in the GAC' install wizard functionality for Visual Studio 2017 is fixed
Entity Developer
- The bug related to the conflict of Entity Developer with dbForge SQL Complete is fixed
1.6.428 25-May-17
- The bug with previewing a DataSet is fixed
Entity Developer
- The .NET Core projects in Visual Studio 2017 are supported
- The Snake case in both Model and Database naming rules is supported via the new "Add underscore" option
Entity Framework support
- Entity Framework Core 1.1.2 is supported
- The bug with paging in EF Core is fixed
- The bug with using the ForSugarHasColumnName and ForSugarHasColumnType modelBuilder methods with the value-type properties in EF Core is fixed
1.6.378 16-Mar-17
- Visual Studio 2017 is supported
- The Readonly connection string parameter is added to allow only reading source data (only SELECT statements)
Entity Developer
- The bug with generating the virtual keyword when Inheritance Modifier=None is fixed
Entity Framework support
- Entity Framework Core 1.1.1 is supported
1.5.368 02-Mar-17
- Visual Studio 2017 Release Candidate 4 is supported
Entity Developer
- The bug with throwing the "Stack empty" error after stopping validation before code generation in a standalone version is fixed
- The bug with a workability of the "Validate on Build" option in Model Settings is fixed
- The bug with compilation of the EF Core template after copying it to model folder is fixed
1.5.353 09-Feb-17
- Visual Studio 2017 Release Candidate 3 is supported
1.5.348 02-Feb-17
- Compatible with other dotConnect providers
1.5.335 16-Jan-17
- Visual Studio 2017 Release Candidate is supported
1.5.320 22-Dec-16
Entity Framework support
- The bug with grouping by constant expression in EF4/EF5/EF6 when using DevExpress.XtraGrid.GridControl is fixed
1.5.310 08-Dec-16
- The 'Do not install assemblies in the GAC' check box that allows disabling placing the provider assemblies to the GAC is added to the Install Wizard
- The bug with generating an error when using SugarMonitor on Linux is fixed
Entity Developer
- The possibility to choose whether to add new entities to a diagram or not in Update From Database Wizard is implemented
- The behaviour is changed: now the DbContext template generates an additional partial class for the context class when "File Per Class" and "Generate Partial Class" are set to True
Entity Framework support
- Entity Framework Core 1.1.0 is supported
- The Scaffold-DbContext NuGet command of Package Manager Console for generating a model basing on the existing database schema is supported in EF Core
- The bug with boolean literal constants in the generated SQL statements in EF Core is fixed
1.5.279 20-Oct-16
- Compatible with other dotConnect providers
1.5.269 06-Oct-16
Entity Developer
- The generation of static methods by the EntityObject template is supported via the new property Direct Call of EntityMethod
Entity Framework support
- The bug with comparing bool class property with some value in EF Core is fixed
1.5.259 22-Sep-16
Entity Developer
- The bug with moving mapping from abstract base class to child classes of TPH inheritance in the fluent mapping generated by the DbContext template is fixed
Entity Framework support
- Entity Framework Core 1.0.1 is supported
- The bug with processing IN expressions in EF Core is fixed
- The bug with retrieving objects of TPH hierarchy in EF Core is fixed
1.5.245 01-Sep-16
Entity Framework support
- The bug with using the DatabaseFacade.UseTransaction() method in EF Core is fixed
- The bug with nullable parameters in EF Core is fixed
- The bug with throwing System.NullReferenceException when using TPH inheritance in EF Core is fixed
- The bug with not throwing concurrency check exception on invoking DbContext.SaveChangesAsync() is fixed
1.5.230 11-Aug-16
Entity Developer
- The bug with setting value of the Value Generated property attribute in the EF Core model is fixed
Entity Framework support
- The bug with executing the UseSugar(DbConnection connection) extension method of DbContextOptionsBuilder in EF Core is fixed
- The bug with using the DbContext(DbConnection connection) overload in EF Core is fixed
- The bug with using EF Core logging is fixed
- The bug with using enum values in EF Core is fixed
- The bug with throwing DbUpdateConcurrencyException in EF Core is fixed
- The bug with using comparisons in LINQ queries in EF Core is fixed
1.5.215 21-Jul-16
Entity Framework support
- The bug with convertation of enum values in parameters when using EF Core is fixed
1.5.205 07-Jul-16
Entity Developer
- Entity Framework Core 1.0 RTM is supported
- The possibility to set values of stored procedure parameters for getting metadata to generate automatically the corresponding complex type is implemented
- The behaviour is changed: the ObservableCollection navigation properties are initialized now in a default class constructor
Entity Framework support
- Entity Framework Core 1.0 RTM is supported
1.5.195 23-Jun-16
- Compatible with other dotConnect providers
1.5.185 09-Jun-16
- Compatible with other dotConnect providers
1.5.176 26-May-16
Entity Developer
- Entity Framework Core support is added
- The DbProviderFactory provider registration in application's *.config is supported by the Entity Developer version integrated into Visual Studio
Entity Framework support
- Entity Framework Core RC2 is supported
1.5.167 12-May-16
- Compatible with other dotConnect providers
1.5.162 05-May-16
Entity Framework support
- Upgrade Wizard is improved for upgrading projects with the Entity Framework functionality
1.5.157 21-Apr-16
- The Run Once Command connection string parameter, which specifies a command to execute when the connection is opened the first time and not executed when the connection is taken from the pool, is added
- The new LoadTable overloads for loading data from a IDataReader, array of rows, or only rows with a specific RowState from a DataTable are added to the SugarLoader class
Entity Framework Support
- Entity Framework Core RC1 is supported
- Entity Framework-related assemblies are renamed
1.00.134 17-Mar-16
- Compatible with other dotConnect providers
1.00.119 25-Feb-16
- First release of dotConnect for SugarCRM data provider
© 2015-2024 Devart. All rights reserved.