16
I Use This!
Inactive

News

Analyzed about 13 hours ago. based on code collected about 16 hours ago.
Posted almost 11 years ago by [email protected] (John Tan)
Thanks Richard.... OK, a quick check on heat.exe shows that when used on a COM DLL, it will generate the necessary registry item in the wxs during compilation.
Posted almost 11 years ago by [email protected] (Richard Bateman)
The reason you don't see it is because that information is compiled by heat.exe into a np<your plugin>.wxs file. If you look in that file and discover no COM registration information then you're most likely missing dependencies at build time ... [More] (DLLs that your plugin needs). One reason for using a combined msi and exe installer would be so you can [Less]
Posted almost 11 years ago by [email protected] (John Tan)
Another reason why I prefered NSIS was that in the installer, I have a routine which will detect any browsers currently holding on the the plugin and will stop the process if it's still loaded. It was easy to implement in NSIS but while I'm sure it's definitely doable in MSI, it's going to be too
Posted almost 11 years ago by [email protected] (John Tan)
Thanks Richard, One thing, which I have not been able to figure out is, as you mentioned, all registry entries will be journaled but which part of the WXS code exactly is that one doing the plugin registration? As far as I can see, there aren't any part of the WXS script related to that. Neither do I see
Posted almost 11 years ago by [email protected] (Richard Bateman)
ForceRemove I believe tells it to force removal of that tag even if something has been added that isn't in the .rgs file. AFAIK there are no keys that are added that aren't removed. The reason for using a msi (whether wix or not) is to ensure that ... [More] that is the case in a journaled manner, instead of in a "well, we're pretty sure we did this before, so do the opposite of this now to uninstall" manner. [Less]
Posted almost 11 years ago by [email protected] (John Tan)
OK, a mistake here.... I should ask, should I remove away the ForceRemove tag so that during the unregistration, it will be deleted. The NoRemove tag are on the higher branch which should be permanently there.
Posted almost 11 years ago by [email protected] (John Tan)
Hi, I know this has been discussed many times and Richard has always stressed on using WiX instead of using other installer and avoid using regsvr32 to register plugin. I have tried studying WiX and created an installer but it is really creating a mess. The plugin is never registered when I deployed to a group
Posted almost 11 years ago by [email protected] (John Tan)
Hi Gaurav, As I used it to drive the video rendering in windowless mode, I can tell you how I did it for my case. Assuming Player and PlayerAPI class is similar to FB-generated xxx and xxxAPI class. 1) Create member variable ... [More] boost::function<void(void*)> onDrawDelegate; in Player.h 2) In the PlayerAPI init code, getPlugin->onDrawDelegate = boost::bind(&SMPPlayerAPI::Red rawWindowless, [Less]
Posted almost 11 years ago by [email protected] (Gaurav)
Hi, Sorry for the delay, I was busy with the development of Mac version of the plugin so couldnt test this. Finally, facing the same problem with Invoke in a different place. Let me explain my code properly. In the onWindowAttched event, I create the opengl thread and my mainApplicationPtr object pointer. mainApplicationPtr is object of
Posted almost 11 years ago by [email protected] (John Tan)
I remember reading from somewhere that IE can be picky on the cert issuer. Safest is to use VeriSign.