Welcome to the sandbox <g>...

That's not quite correct. It depends on where the application was started from. An application started on the local machine by default has full control of that machine. this means Web Services from any site and the ability to write to disk.

However, if you start an application from the network, by default your rights are limited to that network location and you cannot write to local disk.

There are ways around this, such as setting the security environment for speciifc locations or specific applications with the security administrator or using isolated storage which is a stream based file substitute that allows you to persist data without access to the file system.

Bottom line is network applications have next to no rights unless you mess with the security policies...

It'll be fun to see how this pans out for applications that need to run over the network. Microsoft claims this will make life easier for administrators. I see this is as nothing less than a full on configuration nightmare trying to hunt down all the levels of configuration that are available for each app...

We'll see...

+++ Rick ---


>Another of these 'somebody told me this is true'...I wasn't able to reproduce it, but figured I'd ask.
>
>Someone told me that if a WinForm app is utilizing Web Services (say, to access a layer that's connected to SQL Server), that while 'connected' to a Web Service, the WinForm cannot write information to the local hard disk. Apparently, it is because of a new security model in .NET.
>
>This sounds pretty crazy, as a WinForm that is utilizing a Web Service might need to write data locallly (like store user selections, user preferences, etc.)
>
>Can anyone shed any light on this?
>
>Thanks,
>Kevin