Re: Custom Uninstall Question

The CAB configuration file has a parameter for the custom setup dll file.
It uses this DLL for both install and uninstall. If you set this then it
always gets called in my experience. The parameter is called: CESetupDLL.

The CAB file is copied and executed on the device itself so your custom DLL
is not executed at all on the PC, only on the Pocket PC.


"Robert W." <RobertW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E44B5F13-D1B2-44F8-B3B8-DF05BED4DA9E@xxxxxxxxxxxxxxxx
> Chris,
>
> Of course, but are there any tricks to bunding this DLL with the CAB file?
>
> I read one thread entry somewhere that said I could simply replace the
> vsd_setup.dll with my own DLL. Is this a typical approach?
>
> --
> Robert W.
> Vancouver, BC
> www.mwtech.com
>
>
>
> "Chris Tacke, eMVP" wrote:
>
>> You need a custom Setup.dll that resides on the device.
>>
>> --
>> Chris Tacke
>> Co-founder
>> OpenNETCF.org
>> Are you using the SDF? Let's do a case study.
>> Email us at d c s @ o p e n n e t c f . c o m
>> http://www.opennetcf.org/donate
>>
>>
>> "Robert W." <RobertW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:0B1D3805-A247-4ECD-A47C-2F1900E88A64@xxxxxxxxxxxxxxxx
>> > I'm trying to figure out how to remove extra files & folders and
>> > registry
>> > settings that get created post installation.
>> >
>> > I've correctly followed the steps in the following article to build a
>> > custom
>> > installer:
>> > http://www.codeproject.com/netcf/PackagingAndDeployingPPC.asp
>> >
>> > And I've now been reading this related article:
>> > http://www.codeproject.com/ce/setupdll.asp
>> >
>> > So it seems clear that I need to add some code to my
>> > CustomInstaller.dll
>> > to
>> > do the extra cleanup. But in my situation I've chosen not to use the
>> > MSI
>> > file because my app will see users installing the mobile component on
>> > dozens,
>> > if not hundreds, of Pocket PCs. So I built my own installation engine
>> > to
>> > streamline the process.
>> >
>> > My question is this: Is my CustomInstaller (with the 2 special install
>> > and
>> > 2
>> > special uninstall events) utilized by the generated CAB files or only
>> > by
>> > the
>> > MSI file? If the latter then is there a way for me to still get the
>> > Pocket
>> > PC Remove Programs function to utilize it?
>> >
>> > --
>> > Robert W.
>> > Vancouver, BC
>> > www.mwtech.com
>> >
>>
>>
>>


.

Relevant Pages

  • Re: The annoying VSTO 2003 message "The current .NET security poli
    ... You have to add a new project to you're solution that will create a dll. ... I have one project dll and one template Excel file. ... within the Charts folder I have a sub-folder called Chart_bin ... Interop Assembly) for .NET selected during installation. ...
    (microsoft.public.vsnet.vstools.office)
  • Re: Cant use web links from messages
    ... What registering a DLL does is add/update some entries in the registry. ... That's necessary if some other program deleted or modified the registry entries. ... > Choose 'Extract One File From Installation Disk'. ... >> How to Make Internet Explorer the Default Web Browser ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • RE: KB898461 consistently fails to install
    ... To fix the .dll issue, you will need to re-register a couple of .dll files. ... REGSVR32 WUAPI.DLL ... that several aspects of the installation may have failed. ... to 0x80006060 but I think it didn't add any detail to the log file. ...
    (microsoft.public.windowsupdate)
  • Re: Web Part deployment
    ... I sure hope there is going to be better support ... The Bentley.ECOM.dll is a support DLL for the ... you are going to control the installation ... > Microsoft is providing this information as a convenience to you. ...
    (microsoft.public.sharepoint.portalserver.development)
  • RE: system.badimageformatexception returned from custom installer
    ... How do you invoke that dll from the customer action? ... The dll is created as a seperate project. ... Action dll by going to the custom actions tab and then by right clicking ... Yes it is an installer class. ...
    (microsoft.public.dotnet.framework)
Loading