Done!
Just a side note and slightly off topic and I hope you forgive me but every
time I have to do one of these large, multi file code changes in a Web
application I break into a sweat. I can't even begin to count the number of
times I thought I had captured all the places in my html, javascript
Hi Jeff,
You must have a LOT of AsyncCallbacks in order to make it worth the pain of
modifying generator code :-) Extending AsyncCallback is the technique most
people use and makes sense as it's clearly application code.
Perhaps one of the Eclipse refactoring tools can ease the pain?
/dmc
On
Hi David,
So far I have 146 and I am no where even nearly having a fully implemented
application.
Eclipse's refactoring definitely would ease the pain if I go with extending
AsyncCallback :)
Regarding extending ServiceInterfaceProxyGenerator, I've looked at the code
and it doesn't appear to be
I'd recommend simply extending the AsyncCallback. Its undoubtedly
more work up front, but its also not a hack, which is a Good Thing.
Its easy to understand, and future maintainers of the program will
thank you for that. Also, karma will likely stab you in the eye if
you don't.
-Ben
On Jan 14,
I made up my mind and did that hurt lol :).
Even though extending ServiceInterfaceProxyGenerator is rather trivial it
might be overkill for my initial needs which extending AsyncCallback can
easily provide and I can alway extend ServiceInterfaceProxyGenerator at some
later point anyway.
So my
You must have been reading my mind because your reply arrived as soon as I
posted my decision. I am a devout believer in Karma and as we know it is
nothing to sneeze at; my luck, I'd get hit in the head by a 600 page hard
covered book dedicated to DotNot web development falling from an elevated
