Stack Overflow Asked by eek on December 7, 2021
I have a C# application that is published via ClickOnce to a network drive. I have another process that I use to launch this application via the code below that points to the ClickOnce shortcut:
string path = "Z:\MyApp\MyApp.application";
var process = new Process();
process.StartInfo.FileName = path;
process.Start();
This code has worked forever on Server 2008 R2 without any issues. As soon as I upgraded to Server 2019, it is no longer consistently reliable. There are no errors thrown. Nothing happens when I try it…
unless I launch any ClickOnce application right before this from the same mapped drive. Right after, Process.Start()
will suddenly start working for all applications I want to launch until it eventually fails again a few hours later. The drive mapping is not being lost during this time. My guess is it is a security issue, but this system as well as previous ones have all been running under the local Administrator account. Neither is on any domain.
This only impacts ClickOnce .application
links. Any direct .exe
files I try to launch from the same network drive work just fine.
Get help from others!
Recent Answers
Recent Questions
© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP