RANT: Why must all Custom Action DLL's be written in C/C+???
Hello all,
Does anyone know the reason why Custom Action DLL files in a Windows Installer package MUST be written in C/C+ instead of other languages like Visual Basic?
Does anyone know the reason why Custom Action DLL files in a Windows Installer package MUST be written in C/C+ instead of other languages like Visual Basic?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
aogilmor
19 years ago
Brent, I don't know the answer but I'd ask Wise for a product enhancement request. I didn't know you could do DLL stuff with VB -but I'm a relative neophyte when it comes to programming. Isn't C/+ supposed to be faster, more secure than VB?
ORIGINAL: brenthunter2005
Hello all,
Does anyone know the reason why Custom Action DLL files in a Windows Installer package MUST be written in C/C+ instead of other languages like Visual Basic?
Posted by:
brenthunter2005
19 years ago
Its not a WISE limitation, its actually a Windows Installer limitation.
With regards to Visual Basic DLLs, I think they are ActiveX DLL's.
Oh well, sh!t happens.
With regards to Visual Basic DLLs, I think they are ActiveX DLL's.
Oh well, sh!t happens.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.