I copied this strategy from another posting. Everything seemed to work but I still don't see the strategy in the WL6.
I copied both the dll and pdb files to the WL6 directory.
Any help would be appreciated
Here is the source code.
CODE:
Please log in to see this code.
Size:
Color:
FAQ:
*
FAQ | Miscellaneous, Extensions >
"I created an indicator library, but it doesn't show up in Wealth-Lab 6"
"A library compiled for .NET 4.0 doesn't show up in Wealth-Lab 6"
Size:
Color:
Thanks that was it. phil
Size:
Color:
We're trying to escalate the issue of migrating WLP/D 6.4 to .NET 4.0. This is utterly important as .NET 2.0 is more than five years old. Situations like your would be eliminated by changing target framework to NET4.
Size:
Color:
This post seems ot have gotten me almost all the way there but when I retargeted it to any of the versions earler than NET 4.0 within Visual Studio I get error messages like the one below (this one was trying to target Net 3.5). And although it was warnings not errors it did not output files to the destination This was the cleanest of the set , the other re-targetings resulted in more "not found messages" -
Warning 1 The primary reference "Microsoft.CSharp", which is a framework assembly, could not be resolved in the currently targeted framework. ".NETFramework,Version=v3.5". To resolve this problem, either remove the reference "Microsoft.CSharp" or retarget your application to a framework version which contains "Microsoft.CSharp". TestStrategy
Any help or suggestions of what to try next would be great.
Size:
Color:
You can safely delete that Microsoft.CSharp reference from References. Being a leftover from .NET 4.0 default preset, it's N/A in .NET 3.5 (doesn't exist).
FYI,
What is Microsoft.csharp.dll in .NET 4.0
Size:
Color:
P.S. On the bright side, compatibility with .NET 4.0 framework is planned for a future Wealth-Lab release.
Size:
Color:
That was the last issue, I now have my test case up and running.
A big thank you for the help.
Size:
Color: