I have this issue in a VB.NET project using wse1 (ugh)
Have you tried adding a (global) Import (via project properties) that is the
namespace where all your classes that you are using via webservices reside?
I also have a macro for removing the created classes and enums - since I
don't need them again and the Import then allows the compiler to reference
the ones I want as the ones in the local namespace are now deleted.
What I hate most is the use of fields rather than properties and the above
lets me have properties.
> Hi,
>
[quoted text clipped - 14 lines]
>
> thanks
julian - 24 Aug 2005 23:21 GMT
thanks Shaun,
tried and failed, the import just saves me some typing,

Signature
julian
> I have this issue in a VB.NET project using wse1 (ugh)
>
[quoted text clipped - 26 lines]
> >
> > thanks
Shaun Wilde - 25 Aug 2005 14:32 GMT
So all you need to do is delete all the extraneous classes and enums then ?
> thanks Shaun,
>
[quoted text clipped - 30 lines]
> > >
> > > thanks
julian - 25 Aug 2005 22:59 GMT
thanks again,
I thnk I've missed something / feeling a bit slow!.
Add WebReference, change WebReference Folder name from "com.xxxxxx.www" to
"something sensible" and add Global Import works great for classes from
WebService received in the client.
What happens for the same classes returned inside a SoapEnvelope using
SoapClient / SoapService?

Signature
julian
> So all you need to do is delete all the extraneous classes and enums then ?
>
[quoted text clipped - 32 lines]
> > > >
> > > > thanks