CodeFluent Importer Wizard Update
Last week we released a new version of CodeFluent Entities (645) which is available to developers through the licensing client (SoftFluent.Licensing.Client.exe) and besides miscellaneous updates and fixes this new version contains an updated version of the Import Wizard (see this post for an overview, and this one for a demo).
The box hasn’t changed but there’s plenty more inside in this new version
First, let’s do a quick recap’. The import feature in CodeFluent Entities is 5 or 6 years old and at the time there were no Visual Studio integrated UI, actually there were no UI period: developers had to use (and still can) the CodeFluent.Importer.exe which is shipped along with the Modeler edition (i.e. VS integrated) and Core edition (i.e. command line).
The CodeFluent Importer program takes as a parameter a XML file being the import’s configuration:
- activate or disable concurrency in the output model,
- set-up schema, table, or column filters,
- set-up formatters,
Even though you could actually do all this in command line, all available features were not necessarily available in previous versions of the wizard: but that’s it, with the latest build, case solved, we added them all, what you could do in XML and in command line, you should be able to do it in through the wizard!
The magic happens in the “advanced view” of the property grid (click on the yellow ‘+’ sign of the property grid to access it):
You’ll now see plenty of new options as well as descriptions detailing what they do. For instance, the property set in the screenshot above indicates the modeler to skip all tables whose name start with a ‘_’ or “BAK_” by using a comma separated list of regular expressions.
Another cool feature of the importer which is now available is formatters. Using formatters you can define regular expressions and replace a matching group by a string.
For instance in the screenshot above I’m replacing all column names starting by a trigram and a ‘_’ by an empty string to remove all those column prefixes so I don’t have goofy property names in my model.