I am currently converting a Winforms application to a clickonce project for the autoupdating feature. Within this application, an event can be raised that calls a seperate project in the solution that is a console application which returns arguements to the WinForms application.
To get the path to the executable, I was using the following:
stringpath = string.Empty;
path = ConfigurationSettings.AppSettings["SMigratePathtofile"];
if ((path != null) && (path.Length != 0))
{
return path;
}
path = Environment.GetEnvironmentVariable("CommonProgramFiles");
return (path + @"\test\batch.EXE");
As I convert the project to a click once project however, this file will no longer exist in there common files. My question is, if my code does call an executable, what is the best way to deploy it with ClickOnce and how does ClickOnce support multiple projects in a singular solution?