.NET Tab

This tab is only available when you have the .NET generation enabled. Here is what you will see if you have .NET generation enabled.

.NET application information

In this part you will be able to enter the information regarding the assembly such as:

• Namespace name
• Version
• Compatibility
• Culture
• Company
• Product
• Trademark
• Copyright

You can also specify a cryptographic key for your application so that the compiled assembly can be added to the Global Assembly Cache (GAC). Alternatively, if you wish to create a new cryptographic key for your assembly then the 'Generate' key will automatically generate one.

Options

• verifiable: in the .NET world, verifiability is important. This is the only way to ensure that an application is not going to crash or to crash your system by accessing not authorized memory locations. Due to some semantic differences between Eiffel and .NET, our code generation is not always verifiable for performance reasons. If you want your code to be verifiable, you need to select this option. The compiler will then generate a code that will be slightly slower.
• generate DLL: instead of generating an EXE it will generate a DLL.

Class and feature naming

The CURSOR class is located at '$ISE_EIFFEL\library\base\structures\cursors'.  

• Follow .NET naming guidelines: this option determines whether the generated .NET code uses the Eiffel or .NET naming convention.  Using Ildasm, the IL disassemble tool provided with the .NET Framework, we can see the difference between them.  The Eiffel naming convention uses uppercase characters for all classes whereas the .NET nomenclature uses the Camel Case style.  Note that this option is only available in a non-compiled system.  Once the system has been compiled the naming standard is thus fixed for the project.

• Use cluster names and Use full cluster names:  These options dictate how a class is known to the system.  In our CURSOR example there are 4 main scenarios.  For a quick overview of all scenarios refer to the table at the bottom of the page.  If neither box is selected we just have 'CURSOR' or 'Cursor' (depending on whether the .NET naming guidelines are used), as seen above.  If 'Use cluster names' is checked then the cluster name is pre-pended to the class name, so 'CURSOR' now becomes 'base.CURSOR'.

If 'Use full cluster names' is selected then the full cluster name is pre-pended to the class name, so it thus becomes 'base.structures.cursors.CURSOR'.

The final scenario is where a namespace has been defined for the cluster in the Clusters tab of the Project Settings.  In this situation the namespace overrides the name of the cluster.  In the example below the namespace name 'MyBaseNameSpace' is used so the resulting name is 'MyBaseNameSpace.structures.cursors.CURSOR'.

Naming Scenarios

This table shows how the class name generation is affected by the naming options using the CURSOR class found in '$ISE_EIFFEL\library\base\structures\cursors' as an example.