That sounded like it, but I am getting the same error. I used the wizard to
fully trust C:\Inetpub\wwwr oot\VBNET\Manag ingData\bin\Man agingData.dll
but got the error "System.Unautho rizedAccessExce ption: Access to the path
"c:\inetpub\www root\VBNET\Mana gingData\Catego riesProductsSch ema.xsd" is
denied. at System.IO.__Err or.WinIOError(I nt32 errorCode, String str) at
System.IO.FileS tream..ctor(Str ing path, FileMode mode, FileAccess access,
FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean
bFromProxy) at System.IO.FileS tream..ctor(Str ing path, FileMode mode,
FileAccess access, FileShare share) at System.Xml.XmlT extWriter..ctor (String
filename, Encoding encoding) at System.Data.Dat aSet.WriteXmlSc hema(String
fileName) at ManagingData.Ed itProducts.btnS ave_Click(Objec t sender,
EventArgs e) in
c:\inetpub\wwwr oot\VBNET\Manag ingData\EditPro ducts.aspx.vb:l ine 574"
Like I said, when ASPNET is a member of Admin it works, is there something
else I need to Fully Trust?
"Chris" <no@spam.com> wrote in message
news:uI******** ******@tk2msftn gp13.phx.gbl...
101 wrote: I get a security error when trying to write out to an XMLSchema file
"myDs.WriteXmlS chema(strXMLSch emaFile)". I am running XP SP2, No Domain,
MS file and print sharing uninstalled. I was able to get past this by
making ASPNET part of the Administrators group. I tried the Power User
group (as well as others) to no avail. I also had to install MS file and
print sharing in order to even add ASPNET
as a member of the Administrator group (or any other group). After adding
it to the group I can uninstall file and print sharing and everything
works fine.
Is making ASPNET a member of the Admin group the correct way of doing
this, or should I make a new group with some specific permissions?
I am trying to learn .NET programming and trying to avoid going on
security tangents. Is this news group the right place or is there a more
suitable place for Newbie's.
I think the easiest way to solve this is to just fully trust your assembly
in the .Net Config Wizard (in your administrative tools).
Chris