ClickOnce Errors with C# Express Final


  • Hi gang,

    My ClickOnce-deployed application, which used to work fine back in the beta-2 days, is now giving everyone who tries to install it a lot of headaches.

    When I deployed this version (made using the final release of Visual C# Express) I deliberately put it in a different folder on my web server, so there could be no "accidental" upgrades from beta users.

    My users have meticulously uninstalled the beta version of my program, as well as the framework. Some have even run the pre-RTM removal tool from MS.

    What errors am I seeing? Well:

    - A machine at work (which never had beta 2 on it) that I tried it on today simply appeared to stop installing just as the .NET 2.0 framework had finished. I had to repeatedly click on the "Install" button on the publish.htm page to kick off the install today.

    - A test PC here at home (which *did* have beta 2 on it, but has been cleaned) seemed to reboot for no reason just after the .NET 2.0 framework finished installing

    - One of my users' PCs apparently did the same (hard reboot for no reason)

    Is there someone out there in MSDN land who can try installing my program and see if it errors for them; maybe give me an idea of where to look to get it working? The publish page is here:


    Wednesday, November 9, 2005 10:44 AM

All replies

  • Hi Matt, I just installed your app from this location and it installed fine without any problems on final released .NET Framework 2.0 runtime. btw, cool app!

    It's hard for me to pinpoint exactly what's causing the failures you're seeing. For issues with activating the app I'd recommend trying as two step process - first install the .NET Framework 2.0 (via bootsrapper setup.exe package or directly running dotnetfx.exe) and see if that works, then launch ClickOnce app by clicking on link to .application file. This will help narrow down whether the issue you're running into is during the bootstrapper stage or in the core ClickOnce runtime engine itself.

    The reboot after .NET Framework installed was probably because a component was still in use (most likely mscoree.dll) and so Windows Installer prompted for reboot.

    Thursday, November 10, 2005 6:33 PM
  • Thanks for the reply, Sameer (and thanks for the kind words about the app).

    I will pass on the idea of installing the framework separately to those who are still having trouble (I have since found out that some people have been able to install it without hassles).

    The reboot thing worries me because there is no prompt. The machine simply cold-boots unexpectedly.

    Thursday, November 10, 2005 8:17 PM
  • All right. All but one of my beta testers have been able to install the final release of my program. I'll paste in here the log from the one who can't install it.

    He has installed dotnetfx 2.0 from MS's site, rather than relying on ClickOnce, but when he clicks "Install" on my publish.htm page he still gets an error "Application cannot be started" with a log file whose beginning I will paste below. Can anyone help?

     Windows    : 5.1.2600.131072 (Win32NT)
     Common Language Runtime  : 2.0.50727.42
     System.Deployment.dll   : 2.0.50727.42 (RTM.050727-4200)
     mscorwks.dll    : 2.0.50727.42 (RTM.050727-4200)
     dfdll.dll    : 2.0.50727.42 (RTM.050727-4200)
     dfshim.dll    : 2.0.50727.42 (RTM.050727-4200)

     Deployment url   :
          Server  : Microsoft-IIS/6.0
          X-Powered-By : ASP.NET
     Deployment Provider url  :
          Server  : Microsoft-IIS/6.0
          X-Powered-By : ASP.NET
     Application url   :
          Server  : Microsoft-IIS/6.0
          X-Powered-By : ASP.NET

     Deployment Identity  : Comicster.application, Version=, Culture=neutral, PublicKeyToken=1e73ec0f88ccb72b, processorArchitecture=msil
     Application Identity  : Comicster.exe, Version=, Culture=neutral, PublicKeyToken=1e73ec0f88ccb72b, processorArchitecture=msil, type=win32

     * Installable application.

     Below is a summary of the errors, details of these errors are listed later in the log.
     * Activation of resulted in exception. Following failure messages were detected:
      + The application binding data format is invalid. (Exception from HRESULT: 0x800736B2)

     * Transaction at [11.10.2005 11:51:41 PM]
      - Installation of deployment (, Version=, Culture=neutral, PublicKeyToken=1e73ec0f88ccb72b, processorArchitecture=msil) did not succeed.
      - Setting one or more of the deployment metadata did not succeed.

     There were no warnings during this operation.

     * [11.10.2005 11:51:16 PM] : Activation of has started.
     * [11.10.2005 11:51:20 PM] : Processing of deployment manifest has successfully completed.
     * [11.10.2005 11:51:20 PM] : Installation of the application has started.
     * [11.10.2005 11:51:21 PM] : Processing of application manifest has successfully completed.
     * [11.10.2005 11:51:25 PM] : Request of trust and detection of platform is complete.
     * [11.10.2005 11:51:40 PM] : Downloading of subscription dependencies is complete.
     * [11.10.2005 11:51:40 PM] : Commit of the downloaded application has started.

     Following errors were detected during this operation.
     * [11.10.2005 11:51:41 PM] System.Runtime.InteropServices.COMException
      - The application binding data format is invalid. (Exception from HRESULT: 0x800736B2)
      - Source: System.Deployment

    Friday, November 11, 2005 8:00 AM
  • Looking at the log file this appears to be an error caused by some old beta2 files still lying around in the app store. I'd recommend clearing out the store directory to get machine to clean state and try again.

    To nuke the store delete the folder %userprofile%\Local Settings\Apps.


    Friday, November 11, 2005 9:59 PM
  • Thanks again, Sameer. I will pass it on and report back!
    Friday, November 11, 2005 11:45 PM