For the most part, the framework uses Win32. There is code available to add true LFN support to the framework, but as it hasn't been integrated into the main trunk, you can't be certain it's available "everywhere".
Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Friday, May 21, 2010 9:00 AM To: NT System Admin Issues Subject: Re: Idle question? On Thu, May 20, 2010 at 5:34 PM, Michael B. Smith <mich...@smithcons.com> wrote: > The limits that Rod quoted are accurate - for Windows Explorer and > anything that uses the .NET framework. Changing the Win32 API is not > done lightly. If the limitation is Win32 API backwards compatibility, why is this limit still present in the .NET Framework? -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
