1

I am a bit confused. I have a C # WPF application. This works as I wish when I run the EXE file.

Now I have set up an installer (Visual Studio Installer project). This installer installs the application as desired and creates a desktop shortcut.

If I start the application now via the desktop icon, then installer is executed again and it is asked for the admin access data. After entering the data, the application starts directly. And that happens every time I click on the desktop icon.

I use in the application project the costura.fody package to bind one executable.

Have someone ideas whats wrong?

I've read the desktop icon from Visual-Studio-Installer-Project check always the application state. I think this is why the installer start every time I click the app icon on the desktop.

Stein Åsmul
  • 39,960
  • 25
  • 91
  • 164
Marcus
  • 654
  • 1
  • 8
  • 19

1 Answers1

1

Short Answer: This is an MSI self-repair problem.

  1. Work out what component triggers the self-repair. Details below.
  2. Correct the situation by making changes to the setup eliminating the conflict situation.

Self-Repair: This is self-repair, or self-healing or "resiliency" depending on who you ask. I have a description here: Why does the MSI installer reconfigure if I delete a file? Towards the bottom there are three links. I would go for the one saying "how to avoid in your own package".

Understanding: There is a longer explanation of self-repair here. Section "The Primary Causes of Self-Repair" explains 3 main causes, yours being the first one.

Culprit: You should check the event log for clues as to what file / component is triggering the self-repair:

Once you have worked out what component triggers the repair there are a variety of fixes. But first maybe check the list of common mistakes in your own package.

Previous Answer: Come to think of it there are several previous answers:

Stein Åsmul
  • 39,960
  • 25
  • 91
  • 164
  • Ok, thanks for the tips. I found missing registry keys in Event Viewer. By default, registry keys are set in a Visual Studio Installer project (`HKEY_CURRENT_USER\Software\[Manufacturer]`). These are not needed by me and so I deleted the keys in the installer project. Now everything works as expected. – Marcus Jun 11 '19 at 08:21