docs.xsharp.it

User Tools

Site Tools

Trace: • assign_no_returnvalue • tuples • net_introduction • gchandle • xsharp_sites • delegates • extended_syntax • quickstart_xsharp_vo • xsharp_dialects • define
namespaces_migrated_applications

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
namespaces_migrated_applications [2024/09/11 04:57] – wolfgangriedmannnamespaces_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. 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 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
namespaces_migrated_applications.1726030622.txt.gz · Last modified: 2024/09/11 04:57 by wolfgangriedmann