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.
 
Back
Top