Bad web reference proxy code

  • Thread starter Thread starter jjoy
  • Start date Start date
J

jjoy

After moving to 2.0, one of our web references stopped working.
The issue is an enumerated type is defined and then used in several
classes within the proxy code (Reference.cs). This type's values are
now no longer getting set, they're always null.
The classes that use this type define it as nullable. If I remove the
nullable declaration, it works fine.
Is there a better workaround or approach?
I'd rather not have to update the proxy code each time I update the web
reference.
 
Is anyone out there?
With so many talented people out there, I can't believe not one has a
suggestion.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Nullable object must have a value 5
"using" declaration and template (generic) classes 2
WSDL Generated Proxy Classes? 3
HTTPWebRequest, Proxy, Credentials? 1
Question about .NET 2.0 web service proxy generation 2
.Net 2.0 issue with HttpWebRequest/Proxy breaking WebService 2
Cannot Add Web Reference in VS2005 (but everything works in VS2003) 1
System.Net defaultProxy section in web.config 1

Back
Top