[WTB] Support for loading 3rd party assemblies in plugins

[Apoc]

Yea, yea, I know why you don't support it currently. But for those of us who know what we're doing, we're pretty much unable to do quite a few things that would help HB as a whole.

Personally; there's a few assemblies I'd love to be able to load; but am unable to due to your compiler code.

System.Data.Sqlite (SQLite wrapper for .NET)
System.Data.MySql (MySQL wrapper for .NET)

The various SharpZipLib libraries.

The list does go on, but basically, just give us some way to actually extend HB without having to package the source for our libraries with the plugin. (In some cases, we just plain cannot, due to C++/CLI and the like)

The other alternative, is for us to wrap the libraries via Reflection, which we all know is painfully slow, and tedious work.

Just include some form of 'extra parsing' in your compiler code to allow us to specify options.

Something as simple as:

// Reference: System.Data.Sqlite.dll

And then have your compiler just add the reference, is all we really need.

 

[Hawker]

My concern has always been that someone will abuse our users trust - Lets make a whitelist of dlls that are safe and we will enable them in next release.

 

[z0mg]

That shouldn't be much of an issue now that everyone can see the source? WTB VisualBasic support as well .

 

[emmark]

As Hawker, I am worried about abuse.

 

[MaiN]

If this was to be implemented, it would be via a whitelist and a checksum.

 

[highvoltz]

how about adding PresentationCore.dll, to add keybinding suport to plugins.

 

[Apoc]

how about adding PresentationCore.dll, to add keybinding suport to plugins.

You don't need PresentationCore.dll. Use GetAsyncKeyState (PInvoke it)

 

[cryotic]

The funny thing is that before i clicked on the thread...i kinda knew that apoc was the author.

But yeah, its always great to let the developers do more things with hb.

 

[theholyone]

All i want as an update for HB is a support for no dc possible. i was for serious