ClickOnce error: Value does not fall within the expected range

后端 未结 15 1443
旧时难觅i
旧时难觅i 2020-12-01 01:08

Getting this error on ALL ClickOnce application launches for a certain user. This started happening after a version upgrade (but happens to no one else).

I\'ve trie

相关标签:
15条回答
  • 2020-12-01 01:51

    I tried a simple configuration. Go to the project -> properties -> application ->

    check the icon and mainfest, select an icon next to the option embed manifest with the default configuration

    good luck

    0 讨论(0)
  • 2020-12-01 01:52

    Curiously, I had the same issue and it was resolved by simply logging in as another user and installing/running the app. When I logged out and then logged in as the original user it all worked again.

    0 讨论(0)
  • 2020-12-01 01:54

    My problem was caused by a change in the csproj file. a reference to an assembly was changed from:

    HintPath>..\Files\

    to

    HintPath> .. \ ..\Files\

    which added a dependency xml element in the manifest file.

    editing the csproj file and publishing, fixed the manifest file.

    0 讨论(0)
  • 2020-12-01 01:58

    I solved my exception

    System.ArgumentException
        - Value does not fall within the expected range.
        - Source: System.Deployment
    

    Check if the reference has Copy Local= true . For example , my problem was Office reference on true. When it tried to copy it , a conflict occurred, so it couldn't open the program. Hope this solves your problem.

    0 讨论(0)
  • 2020-12-01 01:59

    You can try this:

    rundll32 %windir%\system32\dfshim.dll CleanOnlineAppCache
    
    0 讨论(0)
  • 2020-12-01 02:03

    i have been searching for a clean solution for this problem for a while. I could fix it couple of times by trial and error. Finally i could able to nail down exact issue. I thought of sharing it here.

    Above error tells it can't find a matching file in deployment folder.

    If you are facing this problem for an update check following.

    1. Download application.exe.manifest file from the deployment which is working.
    2. Compare current version of application.exe.manifest file with old one.
    3. Look for any reference added/removed/changed. if you see anything suspicious, manually edit/rollback that part of manifest and try, most cases it will work.

    If new Upload

    Check you have all assemblies marked as 'copy local=true' got in deployment folder, also check its size once uploaded.

    because 'copy local = false' assemblies will be treated as prerequisites in clickonce engine. Most of the application launch problem starts from there.

    0 讨论(0)
提交回复
热议问题