Serious issues related to installing into Program Files

Hi all,

when testing our latest RC-setup we found that installing our software into ProgramFiles\OurFolder creates unexpected things to happen. Our program won't start or actually it starts, but no GUI appears. In other words the main process runs, but nothing happens. Not even the MS SQL logon when not having a valid connection string present. Installing into c:\AnotherFolder works fine. Also putting this "AnotherFolder" into Program Files afterwards. What could cause this to happen? We have no code signing what so ever, but why should this problem occur now? Our software is mainly Clarion based win32, partly .NET. All .NET exe starts like normal from Program Files, none of the Clarion win32 exe does. We tried to change manifest settings on our main exe using "generate default application manifest". We did a recompile of this single application and put it into the installed Program Files\OurFolder. Then the software starts as normal, but with a very outdated look on all controls...running the software right from the release folder also works like normal.

We desperately need some input on this as our customers are giving us a hard time waiting for their updates...

Christian,

of course, this has nothing to do with the installer at all. Is your own Clarion application UAC-aware?

If "c:\AnotherFolder" (not a protected Windows resource) works fine but the "Program Files" folder tree (a protected Windows resource) does not work, then you have a serious (UAC) issue in your own application ;-)

BTW, here is a very brief description of how to make an application "UAC-aware"

http://www.lindersoft.com/forums/sho...3976#post83976

Does this help?

Friedrich

Quick note: if your Clarion application does not work correctly from within the protected "Program Files (x86)" folder tree even with an embedded Win10 UAC manifest, run your application (just for fun) "elevated". Right-click the main .exe and select "Run as administrator". Then see if this works. If it does, it's an UAC issue. But this is just a test. According to the Windows Development Guidelines, the "mixed-mode" application has to work fine non-elevated and elevated.

Friedrich

Quote:

---

Originally Posted by linder

Quick note: if your Clarion application does not work correctly from within the protected "Program Files (x86)" folder tree even with an embedded Win10 UAC manifest, run your application (just for fun) "elevated". Right-click the main .exe and select "Run as administrator". Then see if this works. If it does, it's an UAC issue. But this is just a test. According to the Windows Development Guidelines, the "mixed-mode" application has to work fine non-elevated and elevated.

Friedrich

---

Hi Friedrich,

thank you very much for your comments. We will definitely look into the UAC-aware section asap. As for now, our problem is solved. My colleague had implemented NLog into our program suite. The NLog configuration file was, by mistake, set to create log files directly into the application's base directory (in other words ProgramFiles\OurFolder) ...that's not a very good idea! :-) Turned the logger off and now everything runs fine again! :D

--
Christian

Hi Christian,

PERFECT!!! :-) Thanks for the update.

Have a great weekend.

Friedrich

Quote:

---

Originally Posted by linder

Hi Christian,

PERFECT!!! :-) Thanks for the update.

Have a great weekend.

Friedrich

---

Thanks, the same to you. :-)