Microsoft .NET Framework 2.0

All replies

• 

  

  0

  Sign in to vote

  I've also faced same problem. No idea!

  Monday, May 5, 2014 1:05 PM
• 

  

  0

  Sign in to vote

  Hello,

  I'd argue that the output is correct, and the assumptions are incorrect.

  Ho do you know that 20-feb-30 does not refer to 20th February, 1930?

  If you insist that it should be 2030, use a four digit year.

  No need to repeat the Y2K programming short sightedness.

  Karl

  ---

  When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
  My Blog: Unlock PowerShell
  My Book: Windows PowerShell 2.0 Bible
  My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

  Monday, May 5, 2014 8:58 PM
• 

  

  1

  Sign in to vote

  Sounds like the 2029 rule got applied.

  http://support.microsoft.com/kb/302768

   Might ask them over here.

  http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=netdevelopment&filter=alltypes&sort=lastpostdesc

   

   

   

   

   

  ---

  Regards, Dave Patrick ....
  Microsoft Certified Professional
  Microsoft MVP [Windows]
  
  Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Proposed as answer by Just Karl Tuesday, May 6, 2014 12:46 AM
  • Marked as answer by Just Karl Wednesday, May 14, 2014 2:06 PM

  Tuesday, May 6, 2014 12:42 AM