Hi David,
Yep, this indeed appears to be a flaw in the manner in which the VB.NET
implements the for...each statement. You should find that it exhibits
this behavior for a significant number of collection classes, not just
those of the XML library.
At the root of the problem is the fact that the
Hey... Found another instance of the same problem, this time with the
SyncLock statement.
The code below produces the following output:
Before lock
in lock before exit
after lock
in finally
after finally
Whereas you would expect:
Before lock
in lock before exit
in finally
after finally
Impor
I want to localise the text in the category and description attributes
that adorn a control's properties.
I've noticed that CategoryAttribute has a GetLocalizedString method but
I'm not sure how to apply it. And there doesn't seem to be an
equivalent for the DescriptionAttribute.
I'm guessing i
This is clearly a bug in the VB compiler. Best to avoid End Try in all
situations.
Here is a simplified version of the bug. Uncomment the Exit Try statement to
see it occuring. Both the Exit Try and Goto statements actually generate a
leave MSIL instruction. However, the offset specified for the
Hi
We have a 3-tier application with SAO and CAO. The server is hosted in an
NT service or within IIS. The server is deployed on multiple machines in
order to get better performance and availability.
Currently when our WinForms based client starts up it picks a random
servermachine and keeps usi
