>> Well I could not find an answer must be a bug.
>>
[quoted text clipped - 19 lines]
>
> Pete
> Pete,
>
> I have spent part of this week on the problem and posted 3 times
> on the problem.
Sorry...first time I saw your post.
> To post the code to reproduce the problem
> would mean posting 5 projects of source code as the
> code abstracts creating a data form from xml etc etc.
Well, to post the code would mean reducing your 5 projects of source code
down to the bare minimum required to reproduce the problem, so that you
don't have to post 5 projects of source code.
Oddly enough, that's the same process you should be using to debug the
problem. If you are unable to reproduce the issue without all that other
stuff, that strongly suggests that something in all that other stuff is
causing the problem, rather than a .NET bug.
> Also posting the SQL DB that the data comes from.
If the SQL database involved is required in order to reproduce the
problem, then you _definitely_ have a bug in your own code.
> And frankly know one on here with asking could be bothered
> going through that code as they have there own issue to deal
> with.
That is clearly false, assuming you do the work to post your problem
correctly. That is, reduce the code posted to the bare minimum required
to reproduce the problem.
> And in my frustration hit out at microsoft.
For no good reason, as I pointed out. The bug is most likely in your own
code.
Pete