so what's the verdict on distributing a .net dll to the people on the board? It's nothing more than a wrapper for the product which is b3d.dll so it'd be ok, correct?
I've seen it asked a couple of times now without an official response.
I'm going to assume it's fine if I dont' get any response from the official tech support.
Why would you want to add another layer of code? The '.cs' file that comes with the SDK seems to be just fine.
because I would rather have it as a dll. It's a personal preference. One dll versus multiple copies of the code floating around to me is a better option.
I guess I could see that. Package it up into an Assembly that you could just reference into your project. Pretty good idea. How would you handle updates?
Just make the .cs into a dot.net dll then? That should take about 1 minute... :P
Unless you start having namespaces bugs. then it could take 5 minutes... :D
I think the .net dll is a good idea so a single .dll will give direct managed access to the b3dsdk.dll from C#, Visual Basic, Delphi for .net, any mono for windows language, etc.