none
App updating only with desktop shorcut and starting only from installation directory RRS feed

  • Question

  •  Hi everyone!!!
    I'm having trouble with an app deployed with ClickOnce technology. Thing is it only receives updates when I use the desktop shortcut (created by the installer), and only starts if I use the executable on the installation directory.
    The app it's being published in a server, on the intranet. The update location is just the same.

    I disabled SmartScreen filter, but nothing.

    EDIT: Problem solved. The app is now starting and updating from both shortcut and executable. But now i have another problem: I don't know what solved it xD. I suspect was one of this things:

    1 - Was a problem with the signing.

    2 - The server where the installation files are stored was updated, correcting a bug or something.

    If I find which was the exact reason, I'll come here to tell.

    This is what i get from the log, by the way:

    DETAILED EXECUTION FLOW
    [13:42:53] : Activation through dfsvc.exe started.
    [13:42:53] : Method Call : ActivateDeploymentWorker(C:\Users\emorales\Desktop\Tiempo.WPF.appref-ms|,True,,,) called.
    [13:42:53] : Method Call : PerformDeploymentActivation called.
    [13:42:53] : Activating through shortcut.
    [13:42:53] : Method Call : ProcessOrFollowShortcut(shortcutFile=C:\Users\emorales\Desktop\Tiempo.WPF.appref-ms|,errorPageUrl=) called.
    [13:42:53] : shortcutParameter=
    [13:42:53] : Shortcut Text=file://tsdt01/Deploy/Tiempo.WPF.application#Tiempo.WPF.application, Culture=es-AR, PublicKeyToken=1822f037b0d5f64f, processorArchitecture=msil
    [13:42:53] : Application family is already installed and Shell Visible.
    [13:42:53] : Method Call : PerformDeploymentUpdate called.
    [13:42:53] : UpdateOnStart=True,PendingDeployment=
    [13:42:53] : Start processing deployment manifest for update check : file://tsdt01/Deploy/Tiempo.WPF.application
    [13:42:53] : Method Call : DownloadDeploymentManifest called.
    [13:42:53] : SourceUri=file://tsdt01/Deploy/Tiempo.WPF.application
    [13:42:53] : DownloadOptions=null
    [13:42:53] : Method Call : DownloadDeploymentManifestDirect(file://tsdt01/Deploy/Tiempo.WPF.application) called.
    [13:42:53] : Method Call : DownloadManifest called.
    [13:42:53] : Method Call : DownloadManifestAsRawFile called.
    [13:42:53] : Method Call : DownloadSingleFile called
    [13:42:53] : DownloadQueueItem :  _sourceUri = file://tsdt01/Deploy/Tiempo.WPF.application,  _targetPath = C:\Users\emorales\AppData\Local\Temp\Deployment\0760W7TT.NLW\40A8EWZL.8MZ.application
    [13:42:53] : HttpWebResponse=ResponseUri=file://tsdt01/Deploy/Tiempo.WPF.application
    [13:42:53] : Method Call : ManifestReader.FromDocument(C:\Users\emorales\AppData\Local\Temp\Deployment\0760W7TT.NLW\40A8EWZL.8MZ.application) called.
    [13:42:53] : Schema validation passed.
    [13:42:53] : Manifest is parsed successfully.
    [13:42:53] : Semantic validation passed.
    [13:42:53] : Signature validation passed.
    [13:42:53] : Method Call : FollowDeploymentProviderUri called.
    [13:42:53] : Deployment manifest zone is not local machine. Zone = Intranet
    [13:42:53] : providerUri=file://tsdt01/Deploy/Tiempo.WPF.application,sourceUri=file://tsdt01/Deploy/Tiempo.WPF.application
    [13:42:53] : Deployment provider not followed.
    [13:42:53] : End processing deployment manifest.
    [13:42:53] : Method Call : SkipUpdate called.
    [13:42:53] : Update is not skipped.
    [13:42:54] : Method Call : ComponentStore.ActivateApplication(appId=[file://tsdt01/Deploy/Tiempo.WPF.application#Tiempo.WPF.application, Version=1.0.0.86, Culture=es-AR, PublicKeyToken=1822f037b0d5f64f, processorArchitecture=msil/Tiempo.WPF.exe, Version=1.0.0.86, Culture=es-AR, PublicKeyToken=1822f037b0d5f64f, processorArchitecture=msil, type=win32] ,activationParameter=,useActivationParameter=False) called.
    [13:42:54] : HostType=1
    [13:42:54] : Activating application via CorLaunchApplication.

    Any suggestions?



    • Edited by Zomcat Wednesday, July 10, 2019 3:44 PM
    Friday, June 14, 2019 6:18 PM

All replies

  • Hi,

    Maybe you can try to check the ClickOnce Trust Prompt Behavior. Here is the document you can refer to.

    How to: Configure the ClickOnce Trust Prompt Behavior.

    Regards,

    Kyle


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, June 17, 2019 9:59 AM
    Moderator