Home/ Questions/Q 648859
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T21:52:43+00:00

for automatic update of my WPF application, I’ve this strategy : (1) process.exe starts

  • 0

for automatic update of my WPF application, I’ve this strategy :

  • (1) process.exe starts
  • process.exe looks for update => there’s an update
  • process.exe makes a copy of itself => process_copy.exe
  • process.exe launch process_copy.exe with “update” parameters
  • process.exe exits
  • (2) process_copy.exe starts
  • process_copy.exe see the “update” parameters, download update to process.exe
  • process_copy.exe launch process.exe
  • process_copy.exe exits
  • process.exe starts

Note that my application use a dll.

this strategy is working, except some times (not everytime) when the application is launched at startup in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Sometimes it crashes at (2), with a

System.IO.FileNotFoundException was unhandled
Message=”Could not load file or assembly ‘ManagedWinapi, Version=0.3.0.0, Culture=neutral, PublicKeyToken=null’ or one of its dependencies.

I don’t understand why it can crash.
If it can start in (1), why can’t it (sometimes) start in (2) ?

Do someone have an explanation ?

Thanks in advance for your answer

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Finnaly, I’ve integrated this dll in my application, so I have no dll more … that’s ugly but working

    • 0