In addition to the Visual Studio Integrated Modeler, CodeFluent Entities provides a set of tools in the form of executable files (.exe).
You can take a look in the installation directory of CodeFluent Entities to find these tools.
You will find:
- The Builder (CodeFluent.Build.exe)
- The Importer (CodeFluent.Import.exe)
- The Portable Modeler (CodeFluent.Modeler.Portable.exe)
- The Service Hoster (CodeFluent.Runtime.ServiceHost.exe)
- The Meta Model Explorer (CodeFluent.View.exe)
For a more detailed description take a look at this blog post.
Well, these tools come in two versions: the x86 version and the x64 version.
The x86 version tools are located in \Program Files (x86)\SoftFluent\CodeFluent\Modeler while the x64 version in \Program Files (x86)\SoftFluent\CodeFluent\x64.
By Default, the CodeFluent Entities Modeler (integrated to Visual Studio) executes the x86 version tools, but maybe it would be interesting to use the x64 version (for instance, if you have a big model).
If you use the CodeFluent Entities Tools without its integration to Visual Studio you only need to look in to the wanted directory.
On the other hand, if you use the Visual Studio Integrated Modeler you can easily configure the Build Platform from the CodeFluent Entities Options. Check the “CodeFluent Entities Build – 32 Bits” option for a x86 platform or the “CodeFluent Entities Build – 64 Bits” option for a x64 platform.
Maybe you also noticed in the picture above that there is an option “CodeFluent Entities Build – CLR4”. Indeed, some tools are also built on the CLR4 (the rest is built on the CRL2) as:
- The Builder (CodeFluent.Build4.exe)
- The Service Host (CodeFluent.Runtime.ServiceHost4.exe)
Using a tool built on the CLR4 allows easier integration for custom assemblies (such as custom Aspects or Producers).
CLR2 tools can also be used with the CLR4 assemblies but it requires .config modifications.
The CLR4 tools exist in the x86 version, as well as in the x64 version.
Finally, using a x86 or a x64 tool has no impact when generating applications, as the product builds platform-agnostic code. You will be able to use “Any CPU”, X86, or X64 at your convenience.
Pablo Fernandez Duran
First, we need to distinguish two different environments:
- at modeling time: during developments, when building your model,
- at run time: the built application.
At Modeling Time
- The Modeler runs in 32-bit mode exclusively: this is due to the fact that the Modeler is an extension of Visual Studio which is a native 32-bit process,
- All other tools provided (.exe) both have 32-bit and native 64-bit binaries versions available,
- All tools can run with 32-bit WoW64 on 64-bit machines
- Some producers are supported in 32-bit mode exclusively like the SQL Server Producer v1.
At Run Time
Regarding run time, generated applications are completely “bitness agnostic”: using CodeFluent Entities you can create 32-bit, 64-bit, or “Any CPU” applications. By the way, this is possible because CodeFluent Entities run time assemblies are compiled as “Any CPU” so it’ll use the bitness of the built application (x86 or x64) or the bitness of the target machine if your application is built in “Any CPU”.