0

When we create a SetUp & Deployment project for our application in .net, the default folder for our application to be installed is being set as C:\Program Files..... Our application will run perfectly if we are using a Windows XP machine. But if we are using a Windows Vista or Windows 7 machine, the application wont run perfectly, especially if we are performing any file operations in our application...

Can anyone find a solution for this problem? Is there any means to penetrate this User Account Control and File Access Controls of Windows 7? or can any1 give a choice to change the default installation folder from [ProgramFilesFolder]\[Manufacturer]\[ProductName] to some other folder?

edorian
  • 38,542
  • 15
  • 125
  • 143
Rohit R Keyan
  • 1
  • You did not provide nearly enough information in your question. Primarily - what do you mean by "won't run perfectly"? What is the issue? Exceptions? Errors? – Oded Sep 05 '10 at 06:40
  • application will run.. my app includes many file operations, for example, licensing, while i add licence file 2 my application, it happens 2 be a problems. In short file operations cannot be performed if iam installing my application in [ProgramFilesFolder][Manufacturer][ProductName]. but ther is no problem if im installing it in another directories such as "C:\Myapp\New\".. – Rohit R Keyan Sep 05 '10 at 06:49
  • Can you please edit your question and add the relevant details to it directly instead of adding them as comments? – Oded Sep 05 '10 at 06:51

5 Answers5

3

If your application writes to any files under its install folder (i.e. under Program Files if default path is used), then it is badly written. You shouldn't try to circumvent OS security mechanisms to protect the user from badly written apps; you should rather fix your app so that it works correctly.

And it is, of course, not a .NET issue at all. Any application doing the same thing, no matter which language/framework it's written in, will have the same problem.

Pavel Minaev
  • 99,783
  • 25
  • 219
  • 289
  • Can u give a solution to fix that bug while we are developing such applications? – Rohit R Keyan Sep 05 '10 at 06:50
  • i mean , i want 2do file operations with my application, but its not necessary that my application should be installed in "C:\Program Files\" – Rohit R Keyan Sep 05 '10 at 06:52
  • You can "do file operations", just constrained. Specifically, you can _read_ anything in your app folder. You cannot write there, though. You can write in other places (e.g. "My Documents" of the user currently running your app). – Pavel Minaev Sep 05 '10 at 08:15
1

You should still install your application in Program Files folder. there are good reasons to have it there - a single copy for all users, in a well known locked place where nobody but an admin can tamper with your binaries.

However, any file operation you are doing should be in one of the standard Windows locations for user-writable files. There are several such folders, depending on the file usage model. You can read more about these in the following SO questions :

My winform app uses xml files to store data, where should I store them so Vista users can write to them?
Vista and ProgramData

Community
  • 1
  • 1
Franci Penov
  • 74,861
  • 18
  • 132
  • 169
1

Data shared among all users should go in C:\ProgramData (use Environment.GetFolderPath(Environment.SpecialFolder.CommonApplicationData) to find out where it actually lives -- it can be different between Windows versions).

Data specific to the user should be in SpecialFolder.ApplicationData. If the user has a roaming profile, this is shared between machines.

Data specific to the user that's also specific to the machine should be in SpecialFolder.LocalApplicationData.

If you really need to put something in your program's installation directory, you need to do this with Administrator privileges.

You should either do this by prompting for elevation the first time that the program is run. Preferably, you should do this during installation (because you're already elevated).

Roger Lipscombe
  • 89,048
  • 55
  • 235
  • 380
1

First of all, you should not set your app to install under C:\Program Files\..., you should instead set it to %PROGRAMFILES%\... While these will usually equate to the same thing, they can be different on a 64 bit system, or they can be wildly different if the system has been set that way.

As already mentioned, don't try to circumvent the UAC, it is there for a reason, and your program is no more special than any other program on the system. Instead what you should do is set your app manifest to demand administrative level permission upon launch (which if granted bypasses the file system virtualization, although the user can decline it or possibly not even have the rights to launch something as admin). The other thing you can do is set the ACLs on the folder that your app sits in, and give all users on the machine read/write access to that folder (this would have to be done at install time).

Or you can do things the proper way and store your data files in the %APPDATA% folder, which you have full rights to, although these folders are specific to each individual user of the system.

slugster
  • 49,403
  • 14
  • 95
  • 145
0

I'd suggest start here http://channel9.msdn.com/pdc2008/PC51/

That will give you a good foundation.

Erik Funkenbusch
  • 92,674
  • 28
  • 195
  • 291