Differences

This shows you the differences between two versions of the page.

--- namespaces_migrated_applications [2024/09/11 04:56] – wolfgangriedmann
+++ namespaces_migrated_applications [2024/09/11 06:35] (current) – wolfgangriedmann
@@ Line 2: / Line 2: @@
 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 adds the needed namespaces from the runtime libraries to the program (you can see that if you open the compiled exe with a tool like ILSpy.
+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
@@ Line 16: / Line 16: @@
 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)