I am a bit confused about using isolated storage on an IIS server.
I understand the purpose of isolated storage: it provides a safe place to store data without worrying about how and where this place is.
Since isolated storage has a by-user and by-assembly approach, I'm not too alone in using it on an IIS server, where applications have almost their own identities. I really did not see any interest in impersonating a web application and almost never saw self-named web applications, but this is my point of view.
Using isolated storage on a server means (for Windows Server 2003):
Using isolated storage in \Documents and Settings\<user>\
Which means \Documents and Settings\Default User\when the application pool belongs to the local system or network services, I think
Which also means write permissions in this folder for local system or network services.
Using impersonation
As for the web application (logic), these ideas confuse me ... Document and settings? Default user? Enable impersonation only for storage? No control over server storage? AND?
Some points on MSDN:
Server memory . Server applications can use isolated storage to provide individual stores [...]. Because isolated storage is always shared by the user, the server must impersonate the user making the request. [...]
, .
, , , , [...] . ? . IIS (Windows 2003).
: System.IO.Packaging ( ) - ? IO.Packaging , ?
? - ?
/ IIS, , ββ, .
, " IIS" anwser.
!