The framework is logically sliced up into a number of DLL files.
The framework core implementation is defined in mscorlib.dll.
I guess you can think of the other parts as extensions which you need to
plug in
only if you need those specific features that it provides.
--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"John Spiegel" <js******@YETANOTHERSPAMHATERc-comld.com> wrote in message
news:uU*************@TK2MSFTNGP12.phx.gbl...
Thanks, Dennis.
I'm still a bit confused as to why there are chunks of the framework that
they chose to not let the framework know about, but there was probably
some
resource v. usage issue. Isn't there always?
Thanks again,
John
"Dennis Myrén" <de****@oslokb.no> wrote in message
news:%H*******************@news4.e.nsc.no... Add a reference to system.web.services.dll .
--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"John Spiegel" <js******@YETANOTHERSPAMHATERc-comld.com> wrote in message
news:us**************@TK2MSFTNGP15.phx.gbl... > Hi all,
>
> I'm working through some examples using VS2003 and the classic airport
> weather web service. Current topic is creating a proxy class for a web
> service but the wsdl.exe tool is including namespace references that
> aren't
> recognized by .net, namely "System.Web.Services" and
> "System.Web.Services.Protocols". I'm getting errors indicating:
>
> The type or namespace name 'Services' does not exist in the class or
> namespace 'System.Web' (are you missing an assembly reference?)
>
> Two areas of question:
> - Are these 1.0 framework namespaces that have gone away? What should
> these
> be referencing instead?
>
> - Is there a later version of wsdl.exe I should be using? I'm
> currently
> using 1.1.4322, which matches my framework version.
>
> TIA,
>
> John
>
>
