Right, but you could also put the empty dataset.xml in the App_Data folder as well. Not that you need to, but that is where it would naturally go and since the schema file (xsd) applies to that xml dataset, I would say it logically suggests to put the xsd file in the App_Data folder. Normally the only thing I put into App_Code is BasePage type stuff that all my pages inherit from or some BaseUserControl stuff. I also have some HTTPHandler stuff in that folder. I don't really consider an xsd file code so I would not put it in the App_Code folder. I guess if you had several xsd files perhaps you would want a new folder.
To my knowledge XSD files are not compiled. They are just schema files. They describe the rules for the xml file they are the schema for. In my experience I have not had any issues returning a fully fledged data set through a web service. As far as the web service it is just a dataset. It is your caller and the web service that need to understand what is in the dataset.
Still it sounds like you want to put the xsd in App_Code. In the end it doesn't matter that much. I was just giving you my opinion on where I thought it should go.
How do I add the user "everyone" with full control to the security settings of my web.config file. I need to chane the web.config file via my web service so that I can set my connection string as required per client
This is a fire detection server that will be standing behind a firewall and no-one can have access to it from the outside. No one will consume the web service from the outside. However for my technicians to install the system on the mine they need to change the connection string to connect to the database as the path of the data base can change on a per install base
I think the web.config is readonly in runtime 'cause the web
application is forces a restart the it detects a changed web.config
file. So either if you can change it I don't think its saved until the
webapp restarts or the web.config is readonly in runtime.
I wrote and article which describes how to change the web config file programmatically. I think if you follow my article you can created a domain user that you set up as the identity of your app pool that your web service runs under. Then you could change the web.config. NOTE when the web.config is change the application will restart. If you are talking about the web service changing a different web sites web.config that is pretty dangerious, I would suggest a different solution if at all possible. http://www.codeproject.com/useritems/SingleWebConfigFile.asp[^]
Hi Ihave looked at the article a while ago. Nice one, if I may say so, but it does not quite suite my needs.
I just need to change an element in the connectionstringsettings to the connection string of my database. This connectionstring is unique per installation. If I change the security settings of the web.config file via Explorer then my code works well, and I can change the connection string as I please.
I just need to change the security setting programmaticaly