Using Microsoft’s ClickOnce technology, we publish our application to an in-house LAN server for unattended installations; the users can simply type something like the following into their browser address bar:
//inHouseServer/apps/app1/publish.htm
and the application files are downloaded and installed onto their computers, and any prerequisites are fetched; in our particular case, the prerequisites are Microsoft .NET Framework runtime downloaded automatically from microsoft.com.
The program crashes in the Sandbox. We would therefore like to know
-
Is it possible to designate //inHouseServer as a trusted file origin/source, so the application will pass muster and avoid AutoSandboxing because “The file origin/source is suspicious” and/or “the file is executed from a remote/removable media”?
-
Is it possible to tell Avast to look at the certificate issued which Visual Studio “signs” the app with, so that it avoids AutoSandboxing because “the file prevalence/reputation is low”? Can we artificially “pump up” the reputation of the files?
Thanks