Is there a "simple way" to locate a custom MyIndicators.DLL file to someplace other than the Wealth-Lab program directory?

I added the alternative location to the list of "Other Assemblies to Reference" in the WL editor, and indeed the compiler/linker gripes about having duplicate assembly files if they're placed in both the program directory and the alternative location. But WL won't load the DLL from the alternative location for some reason.

Yes, I know I can create a "hard" directory link as a workaround. Gee, I think you need a utility off the Windows Resource Kit to do that. Creating a symbolic link (Windows Shortcut) doesn't solve this problem; I'm not sure why not. Thoughts?

---

Additionally, is there a way to update/replace the MyIndicators.DLL file without restarting Wealth Lab? It doesn't appear the WL Extension Manager can do this, but it would be nice if it could. Does Microsoft have a tool for dynamically loading and unloading DLLs?

QUOTE:
But WL won't load the DLL from the alternative location for some reason.

"Other Assemblies to Reference" does not apply to indicator libraries, only to code dependencies of particular Strategies. Alternative locations are not supported and all extension files (including but not limited to indicator libraries) must reside in the root of WL6 main folder under Program Files. Symlinks are not supported too but you're free to experiment (this might void your warranty):

http://www.tested.com/tech/windows/39-using-symlinks-in-windows-for-fun-and-profit/
http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/?PageSpeed=noscript

QUOTE:
Additionally, is there a way to update/replace the MyIndicators.DLL file without restarting Wealth Lab?

This is not supported. You must restart WLP if you wish to update any extension (custom built or downloadable) or to modify externally most of Wealth-Lab's XML/TXT config files. However, with Edit and Continue feature of Visual Studio you should be able to change the code being debugged. Lately the feature seems to have been added to 64-bit VS as well (previously only 32-bit IDEs were lucky to have it).

QUOTE:
"Other Assemblies to Reference" does not apply to indicator libraries, only to code dependencies of particular Strategies.

Thanks for that clarification. So any DLL that must be "preloaded" so it appears in the Wealth-Lab main menu system (such as indicator libraries for the Indicator Menu) cannot be referenced via "Other Assemblies to Reference". Interesting.

I'm gathering if I create a separate MyComponents.DLL, which does not appear in any WL menus (and has no WL helper-file that needs preloading), that DLL could be referenced with "Other Assemblies to Reference" at a different location. I'll give that a try.

Thanks also for the URLs about hard directory links for Windows.

---

I didn't know the Visual Studio debugger lets you edit running code. That's a nice feature.