When are vb.net modules and its members loaded to memory

[IT_Researcher]

I wanted to know how modules and their members are loaded into memory in vb.net windows form application.

According to a VBForums post [1], Visual Basic loads code modules on demand, not all at once during startup. However, it's unclear what happens to functions in a module that are never called.
I also found a statement in Microsoft documentation [2] stating that a module and its members has the same lifetime as the program. Does this mean modules are loaded into memory during application startup ?

To get better clarity, I tried using a profiler and check when module gets loaded, but it didn't get clear information.

Here are my questions:
1. Do modules and all their members load into memory during application startup? If yes, is it possible to lazy load a module or its members?
2. If no, and if loads to memory only on function/method called, will other function/method in the same module be loaded to memory along with called function/method.
3. Is using a profiler the right way to monitor module loading into memory? If not, what other methods can be used?

[1] VBForums: VB Modules
https://www.vbforums.com/showthread....691-VB-Modules

[2] Microsoft Documentation: Module Statement
https://learn.microsoft.com/en-us/do...dule-statement