|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: XmlSerializer Namespace problemHello Christoph Schittko,
You did not answered my question. I guess you are too busy or you just don't know the answer. Thanks anyway for trying. Yes, I do have a paying day job that I have to tend to ... answering
questions in newsgroups is something I do on my personal time. I try my best to answer timely and follow up, but sometimes other issues (the ones that help me pay my bills take precedence). Now with all that ... would you still like me to help or have you figured it out on your own? Christoph Show quote > -----Original Message----- > From: Alexis [mailto:is4fu***@yahoo.com] > Posted At: Monday, November 15, 2004 10:35 AM > Posted To: microsoft.public.dotnet.xml > Conversation: XmlSerializer Namespace problem > Subject: Re: XmlSerializer Namespace problem > > Hello Christoph Schittko, > You did not answered my question. I guess you are too busy or you just > don't know the answer. > Thanks anyway for trying. No, I have not found a way to resolve it.
I'm sorry for the way I wrote my previous posting. This issue has frustrated me so much. I'm thinking there may be no way of fixing it. This XmlSerialization is not completed yet (I beleive). It will not be the first time microsoft releases something not fully worked out. Any way I still need to find some work around for it. Well as I said I already have one but I'm not happy about it. Has that happended to you? You have finished coding but still beleive there got to be a better way. Any way, yes if you still want to take another look to this issue you are more than welcome. I'll really appreciate it. Thanks in advance. /Alexis |
|||||||||||||||||||||||