Tweet
PwrDev can load .NET assemblies from memory.
You can include your assembly dll file(s) in your application the way you want it.
Like as resource or !db statements (encrypted?).
This 'may' be a method to prevent decompilation of your MSIL, not guaranteed though.
I consider it much safer than using it as stand alone assembly.
The same applies to the latest test i did, i was able to write something which executes a .NET executable from inside a PowerBASIC executable.
Of course created with PwrDev.
If i get some positives on this i may implement it into PwrDev as feature.
If you like .NET for your PowerBASIC projects (using PwrDev) visit:
A previous discussion about using assemblies with PowerBASIC (using PwrDev) can be found here:
You can include your assembly dll file(s) in your application the way you want it.
Like as resource or !db statements (encrypted?).
This 'may' be a method to prevent decompilation of your MSIL, not guaranteed though.
I consider it much safer than using it as stand alone assembly.
The same applies to the latest test i did, i was able to write something which executes a .NET executable from inside a PowerBASIC executable.
Of course created with PwrDev.
If i get some positives on this i may implement it into PwrDev as feature.
If you like .NET for your PowerBASIC projects (using PwrDev) visit:
A previous discussion about using assemblies with PowerBASIC (using PwrDev) can be found here:
Comment