I'm trying to build a library with Visual Studio for use in WL. I can't get the library to show up in the Tools-Assembly References menu.
I am creating a test library on .net 6.0, I tried to build it under x86 and x64.
Please help me understand what I'm doing wrong.
If necessary, I can record the entire process of creating a dll on video.
I am creating a test library on .net 6.0, I tried to build it under x86 and x64.
CODE:
namespace testLibrary { public static class TestClass { public static int TestFunc() { return 0; } } }
Please help me understand what I'm doing wrong.
If necessary, I can record the entire process of creating a dll on video.
Rename
Which one of detailed API Library instructions are you following?
https://wealth-lab.com/Support/ExtensionApi
https://wealth-lab.com/Support/ExtensionApi
QUOTE:
I can't get the library to show up in the Tools-Assembly References menu.
Where did you even read about this? Our manuals never suggest it. Your library will not appear there unless it's installed in the GAC, and you don't need it.
Solution: place your assembly's DLL file in the "Wealth-Lab 8" folder under Program Files\Quantacula, LLC.
QUOTE:
creating a test library on .net 6.0, I tried to build it under x86 and x64.
Off topic, but you should build your library strictly for x64 and not include x86. There's nothing in WL8 that's x86 compatible.
QUOTE:
Which one of detailed API Library instructions are you following?
https://wealth-lab.com/Support/ExtensionApi
I did not find information about including libraries in the official manual. But I found a topic on a third-party forum:
http://www.wealth-lab.net/Forums/Thread.aspx?pageid=2&t=138~-1
I would like to see this information in an official source, including information about the compatibility of libraries and WL8 (Framework version and bitness).
I have successfully included the library:
https://www.alglib.net/
On the advice of Eugene, I simply copied the library to the WL8 folder. Although it didn't appear in the Assembly References list, it worked.
Thank you all for your help.
Great to hear you got it working!
The instructions for copying custom assemblies appear here,
I think it would be less confusing for new users if there were either a blog post or an entry in the Extension API page (even though we aren't building an extension) much like the "StrategyLibrary API" section. The working assumption is that developers will search the forum for "Visual Studio" to locate this information. And, although that works, it's not ideal (otherwise, we wouldn't be seeing a post like this). Integrating all the Visual-Studio forum posts into a "How to develop a custom/local code library" section would make the most sense.
I would have called them "local" or "external" assemblies rather than custom assembles. Perhaps I'm too traditional.
Off topic, but I like https://numerics.mathdotnet.com/ a little better than https://www.alglib.net/ because the former is written in C#, so bindings are better if you're using C#.
I wouldn't call external libraries directly from your strategy code because the data types between WL and the external libraries won't agree. Instead, write local, high-level stub code that converts the data types along with their other high-level functions.
I would have called them "local" or "external" assemblies rather than custom assembles. Perhaps I'm too traditional.
Off topic, but I like https://numerics.mathdotnet.com/ a little better than https://www.alglib.net/ because the former is written in C#, so bindings are better if you're using C#.
I wouldn't call external libraries directly from your strategy code because the data types between WL and the external libraries won't agree. Instead, write local, high-level stub code that converts the data types along with their other high-level functions.
Your Response
Post
Edit Post
Login is required