v1.8.3: UI for client-side data-traffic analysis

10/10/2012 - Marco (updated on 9/18/2020)

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.


  • Improved registration for remotable methods (now uses a single interface and implementations are integrated with the service locator, as shown below)
  • Many updates to the standard MVC UI
  • Included a binary payload format for the remoting data-handler
  • Improved support for multiple data sources
  • Added support for VS2012 in all projects and build files
  • Improved console migrator with more options for integration into a build server
  • Improved base NAnt support
  • Includes spell-checking support for DevExpress Winform applications
  • Includes DevExpress Winform UI for viewing live database statistics

Breaking changes

  • The DocumentLibrary and IContentRegistry have been moved to the Documents namespace.
  • The ReportsModule.DocumentLibrary no longer exists; instead, access it via the service locator with ServiceLocator.Current.GetInstance<IDocumentLibrary>(). Also the return type is an interface rather than the class itself, but the interface is unchanged.
  • The DocumentBase constructor now takes an IDocumentLibraryProvider instead of a DocumentLibraryProvider
  • The DocumentLibraryProvider is now called DocumentLibraryProviderBase and the constructor no longer requires an IDocumentLibrary.
  • Since the DocumentLibraryProvider no longer has a DocumentLibrary as a constructor parameter, it is no longer auto-registered. Instead, simply get the document library via the service locator (as shown above) and add it to the providers list manually.
  • ViewClassAspect no longer exists; instead, use ViewIconAspect or ViewDynamicIconAspect.
  • The Credentials class is now abstract; instead, use UserCredentials
  • The Encodo.Quino.Data.Persistence.Connections no longer exists; simply remove the using statement as it only included obsolete or internal classes and should have been removed in previous versions anyway.
  • The ViewContextHandler now has generic parameters; instead, most usages will be able to simply switch to using the IViewContextHandler interface.MetaBuilderBase.AddMethods no longer accepts client, base and server classes as parameters. Instead, you should register methods via a single interface and register the appropriate implementation in the startup.

For example, to register IDemoMethods, use:


To set up a client to use the appropriate implementation, depending on whether a remoting data driver has been selected, use:

configuration.IntegrateRemotableMethods<IDemoMethods, LocalDemoMethods, RemotableDemoMethods>();

To set up the application server to host these methods, simply register the local version with the service locator, as shown below:

configuration.RegisterSingle<IRemoteMethods, ServerRemoteMethods>();
  • MetaMethodTools.Execute() now requires four arguments because the call target must be included (remoting methods are no longer static).

Sign up for our Newsletter