Browse by Tags
All Tags »
Bug (
RSS)
Back in April 2006, I blogged about a nasty JIT compiler optimisation that would cause String.IsNullOrEmpty to throw a null reference exception; ironic really given that is the very thing you’d use the IsNullOrEmpty method to check against. ...
Last month (December 2008), Microsoft released some security updates for VB6 components such as the MS Chart control The first update http://support.microsoft.com/kb/932349 updates MS Chart to 6.1.98.12. The second update http://support.microsoft...
One of the nice things about the My application framework in VB.NET is the ability to easily show splash screens. The splash screen is displayed using a separate thread and by default will close when your main form’s Load event is called. There...
One of the most annoying things I have found about Vista is the file explorer. It constantly changes the views of folders and way too often sets the columns in a folder as if the folder contains photos when it doesn't. To me that is really disappointing...
A couple of weeks ago I wrote about XML Namespace issues in VB: one in particular was to do with namespace declarations being repeated in the output X ML. In those cases we only looked at common namespaces for the entire document. However the example...
If you programmatically add attributes with namespaces to an XElement, when the XElement is written out it will give each attribute a namespace prefix and then define a xmlns for that prefix. The way XElement does this is first it examines the namespaces...
When working with VB9 you may get this cryptic error : XML namespace prefix 'xmlns' is not defined If you are using only default namespaces you can fix this by including a definition for the xmlns as an Import statement or as an xmlns attribute...
If you use XML literals in your code, adding one to another: Dim e1 = <a:books></a:books> dim e2 = <a:book></a:book> e1.Add(e2) You will have the xmlns declaration repeated in each of the elements, when really it is only needed...
Kathleen has posted about a real nasty bug in the VB 9 (VB 2008) compiler. And I mean nasty !! The compiler won't warn you, won't give an error of any sort.. it will just omit lines of code from your application ! Yep, it will compile as if nothing...
In VB9, there's a bug when using XML literals with any type member that is a protected keyword. For example, given the following psuedo types, Class Doc Public Property [Imports]() As List( Of DocImports) End Class Class DocImports Public Property...