Closed coder925 closed 3 years ago
[Triage] Please investigate.
@NikolaMilosavljevic , thank you for looking into this. Were you able to reproduce the issue?
Please let me know in the case I'm doing something wrong or if there is any other workarounds. For now, I'm deploying my app with -Install false
. However, I'd like to switch to an installed app as soon as I can get the updates to work. Thanks!
@coder925 apologies for the delay - I will try to repro this today.
@coder925 I was able to reproduce this issue.
However, if I modify your deploy-next.bat
script to replace -mv %coVersion
with -i true
you will get the correct update experience, for all app updates.
I will debug why -mv
option does not produce the expected outcome.
@NikolaMilosavljevic , good that you were able to reproduce it and thanks for the found workaround!
In my specific case unfortunately, I cannot skip the -mv
option. Whenever there is an update available, my clients must update in order to be allowed to run the app. Hopefully it can be fixed.
@NikolaMilosavljevic , did you find the bug? If so, when do you believe a fix can be released?
@NikolaMilosavljevic , did you find the bug? If so, when do you believe a fix can be released?
@coder925 it seems that old .NET FX tool 'Mage' generates the exact same ClickOnce manifest. I expect the issue to exist there as well. Is this a regression from .NET FX?
@NikolaMilosavljevic , I have only tested with dotnet mage
on .NET 5.0. I don't know about the other versions.
@NikolaMilosavljevic , I have only tested with
dotnet mage
on .NET 5.0. I don't know about the other versions.
It seems that this issue has always existed in Mage tool, even in old .NET FX.
It is blocking simultaneous usage of -i
and -mv
, so it essentially allows specifying minimum version for online apps only, which seems incorrect. I think the tool should only block combination of -i false
and -mv
. I need to investigate this further.
Interestingly, this issue does not exist if app is published from Visual Studio.
Description
I'm running
dotnet mage
to publish deployments, but the client is only updating one time. (UpdateOnce :relaxed:)I'm expecting the client to always update to the latest required version if there is a newer version available. This is regardless how often new updates are released.
Steps to reproduce:
dotnet mage -cc mkdir c:\temp\%appName% cd c:\temp\%appName% dotnet new wpf -f net5.0 dotnet publish -o publish/%coVersion%/ cd publish dotnet mage -al %appName%.exe -td %coVersion% dotnet mage -new Application -t %coVersion%\%appName%.manifest -fd %coVersion% -v %coVersion% dotnet mage -new Deployment -i true -pub "Test Publisher" -v %coVersion% -appm %coVersion%\%appName%.manifest -t %appName%.application -pu %providerUrl% xcopy . %sharedFolder% /S /Y start %providerUrl%
set coVersion=1.0.0.1 set appName=TestApp1 set sharedFolder=\comdev1\clickonce set providerUrl=%sharedFolder%\%appName%.application
cd c:\temp\%appName% dotnet publish -o publish/%coVersion%/ cd publish dotnet mage -al %appName%.exe -td %coVersion% dotnet mage -new Application -t %coVersion%\%appName%.manifest -fd %coVersion% -v %coVersion% dotnet mage -new Deployment -mv %coVersion% -v %coVersion% -pub "Test Publisher" -appm %coVersion%\%appName%.manifest -t %appName%.application -pu %providerUrl% xcopy . %sharedFolder% /S /Y