%TEMP% Env Variable

Hot Topic

Guidance Needed on User Interface Process Application Block (UIPAB) - Starting a Open Navigation Task
Software architecture... I'm stuck!
seperate rule engine need
Architecting a System is a Thought Process or Practice or Combination of both of these or others too
Databinding vs Multi-tier
OO design question.
Database Bytes per LOC
Architecture for Product Development
Limit processor frequency in windows
Why use an application server?

Architecture

Adding EntLib 2.0 to a Solution, what would be the best practice?
Designing Databases for SOA
windows scheduler - who gets the CPU?
UI Design: Edit then List vs List then Edit
General business object requirements
Client Server Application
Proportional fonts
Have you tried NHibernate?
Design pattern for interactive communications between users
Stored Procedure Reporting?

%TEMP% Env Variable

Is there a need for having multiple values for the System's %TEMP% variable From a design point of view, is it safe to assume it as a single valued variable

Incase it is a multi-entry variable is there a registry entry or some reference that separates the %TEMP% value created by Windows and %TEMP% value created by a 3rd party program How can I make sure that I use the one that is defaulted/created by Windows

Thanks in advance!




Answer this question

%TEMP% Env Variable

  • Simon Honeybone

    In .NET it's safer to use Path.GetTempPath(), it will deal with retrieving values from the TEMP env. variable if needed.

  • T.C.

    when I access the environmental variables through .NET, it gets the User related %TEMP%. No problem there.,

    My main concern is if the variable is designed for supporting multiple values for example:

    "C:\DOCUME~1\yourprofile\LOCALS~1\Temp;C:\Program Files\Microsoft SQL Server\80;C:\TEMP"

    or is it just always expected to have a single value, example:

    "C:\DOCUME~1\yourprofile\LOCALS~1\Temp"

    Should I ever expect multiple values for %TEMP% variable in my program logic



  • Loup

    I think this would have usability implications… and most certainly privacy implications as well; both are better addressed with a unique %TEMP% value for each user context.

    Dan
  • %TEMP% Env Variable
Answer this question