. Net CF get the file name and full path of the current DLL and its calling program

In DLL, you sometimes need to use the main callProgramTo obtain the name and path of the calling program correctly. This must be distinguished from the name and path of the DLL itself!

 

This involves the use of the system. reflection. Assembly class.

Getexecutingassembly: Gets the Assembly containing the Code currently executed

Getcallingassembly: Returns the system. reflection. Assembly that calls the method currently being executed.

 

The following are static functions in a DLL. Note the differences:

2. Public Static Void Getname()
4. {
6. // The Name Of The current DLL-related collection
8. Debug.Writeline(Path.Getfilename(Assembly.Getexecutingassembly().Getname().Codebase));
10. Debug.Writeline(Assembly.Getexecutingassembly().Getmodules() [0].Name);
12. Debug.Writeline(Assembly.Getexecutingassembly().Manifestmodule.Name);
14. Debug.Writeline("");
16. Debug.Writeline(Assembly.Getexecutingassembly().Getname().Codebase);
18. Debug.Writeline(Assembly.Getexecutingassembly().Getmodules() [0].Fullyqualifiedname);
20. Debug.Writeline(Assembly.Getexecutingassembly().Manifestmodule.Fullyqualifiedname);
22. Debug.Writeline("");
24.  
26. // Name of the relevant Assembly of the caller
28. Debug.Writeline(Path.Getfilename(Assembly.Getcallingassembly().Getname().Codebase));
30. Debug.Writeline(Assembly.Getcallingassembly().Getmodules() [0].Name);
32. Debug.Writeline(Assembly.Getcallingassembly().Manifestmodule.Name);
34. Debug.Writeline("");
36. Debug.Writeline(Assembly.Getcallingassembly().Getname().Codebase);
38. Debug.Writeline(Assembly.Getcallingassembly().Getmodules() [0].Fullyqualifiedname);
40. Debug.Writeline(Assembly.Getcallingassembly().Manifestmodule.Fullyqualifiedname);
42. }

 

The Dynamic Static environment is in the testclassclass, and then the static environment is called in the calling program, and the calling program is getapplicationname.exe ", as follows:

1. Testclass.Getname();

 

The observed results are as follows:

2. Testdll. dll
4. Testdll. dll
6. Testdll. dll
8.  
10. \ Program Files \ getapplicationname \ testdll. dll
12. \ Program Files \ getapplicationname \ testdll. dll
14. \ Program Files \ getapplicationname \ testdll. dll
16.  
18. Getapplicationname.exe
20. Getapplicationname.exe
22. Getapplicationname.exe
24.  
26. \ Program Files \ getapplicationname \ getapplicationname.exe
28. \ Program Files \ getapplicationname \ getapplicationname.exe
30. \ Program Files \ getapplicationname \ getapplicationname.exe

 

There is another way, but you can only get the name of the calling program, not the full path, that is throughAppdomain. currentdomain. friendlynameObtain, as follows:

1. Debug.Writeline(Appdomain.Currentdomain.Friendlyname);

Result:

1. Getapplicationname.exe

You can also refer to this articleArticle: Write and design friendly controls for Windows Mobile.Appdomain. currentdomain. friendlynameI have introduced it.

 

CodeDownload:

Getapplicationname.rar