The summary below describes major new features, items of note and breaking changes. The full list of issues is also available for those with access to the Encodo issue tracker.
IMetaModule.ClassOptions.OneClassPerFile = truefor those modules where it is desired).
IConstantExpressionno longer exists. Please update method signatures with
Encodo.Quino.Meta.IMetaModuleGeneratorhas been moved to
Encodo.Quino.Tools.ModelGenerators.IMetaModuleGenerator. Fix compile errors by including the new namespace.
MetaBuilderBaseno longer returns
MetaGroupContainer; instead it returns
IMetaGroupContainer. Code that expects the class rather than the interface will have to be updated to use the interface instead.
MetaBuilder.CreateWrapperClass()no longer adds the created class to the model. If this is the desired behavior, use
MetaBuilder.AddWrapperClass()instead. In most cases, the extra class in the model was neither necessary nor desired, but we strongly recommend that you verify your calls to
CreateWrapperClass()to make sure that it still does what you expect.
IMetaMethodImplementationContainerinterface. There is only one method to implement --
SetSession()-- and you can use the
MetaMethodImplementationContainerbase class if you don't have another base class that you want to use. Regenerate code to update the generated class for remotable methods to a version that implements the interface.The generated remote methods can no longer be called without specifying the session to use for the remote-method call. For a given method interface --
IBusinessLogicsay -- instead of calling
ServiceLocator.GetInstance<IBusinessLogic>()to get the instance, use the helper method
For example, in the Quino demo, the call to
DeletePerson used to be:
Instead, you should call:
MetaMethodTools.GetInstance<IBusinessLogicMethods>(person.Session).DeletePerson(person); ```**XML documentation** files are **no longer included** with the **source-only** release. Instead, you should generate the documentation files locally by calling the `deploydoc` target in the `Quino.build` NAnt file. This target can be called at any time to synchronize the XML documentation files with the current sources. For example, when you download the Quino sources (and have NAnt in the system `PATH`), you can execute the following to build & deploy Quino as well as source-code documentation.
nant deploydoc deploy
* As a result of updates made for the model-generation pattern, you will have to re-generate code for your model(s) in order to remove compiler warnings in that code. ------------------------------------------------------------------------ [^1]: Naturally, the Mongo driver can also be used in a distributed solution. It is, as much as possible, a first-class driver for Quino with the following caveats: it supports neither foreign-key constraints nor transactions.
Sign up for our Newsletter