Empty long named directories created under WINNT folder

  • Thread starter Thread starter Jorge Balderas
  • Start date Start date
J

Jorge Balderas

The .NET Framework seems to be generating empty directories with long unique
names every time a Windows Forms application is ran. The owner of these
directories is the user launching the application, these users have write
permission on the WINNT folder, but no Modify permission. My guess is that
the .NET Framework needs to generate these directories (to JIT compile the
assemblies maybe?) and is failing to delete them because the user has no
Modify permission. I have read posts (see link below) about very similar
behavior under ASP .NET, and I was wondering if anyone had seen this
behavior for Windows Forms apps, its cause or workarounds (other than
granting modify permissions) for this issue. By the way, the reason for this
awkard set of permissions is because this application is being accessed
remotely through Citrix.

Thanks,
Jorge

ASPNET temporary directories
http://groups.google.com/[email protected]
 
Hi Jorge,

It might be related to isolated storage if the machine was upgraded from NT
4.0, check out MSDN documentation on isolated storage.

Sijin Joseph
MCP Visual C#
 
Back
Top