I can't answer the SOAP question, but as to the security question, do this: Login in to your machine as a local administrator (you're not running as a local admin all the time, are you?) Open the .Net Framework configuration tool. Navigate to the Runtime Security Policy and choose the machine level (you could do this at the user level, but I like to keep it simple and the default policies are implemented at the machine level). Right-click on one of the code groups and choose New.. to create a new code group. Give the code group a name and description, then click next. For the membership condition, choose URL and then specify your share like this: File://g:/projects/myteam/*
Click next and then click the "Use Existing Permission Set" radio button and choose FullTrust from the dropdown. Click next and finish and you are all set. You'll still get the warning when you load a project, but everything will work as if you were working off your local drive. Be aware that any code originating from that directory will have full trust on your machine. -----Original Message----- From: David B. Bitton [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 30, 2002 4:20 PM To: [EMAIL PROTECTED] Subject: [DOTNET] Control SOAP Envelope Is there a way to take complete control over a SOAP envelope. I'd like to omit some namespace declaration at the top. Also, I'd like to use .NET projects from a share (mapped drive). I'd get the warning about being an untrusted source. Ok, this makes sense. Now, how do I make it as safe? I tried to poke around in the .NET MMC snap-in, but it was a bit to cryptic. Can someone shed some light on this? TX :) -- David B. Bitton [EMAIL PROTECTED] www.codenoevil.com Code Made Fresh DailyT You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
