Link to home
Start Free TrialLog in
Avatar of Sid Price
Sid PriceFlag for United States of America

asked on

Windows 7 File creation issue

I am developing an application suite and one of the programs is started by the installer, which also places it in the start-up folder. When this application is started for the first time (by the installer) it discovers it does not have a configuration file and creates it. The problem is that the file permissions given to this configuration file prevent other applications in the suite being able to write to it.

If I delete the configuration file and restart the PC then when the application starts up it recreates the configuration file and permissions are good.

What is the best way to resolve this problem. I do not want to disable the auto-run of the application by the installer as this would mean the user would either need to start it manually for the first time or ask for a PC restart.
Sid.
Avatar of AndyAinscow
AndyAinscow
Flag of Switzerland image

Would this achieve what you want.
Create another small app which the installer will start.  The only job of this app would be to launch your 'real' app.  You 'real' app then deletes this stub app if it detects it.
ASKER CERTIFIED SOLUTION
Avatar of sarabande
sarabande
Flag of Luxembourg image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Sid Price

ASKER

sarabande, I was considering your idea of including a default file with the distribution, It may be the simplest solution, the only thing one would need to ensure is that uninstall (to make updates) should not remove this file because then the user would loose the current settings.
Thank you for helping my decision,
Sid.