How to deal with this exception?
I need to quickly make my appl to be able to open files beyong this limit
Any help appreciated.

Peter

Re: Path too long exception by John

John
Fri Mar 14 11:51:19 CDT 2008

"Peter" <worhol.peter@gmail.com> wrote in message
news:frebbc$c3c$1@news.uar.net...
> How to deal with this exception?
> I need to quickly make my appl to be able to open files beyong this limit
> Any help appreciated.

I believe this is a limitation of Windows, not of .NET.
--
--------------------------------------------------------------------------------
John Saunders | MVP ? Windows Server System ? Connected System Developer



Re: Path too long exception by Fred

Fred
Fri Mar 14 12:32:22 CDT 2008

Dans : news:uQ$m6NfhIHA.4196@TK2MSFTNGP04.phx.gbl,
John Saunders [MVP] disait :
> "Peter" <worhol.peter@gmail.com> wrote in message
> news:frebbc$c3c$1@news.uar.net...
>> How to deal with this exception?
>> I need to quickly make my appl to be able to open files beyong this
>> limit Any help appreciated.
>
> I believe this is a limitation of Windows, not of .NET.

I think some Windows API can handle path longer than 260 chars in their
Unicode version.
But the framework defines the max to 260.
So, the solution could be to use API perhaps.

--
Fred
foleide@free.fr


Re: Path too long exception by Peter

Peter
Fri Mar 14 13:26:58 CDT 2008

Thanks

I already found out myself.
It is limitation of ansi WinAPI.
Found quick solution here:

http://www.abtollc.com/products.aspx

there are c++ and .NET wrapper.

Thanks



Fred wrote:
> Dans : news:uQ$m6NfhIHA.4196@TK2MSFTNGP04.phx.gbl,
> John Saunders [MVP] disait :
>> "Peter" <worhol.peter@gmail.com> wrote in message
>> news:frebbc$c3c$1@news.uar.net...
>>> How to deal with this exception?
>>> I need to quickly make my appl to be able to open files beyong this
>>> limit Any help appreciated.
>>
>> I believe this is a limitation of Windows, not of .NET.
>
> I think some Windows API can handle path longer than 260 chars in their
> Unicode version.
> But the framework defines the max to 260.
> So, the solution could be to use API perhaps.
>