/bundles/itninjaweb/img/Breadcrumb_cap_w.png
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?
0 Comments   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

0
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?
Answered 02/16/2005 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
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.
Answered 02/16/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment