Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clickonce - conditionally updating update location #284

Open
statler opened this issue Jul 11, 2023 · 6 comments
Open

Clickonce - conditionally updating update location #284

statler opened this issue Jul 11, 2023 · 6 comments
Labels
area-ClickOnce enhancement New feature or request question Further information is requested

Comments

@statler
Copy link

statler commented Jul 11, 2023

This is a bit of a fishing expedition here as I am trying to understand if this is possible, and if so how I might start investigating. We have an app that is updated from a central location. We also have a series of Clients, each with their own azure app services. We are wanting to move our installer so it is updated from each Client's app service rather than just having one installer for all Clients. We would then deploy our app automatically to each Client's app service. Obviously this enables us to deploy early versions to Client's with specific bugfixes etc. without affecting the general environment.

I know it is possible to change the deployment location after deployment by just updating the property between updates. Is it possible to conditionally do this - e.g. update the manifest client side based on a database setting, thus rewriting the UpdateUrl with an updated location? I think technically this should be OK as it doesn't change the ApplicationId

@ghost ghost added the untriaged label Jul 11, 2023
@jeffschwMSFT
Copy link
Member

@statler is this related to .NET Framework? For .NET Framework, our Visual Studio developer community is the best way to get questions like this answered.

https://developercommunity.visualstudio.com/home

@jeffschwMSFT jeffschwMSFT added the question Further information is requested label Jul 12, 2023
@ghost
Copy link

ghost commented Jul 12, 2023

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

This is a bit of a fishing expedition here as I am trying to understand if this is possible, and if so how I might start investigating. We have an app that is updated from a central location. We also have a series of Clients, each with their own azure app services. We are wanting to move our installer so it is updated from each Client's app service rather than just having one installer for all Clients. We would then deploy our app automatically to each Client's app service. Obviously this enables us to deploy early versions to Client's with specific bugfixes etc. without affecting the general environment.

I know it is possible to change the deployment location after deployment by just updating the property between updates. Is it possible to conditionally do this - e.g. update the manifest client side based on a database setting, thus rewriting the UpdateUrl with an updated location? I think technically this should be OK as it doesn't change the ApplicationId

Author: statler
Assignees: -
Labels:

question, area-Meta, untriaged, needs-area-label

Milestone: -

@statler
Copy link
Author

statler commented Jul 13, 2023

No this isn't about .Net framework, this is about .Net 7 clickonce deployment.

@jeffschwMSFT
Copy link
Member

Thanks for clarifying. I think this may need to go to winforms repo. But adding @leecow and @merriemcgaw to see who can best help out.

@leecow
Copy link
Member

leecow commented Jul 13, 2023

@NikolaMilosavljevic may have an idea.

@NikolaMilosavljevic
Copy link
Member

@statler my understanding is that you would like to modify the deployment manifest of the app, on user's machine - i.e. in ClickOnce store (cache). Is that correct? I'm not sure if ClicKOnce runtime would see this as an app integrity violation, but it might technically work only if manifest is unsigned. We do not recommend deploying unsigned apps.

cc @Tanya-Solyanik

@NikolaMilosavljevic NikolaMilosavljevic transferred this issue from dotnet/runtime Jul 25, 2023
@NikolaMilosavljevic NikolaMilosavljevic added enhancement New feature or request and removed untriaged area-ClickOnce labels Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-ClickOnce enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants