Welcome to MSDN Blogs Sign in | Join | Help

May 2007 - Posts

Thursday, May 10, 2007 3:36 PM

DateTime.Parse() and DateTime.TryParse() fail in some cases

DateTime.Parse and DateTime.TryParse fail in .Net 2.0 if the user locale date override has a space in it. Ie: if its something like "M d yyyy". .Net is getting tripped up over the space (we're working on a fix for SP1/Orcas). A workaround is to pass the
Posted by shawnste | 0 Comments
Friday, May 04, 2007 9:10 AM

MLang & MSXML6 doesn't like UTF-7

In some cases MLang (on which MSXML6 depends) can added extra ? to decoded UTF-7 data, which can cause UTF-7 encoded XML to fail to parse. UTF-7 isn't a great encoding anyway, so this is just another reason to Please Avoid UTF-7 . In particular there
Posted by shawnste | 2 Comments
Thursday, May 03, 2007 1:29 PM

How do I get HKSCS 2004 characters from Big-5 in .Net?

Well, that's pretty tricky. We provide the Microsoft Character Code Conversion Routines For HKSCS-2004 functions, but those are intended for use with unmanaged code. The fundemental problem is that these "HKSCS" characters were in use prior to the assigment
Posted by shawnste | 3 Comments
Wednesday, May 02, 2007 12:50 PM

How do I get my ANSI based application to run correctly?

A common question is "how do I get my ANSI based code page application to run on a system that has a different code page?" The most obvious solution is to use Unicode :) Then you won't have the code page messiness that leads to this kind of problem. For
Posted by shawnste | 4 Comments
Tuesday, May 01, 2007 11:13 AM

Please avoid UTF-7

UTF-7 inherently some of the security issues that concern people about encodings. For example, by shifting in & out of the base64 mode one can create multiple representations of the same string, enabling spoofing and other problems. UTF-7 is primarily
Posted by shawnste | 1 Comments
 
Page view tracker