docs.xsharp.it

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Namespaces in migrated VO applications ======

Migrated applications does not have indicated any namespace, therefore some special rules apply.
Normally, such applications use the compiler option /ins (use implicit namespace), so the compiler searches the referenced libraries and adds namespaces with special attribute. You can see that if you open the compiled exe with a tool like ILSpy. For more informations please look at [[compiler_option_ins|/ins compiler option]]

When you migrate a VO app with the name DictEdit, then the generated Assembly name by the Exporter is DictEdit.EXE and the Default Namespace is also DictEdit

Please note that this default namespace is only used with:

- when you enable the option "Prefix classes with Default Namespace". In that case, the class Foo becomes DictEdit.Foo

- when you create files inside Visual Studio. A new class "Class1" will be generated as DictEdit.Class1.
When the new class file is in a folder "Test" then VS generates code for the class as DictEdit.Test.Class1.

The functions class in a migrated application is derived from the assembly name and not from the default namespace.

When the assembly name is DictEdit.Exe, then the name of the functions class is DictEdit.Exe.Functions

When the assembly name is DictEdit.Dll, then the name of the functions class is DictEdit.Functions

The compiler automatically adds a using DictEdit.Exe.Functions inside each of the programs in your app (assuming DictEdit.Exe is your assembly name).

So there is no need to prefix the code with Functions. If you do want to prefix then I would recommend to use the full name: DictEdit.Exe.Functions.Start()

(Comment by R.v.d.H.: https://www.xsharp.eu/forum/topic?p=30999#p30999)