Sign in to follow this  
Jarwulf

Environmental variables win 7

Recommended Posts

Jarwulf    223
I'm having trouble setting environmental variables for VS 2008 in windows 7. I'm under a limited user account and when I go to the environmental variables section I get prompted for the password from the admin. Well once there I see a list for admin user variables and system variables. I then enter in ENV_VAR and the location under user variables or system variables. However once I go back to VS2008 and put in $(ENV_VAR)\include in the VC++ directories they don't seem to solve any of the errors and I have to reenter in the plain location.

Share this post


Link to post
Share on other sites
frob    44902
I'd fix the limited user account thing first.

You won't get far in software development with that account. Debugging without privileges is going to be a bit hard.

At the very least you'll need your limited user to be added to the "Debugger Users" group. You will also probably access to several restricted folders and the ability to install SDKs and other big pieces of software, but might get away with it if you are only starting out with simple 'hello world' type apps.

It would be much easier and better overall to simply have a proper local machine administrator account, which is basically required for almost any serious software development.



To simply change your environment variables as a limited user, Google suggests:

[quote][font="Calibri, Helvetica, Arial, sans-serif"][size="2"]To edit your own personal environment variable list, you must use the following method: Click Start, Control Panel, User Accounts and Family Safety, User Accounts. In the task list at the left side, click Change My Environment Variables. You will be able to edit only the upper (personal) environment variable list.[/quote][/size][/font]
[font="Calibri, Helvetica, Arial, sans-serif"][size="2"][font="arial, verdana, tahoma, sans-serif"] [/font][/size][/font]

Share this post


Link to post
Share on other sites
mhagain    13430
...on the other hand, developing as an admin introduces the serious danger of writing code that will only work for an admin account. So if you go down that route be sure to add "test while logged on as a limited user" to your test plans.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this