EldoS | Feel safer!

Software components for data protection, secure storage and transfer

InstallHelperDll method

Also by EldoS: CallbackProcess
A component to control process creation and termination in Windows and .NET applications.
#6256
Posted: 05/14/2008 15:55:06
by Sid Schipper (Standard support level)
Joined: 03/14/2008
Posts: 285

I tried using the InstallHelperDll function, which in the documentation from build 27 it says returns a BOOL, but the compiler tells me that it is a void function. Also, if I change the prototype for it in Cbfs.h to a BOOL function, I get an unresolved external reference for that function. Which should it be, BOOL or void?
#6258
Posted: 05/14/2008 16:41:51
by Sid Schipper (Standard support level)
Joined: 03/14/2008
Posts: 285

Also, I am not clear on what the FileName parameter is used for in this API. For the InstallDriver method your sample uses a hard coded GUID for the FileName. When I install the helper dll, should I use the same GUID as I did for the driver? Or should I get a new one from the system and use that one instead?
#6259
Posted: 05/14/2008 16:43:32
by Sid Schipper (Standard support level)
Joined: 03/14/2008
Posts: 285

Oops, in the previous message I meant to say ProductName parameter instead of FileName Parameter. I hope that makes my question clearer.
#6261
Posted: 05/15/2008 00:57:48
by Eugene Mayevski (EldoS Corp.)

1) The documentation corresponds to the code completely. What are you looking at - the instaler DLL or CallbackFileSystem class?

2) Progam name is *your* name. It's not something you copy from the sample. And you are free to put anything there, as long as this value is unique (doesn't intersect with other users of CBFS). You may use the same name for the driver and the helper DLLs, or you can use different names. This doesn't matter.


Sincerely yours
Eugene Mayevski
#6265
Posted: 05/15/2008 03:12:51
by Robin Astle (Basic support level)
Joined: 04/15/2008
Posts: 30

Quote
Sid Schipper wrote:
I meant to say ProductName parameter instead of FileNa


Copied directly from the documentation:

ProductName is used to distinguish between installations of the helper DLL made by different applications and to prevent the situation when the DLL is installed by two applications and further deinstallation of one of them removes the DLL.

So yes, I use the GUID of my application there which is good practice in my opinion.
#6276
Posted: 05/15/2008 12:35:57
by Sid Schipper (Standard support level)
Joined: 03/14/2008
Posts: 285

In regards to the documentation, there is a conflict between what it says in the section on the CallbackFileSystem class, where the InstallHelperDll method is defined as a void function, and the section on the installer DLL, where the same method is defined as a BOOL function. Which one is correct?
#6277
Posted: 05/15/2008 12:38:41
by Sid Schipper (Standard support level)
Joined: 03/14/2008
Posts: 285

Also, the prototype for it in the Cbfs.h file is for a void function, so I am still confused as to why the installer DLL documentation says it is a BOOL function?
#6278
Posted: 05/15/2008 12:45:43
by Sid Schipper (Standard support level)
Joined: 03/14/2008
Posts: 285

OK, now I finally get it. The Installer dll has a different h file associated with it, cbfsinst.h, that exposes the functions in the dll. That h file has different prototypes than the ones in the cbfs.h file. I know I must sound stupid, but it would be nice if you made things a little clearer for idiots like me :-)
#6307
Posted: 05/19/2008 02:23:02
by Volodymyr Zinin (EldoS Corp.)

It's our mistake. We'll fix this. Thanks.
Also by EldoS: CallbackRegistry
A component to monitor and control Windows registry access and create virtual registry keys.

Reply

Statistics

Topic viewed 4228 times

Number of guests: 1, registered members: 0, in total hidden: 0




|

Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!