The summary below describes major new features, items of note and breaking changes. The full list of issues is in the release notes below and is available to those with access to the Encodo issue tracker.
Most of the existing metadata-building API has been deprecrated and replaced with a fluent API that is consistent and highly extensible.
IMetaProperty.Primary
(QNO-5400)IMetaClass.Relations
and IMetaClass.Actions
auto-managed and read-only sequences (QNO-5402, QNO-5400, QNO-5400)IMetaBase.Identifier
to IMetaBase.Name
(QNO-5412)MetaBuilder
along with associated metadata builders and extension methods.GlobalContext
obsolete (QNO-5313)IDataSession
sticky, by default (QNO-5018)IMetaReadable
and IMetaWritable
with IDataObject
(QNO-5429, QNO-5238, QNO-4737, QNO-3043)IDataSession.ActiveDataLanguages
(QNO-5476)GenericObject
(QNO-5583)Encodo.Quino.Builders.Extensions
namespace has been removed. All members were moved to Encodo.Quino.Meta
or Encodo.Quino.Builders
instead.Quino.Meta.Standard
no longer exists and may have to be removed manually if Nuget does not remove it for you.CreateModel()
to MetaBuilderBasedModelBuilderBase
MetaBuilderBasedModelBuilderBase
GetSubModules()
and GetModules()
now returns IMetaModule
instead of IModuleAspect
AddSort()
, AddSortOrderProperty()
, AddEnumeratedClass()
, AddValueListProperty()
all expect a parameter of type IMetaExpressionFactory
or IExpressionConstants
now.IDataSessionAwareList
is used instead of IMetaAwareList
DataList
have been made privateGenericObject.DoSetDedicatedSession()
is no longer called or overridableAuthenticatorBase
accept an IApplication
as constructor parameters anymore. Instead, use the Application or Session to create the authenticator with GetInstance<TService>()
. E.g. if before you created a TokenAuthenticator
with this call, new TokenAuthenticator(Application)
, you should now create the TokenAuthenticator
with Application.GetInstance<TokenAuthenticator>()
. You are free also to call the new constructor directly, but construction using the IOC is strongly recommended.DataSession
has changed; this shouldn't cause too many problems as applications should be using the IDataSessionFactory
to construct instances anyway.IDataGenerator
interface instead of using the DataGenerator
base class.ISchemaDifference
have changed, so the output of a migration plan will also be different. Software that depended on scraping the plan to determine outcomes may no longer work.NULL
-constraint violation will be thrown by the database. Existing applications will have to be updated: either set a default value in the metadata or set the property value before saving objects.SetCodeGenerated()
on the multi-language or value-list propertyLanguageTools.GetCaption()
no longer defaults to GetDescription()
because this is hardly ever what you wanted to happen.CaptionExtensions
are now in CaptionTools
and are no longer extension methods on object
.ReflectionExtensions
are now in ReflectionTools
and are also no longer extension methods on object
.Operation<>
with new method signatureSome Windows-specific functionality has been moved to new assemblies. These assemblies are automatically included for Winform and WPF applications (as before). Applications that want to use the Windows-specific functionality will have to reference the following packages:
WindowsIdentity
-based code, use the Encodo.Connections.Windows
package and call UseWindowsConnectionServices()
ApplicationSettingsBase
support, use the Encodo.Application.Windows
package and call UseWindowsApplication()
Encodo.Security.Windows
package and call UseWindowsSecurityServices()
.Sign up for our Newsletter
This is my comment
Lasix Ol Comparativa Precio Viagra Generico [url=http://gemeds.com]adn es la kamagra[/url] Amoxicillin 250 5 12 Ml Keflex For Toddler Viagra Sin Receta Espana