7

In a proper installation of an average software, its executables would be in the program files folder; its user data in the user's application data folder; it's non user specific data in the all users application data folder; and it should usually be able to run under non-administrative privileges. These guidelines could easily be ignored on XP, but they are an issue on Vista and 7 due to UAC.

We're on the verge of releasing a major version of our software. It's a CMS, used by our clients as their main work tool, and their IT staff are well familiar with it. If we want to be fully compatible with Windows 7, we have to make quite a few changes, and we're already on a tight schedule.

Question is: we can easily have our clients install our software outside of program files, or have them run it as administrators. I think it's wrong, but I need some ammunition: why should we install on program files, with all the limitations that come with it?

EDIT:

  1. I'm asking this here because I'd like to get IT guys input. For programmers input I can just ask the guys next to me instead of stackoverflow. This is NOT a programming question.
  2. I'm asking this because we'd like to make our software better. Old installation habits go back about 15 years, when the software was first created. Fixing its installation is a matter of priorities, nothing else. Worse comes to worse, it'll be postponed to the next version.
Eran
  • 267

4 Answers4

2

Technically: Yes.

Logically: No

Business wise: I know a lot of companies that would throw you out based on obvious quality issues. Even if you do not certify for windows, you should not blatantly violate common sense and guidelines.

I personally would return the software as faulty and bill you for every minute we spent with it - due to gross neglect.

Someone on your end obviously messed up and never read how to program windows. Happy fixing ;)

So, at the end: It is going to cost you. ESPECIALLY in a CMS area - highly competitive.

Sirex
  • 5,585
TomTom
  • 52,109
  • 7
  • 59
  • 142
2

You should read ALL of the following reference material before making your decision. It's a lot, but then you wanted to write Windows apps so...

Windows User Experience Interaction Guidelines

Windows 7 and Windows Server 2008 R2 Application Quality Cookbook (Windows)

Certification requirements for Windows 8 desktop apps

John Homer
  • 1,343
1

15 years ago was when Windows 95 introduced "Program Files" to the world. A lot of installers back then failed because of the space in the path. I remember what a pain it was for us but after a week's work it was done and everyone was happy.

I'm with TomTom, you are really showing that you are not in touch with Windows standards. Lots of assumptions are made about "program files" in modern times, e.g. anti-virus programs assume that's where the applications are and treat apps outside of that as different. The new default security settings on directories will also start to cause you grief and phone calls. And what's the point of the customer upgrading to Windows 7 if you insist on bypassing the security?

BTW: never assume you are entrenched. If Windows 7 is more important to them than you are they will toss you out. Senior executives make the weirdest decisions, often based on the what you think are trivial issues but to them it's a sign to get rid of your app.

jqa
  • 451
  • 2
  • 7
0

This has nothing to do with system administration but quite frankly, this issue should never have cropped up in the first place. Had the software been built and packaged by someone familiar with Windows it would have been put in the right place in the beginning, making this a non-issue. Having to fix it now is the price to be paid for ignoring convention and good practice.

If it was up to me the software would be rebuilt and repackaged correctly, which should be a trivial job and I can only wonder why it's even being discussed.

Just one question. What limitations do you see in installing software where it is intended to be?