I have a compiled strategies that sometime shows up on a machine and a slightly modified newer version does not show up. They ALWAYS show up on all the computers that I have (both Win 7 & 10). All the machines are using 64-bit versions of WLP and I am compiling all of the strategies with .Net Framework 4.6.2

Anyone have any ideas what I might be missing or doing wrong? Thanks!

Vince

QUOTE:
I have a compiled strategies that sometime shows up on a machine and a slightly modified newer version does not show up.

By compiled strategies, are these *.DLL files (created by VS from *.cs files) or *.XML files (created by the WL editor)? If it's the latter, this sounds like a corrupted XML source file to me. Did you have a WL crash or OS crash (AbEnd) while these files were opened?

Assuming their WL source (C#) code is still intact, I would create a new source file from code, then copy all the source lines from the old source file into the new source file and save it. I would verify the new source file is working correctly before deleting the old file.

If you're really good with editing XML files, you could pull the troubled XML file into the Visual Studio editor and fix it assuming you know exactly which XML lines are missing or broken. If not, I would use the first approach mentioned above instead.

Possible reasons include:

* duplicate Strategy GUID (unchanged)
* bitness (make sure you target Any CPU)
* target folder (e.g. occasionally copied to 32-bit WLP or to a subfolder inside "Wealth-Lab Pro 6" instead)
* "Downloaded from the internet" flag not cleared after obtaining the DLL file using online sync service. To quote the FAQ below, paragraph #3:

QUOTE:
When installing extensions obtained by email or file download from 3rd party sources (be careful!), such files are automatically marked by Windows as "insecure" (all versions starting from Windows 7). After dropping such DLL file into Wealth-Lab's program folder, it will not be loaded. Close Wealth-Lab and clear the "File downloaded from the internet" flag in File Properties as suggested in this article: What Causes the "File Downloaded from the Internet" Warning and How Can I Easily Remove It?

P.S. Should someone else stumble onto the same issue with other extensions (other than compiled Strategies), for more reasons they might check out the FAQ:

Extension installed in Wealth-Lab doesn't show up after restarting application.

superticker,

These are *.DLL files compiled by VS Community 2017.


Eugene,

1. I use a new GUID for each instance, even after modding a file
2. Using "Any CPU"
3. All machines only have 64-bit WLP, never had 32-bit
4. All *.DLL files are encrypted before transfer so are not modified during transport.

I have suggested that folks look at the link on the "File Downloaded fron the Internet" flag to see if that might be the issue.

Thanks all!

Vince

QUOTE:
4. All *.DLL files are encrypted before transfer so are not modified during transport.

It's not about encryption or modification. Since you say "transport" I assume that either you transport the DLL to different PC or get the transported DLL file from somebody. Whatever it is, I'm pretty sure that in both cases Windows has marked this file as "downloaded from the internet". Unless this flag is cleared such assembly will not be visible in Wealth-Lab Pro. This protection measure is in place since Windows 7.

Understand Eugene! I have sent the link you provided to folks to see if that is an issue. The strange part is this is NOT reproducible continually. Sometimes the *.DLL file is seen after installation, and then after a mod version is provided it is not seen, and then after a subsequently modded version can be seen again. And never on my development machine; it always shows up there regardless.

Vince

Hope this helps. If it's not we'd need much more facts about your code, settings and environment to make this troubleshooting procedure productive. It's just guesswork at this ponit, and I'm not a fan of it.

As a last minute thought, antivirus activity should not be discarded!

Hi All!

Just thought that I would drop a note about the problem and its resolution.

There appears to be a minor incompatibility between WinRar (which I use to package and encrypt a Zip file [using the legacy Zip format]) and WinZip V.21 (but not V.23) for how it handles binary files. Using a hex editor I found that a single byte in the header of the .DLL file was being changed during the encryption-decryption-Zipping process which was why the .DLL was not recognized on some computers. I am not sure if it is a WinRar problem or a WinZip problem, but since it is now resolved it does not matter. :)

Vince

Nice detective work :)