All geek questions in one place

Testing ClickOnce Applications

What method would you use to test a new version of the ClickOnce application (next to the current version) among several users? Are there any best practices (especially since the applications depend on different servers for live / test versions of SQL / web services, etc.).

We use internal DNS to configure http: //application.ourdomain.test sites for testing web applications. You can see from the address bar that you are logged in to the test site, and this is just changing the connection string to force this deployment to connect to our test SQL server. Is there any way to get closer to this?

+3
source share
2 answers

To test ClickOnce deployment, we configured several virtual machines and connected testers using Remote Desktop. The VM desktop background is an ugly color and says "TEST" in big bold red letters.

In addition, all of our applications display a warning message if the user is about to connect to anything other than the production database.

+1
source

Today I met this link text today, which seems to offer a way to do this - you have to use different certificates to sign the manifest. I change the package name in the Publish Settings dialog box to create different menus.

+1
source

Source: https://habr.com/ru/post/1334075/

More articles:


All Articles