> I've found this article on how to get ASP.Net to read/write from the
> server's registry, but it got heavily critted as being something that you
> should not do...
By whom? The article certainly doesn't say that wiritng to the Registry is
not something you should do. It merely warns you about the possible issues
that you may encounter.
> [ why is that? ]
Again, who said that?
> what's the problem with a server side application reading data from a server
> box, and using that in it's functions?
The article does a good job of explaining what issues you will have to deal
with.
> the second major question then is, what are the alternatives?
> I've got a messaging framework, and have exposed an incoming interface into
[quoted text clipped - 5 lines]
> server registry so that when the web service is sent data, it sticks the
> relevant files into the folder, who's location it finds in the registry.
Putting data into the System Registry is hardly "the obvious thing to so" -
actually, a database is the usual place to store data persistently. You can
also write the information to a file. While using the registry for such a
purpose isn't going to harm anything necessarily, it will add to the size of
the registry, which is not necessarily a good thing.

Signature
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
> [ the article ]
>
[quoted text clipped - 23 lines]
> Thanks for your time.
> Daniel Bass.
Well, for me if I need a simple configuration value that my webservice needs
to read, I put it in the web.config file. I like to keep out of the
registry as much as possible.
If you need more details about how to work with the web.config, let me know.
Michael
> [ the article ]
>
[quoted text clipped - 23 lines]
> Thanks for your time.
> Daniel Bass.