Hi Steve,

On the server, you can look to see if ASP.net is installed, yes.  This can
be done by looking for the correct registry keys are set up.  This is how
the IIS installer determines whether ASP.net is present.  Offhand, I don't
have the details for this.  You can also think about methods involving
looking to see if a .NET CLR runtime is installed (if not, then you know
ASP.net is not going to work).

As for detecting the configuration settings for web service extensions, you
should look into the structure of the machine.config file - this is
documented on MSDN.  This holds the policy statements governing web service
extensions.  For the most part, the default is that they are enabled, but
require attribution in the code or entries in the config file(s) to make
specific web service extensions active.  Writing a program that finds out
if any WSE are present anywhere would take knowlege of all of the
applications on the machine, and a scan of the config files that are nested
from each application on into the machine config file.  I know of no
implementation of such a tool.

I hope this helps

Dan Rogers
Microsoft Corporation
--------------------

microsoft.public.dotnet.framework.aspnet.webservices:26345