A new version of CodeFluent Entities is publicly available on our servers (the 661) and this new version contains a brand new ribbon:
In a nutshell, it contains the same tabs and menus as before, however it was re-designed to perform better when used in little spaces and has a new look
The screenshot below illustrates how much more information is displayed with the new ribbon compared to the old one:
A few months ago we added support for non-Latin characters in models. Though nice at first, we noticed that it slowed down method inference noticeably as we had to load non-Latin character sets to parse CFQL when a majority of our users were using Latin characters indeed.
This is why starting with build 646 and upper, we disabled non-Latin character support in CFQL. Nonetheless, you’ll be glad to know that this is configurable, so if you do want to use Cyrillic in your CFQL queries you’ll have to enable it explicitly, and here’s how to do it!
Enabling support is done through an appSetting in the configuration file. Here’s a sample CodeFluent.Build.exe.config configuration file which you can place next to CodeFluent.Build.exe (e.g. “%ProgramFiles(x86)%\SoftFluent\CodeFluent\Modeler”):
<?xml version="1.0" encoding="utf-8" ?> <configuration> <appSettings> <add key="CfqlAllowsNonLatinCharacters" value="true" /> </appSettings> </configuration>
Please note that you’ll also need to set that appSetting in the devenv.exe.config configuration file to be able to use non-Latin characters in CFQL queries at design time as well.
Here is the CodeFluent Entities roadmap for the beginning of this year (click on the image for a broader view):
In the latest builds (higher than 646), we have shipped the PostgreSQL importer, as well as the ASP.NET Producer V2 (which is currently in beta). In the build to come (higher than 656), we will ship the following new features:
- Automatic Data Annotations (e.g. “ADA”): the BOM producer will automatically create System.ComponentModel.DataAnnotations from the rules declared in the model. Data Annotations supported are StringLength, Required, RegularExpression, Enum, Range, and DataType. CodeFluent Entities rules are much richer than data annotations, and some information will not be translated. For example, there is no equivalent to the features of the CompareValidate rule in data annotations, or there is no standard Luhn check Data Annotation.
- The new RequiredValidate rule. This property validation rule is almost equivalent to the ObjectValidate rule, but is more simple. It has been created mostly to be able to have a direct equivalent CodeFluent Entities rule to the RequiredAttribute CodeFluent Entities Roadmap during ADA mapping process.
- The new LookupValidate rule. This property validation rule is used to check a property value is in a list of allowed values. The list can be declared ad-hoc (a string representing a list of items separated by a specific separator character), or can be defined by an enumeration type name. This enumeration can be declared in the CodeFluent Entities model, or can be an existing CLR enumeration type. This rule also support the combination of multiple values.
The R&D Team
A few months ago we released the CodeFluent Runtime as a NuGet package so developers could benefits from its features (e.g. JSON Serializer, WinForms Wizard control, EditableUri, Utilities, etc.) in their .NET projects.
Today we’re pleased to announce a new package replacing the previous one: the CodeFluent Runtime Client!
It’s basically the same as the previous one with new controls (yay! a ribbon menu!) and most importantly supporting the .NET 4 Client Profile on top of supporting all .NET Framework versions from 2 and upper, across all technologies (WPF, WinForms, ASP.NET, consoles, services, SharePoint, etc.).
Just like last time, it’s all free and it’s all happening on NuGet