A
Angry Developer
I am addressing this message to Microsoft directly.
Recently this service pack was released, and it has fixed many issues.
However, one glaring bug fix, for some reason or another, was left
out of this service release. The VersionNotFoundException which will
occassionally rear its ugly head when using expression columns in
datatables. This bug has been known for a while. For some reason,
the release of Framework 1.1 didn't fix it, and yet another
opportunity to fix it has come and passed. What is the deal? Does
Microsoft not know where the cause of this error is? Is it not a
priority? I have a large project which uses expression columns on a
rather large scale. The only workaround I have ever seen documented
is simply "don't use expression columns." For some of us that is just
not an option.
Does anyone have a workaround?
Will someone at Microsoft please look into this and give us developers
some advice as to how to work around this bug? Would that same person
give us some kind of time frame as to when this will be fixed. I
don't care if VS.2005 fixes it. That is years away from being a
development solution for some of us. And would that same person
please express our frustration to somebody there at Microsoft so this
will get fixed ASAP.
Thank you.
Recently this service pack was released, and it has fixed many issues.
However, one glaring bug fix, for some reason or another, was left
out of this service release. The VersionNotFoundException which will
occassionally rear its ugly head when using expression columns in
datatables. This bug has been known for a while. For some reason,
the release of Framework 1.1 didn't fix it, and yet another
opportunity to fix it has come and passed. What is the deal? Does
Microsoft not know where the cause of this error is? Is it not a
priority? I have a large project which uses expression columns on a
rather large scale. The only workaround I have ever seen documented
is simply "don't use expression columns." For some of us that is just
not an option.
Does anyone have a workaround?
Will someone at Microsoft please look into this and give us developers
some advice as to how to work around this bug? Would that same person
give us some kind of time frame as to when this will be fixed. I
don't care if VS.2005 fixes it. That is years away from being a
development solution for some of us. And would that same person
please express our frustration to somebody there at Microsoft so this
will get fixed ASAP.
Thank you.