The answer to the question is no, and you'll probably never notice until you reach tmpFFFF.tmp
and get an error. If this is on a webserver your operation is going to fail.
The path name used for temp files depends on the context. So if you're getting this error and it is an emergency condition you'll want to make sure you can quickly find correct tmp
folder.
Running as a console app on Windows 8 gives me a path in my local prpofile:
C:\Users\sweaver\AppData\Local\Temp\2\tmp4193.tmp
And in IIS with Load User Profile = True
for the AppPool I get :
C:\Users\APPPOOL_NAME\AppData\Local\Temp
And when Load User Profile = False
I get a more manageable :
C:\Windows\TEMP\tmp7C32.tmp
You want to clean your temp files right away to avoid this!