Ok, so I should learn not to post things too early, right? The problem
wasn't the new operator on the property, it was because this property was
I'am wondering if I should implement ISerializable in order for me to stick
with read only properties. Any comments?
"Graham Allwood" <NoToSpam-graham.allwoodeborsolutions.com> wrote in
message news:%2311EvpfIEHA.3276TK2MSFTNGP09.phx.gbl...file> Hi,
> I have been reading several posts where people are getting a
> FileNotFoundException when trying to construct a web service proxy. TheWhen> that is reported missing changes everytime.
> There has been several different reasons for this in the past including
> permissions to the c:\winnt\temp folder, missing default constructor and
> duplicate enum definitions in the schema. Well, I have another reason for
> this to happen:
> I have an assembly that contains all the custom types my services use.is> I reference my service in my WinForms app I have to modify the proxy thatfor> generated for me; specifically I have to remove the generated definitionXmlSerializer,> my types and add a USING statement so that it picks up my own type
> definitions. Everything was working fine until I started using a type when
> one of the properties was using the new (C#) operator to hide a property
> definition in a base class. This caused the proxy constructor to fail with
> the about error. Commenting out the property made everything work again.
> Can anyone explain this to me? Is it something to do with the> if so what?
> Thanks for any help
> Graham Allwood