Scott Hanselman

VB6->VB.NET->VB.NET/Whidbey Collection Class change

July 1, '04 Comments [0] Posted in Programming
Sponsored By

Remember all the weirdness around Collections and VB6 when VB.NET came out?  I just noticed this breaking change as we move from 1.1 to Whidbey.  Previously added workaround code will have to be removed.

VB collections have weird implementation of IList: 0 based for read and -1 based for insertion
Affected APIs none
: Ilist implementation of VB collection is fixed
Affected Assemblies\Dll(s): Microsoft.VisualBasic.dll
Affected Scenarios: Upgraded apps that use VB Collection through inconsistent implementation of Ilist (very unlikely scenario) may be broken.
Description: An instance of Collection type is casted to Ilist and then used via Ilist interface. To make this work in 7.0, 7.1 you would need to specialcase access to Ilist if it holds Collection
Workaround Code that has special-case warkarounds to use Collections casted to Ilist, will have to remove workarounds.

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Sponsored By
Hosting By
Dedicated Windows Server Hosting by SherWeb
Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.