G
Guest
Hello, I have just had a bad experience upgrading a Windows Forms app from
vb.net 2002 -> vb.net 2003.
I experienced the problem as detailed in KB article 830118.
According to the article, this behaviour is by design. Can someone please
explain to me what the design goal was, and what is going on "under the hood"
to cause this?
Will it be resolved in future service packs and/or .net versions?
Thanks.
vb.net 2002 -> vb.net 2003.
I experienced the problem as detailed in KB article 830118.
According to the article, this behaviour is by design. Can someone please
explain to me what the design goal was, and what is going on "under the hood"
to cause this?
Will it be resolved in future service packs and/or .net versions?
Thanks.