Path too long exception

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Peter

    Path too long exception

    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
  • John Saunders [MVP]

    #2
    Re: Path too long exception

    "Peter" <worhol.peter@g mail.comwrote 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


    Comment

    • Fred

      #3
      Re: Path too long exception

      Dans : news:uQ$m6NfhIH A.4196@TK2MSFTN GP04.phx.gbl,
      John Saunders [MVP] disait :
      "Peter" <worhol.peter@g mail.comwrote 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

      Comment

      • Peter

        #4
        Re: Path too long exception

        Thanks

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



        there are c++ and .NET wrapper.

        Thanks



        Fred wrote:
        Dans : news:uQ$m6NfhIH A.4196@TK2MSFTN GP04.phx.gbl,
        John Saunders [MVP] disait :
        >"Peter" <worhol.peter@g mail.comwrote in message
        >news:frebbc$c3 c$1@news.uar.ne t...
        >>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.
        >

        Comment

        • Michael Nemtsev [MVP]

          #5
          Re: Path too long exception

          Hello Peter,

          use unicode version if winapi.
          Just user the "\\?\" prefix for this http://msdn2.microsoft.com/en-us/library/aa365247.aspx

          ---
          WBR,
          Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

          "The greatest danger for most of us is not that our aim is too high and we
          miss it, but that it is too low and we reach it" (c) Michelangelo


          PThanks
          P>
          PI already found out myself.
          PIt is limitation of ansi WinAPI.
          PFound quick solution here:
          Phttp://www.abtollc.com/products.aspx
          P>
          Pthere are c++ and .NET wrapper.
          P>
          PThanks
          P>
          PFred wrote:
          P>
          >Dans : news:uQ$m6NfhIH A.4196@TK2MSFTN GP04.phx.gbl, John Saunders
          >[MVP] disait :
          >>
          >>"Peter" <worhol.peter@g mail.comwrote in message
          >>news:frebbc$c 3c$1@news.uar.n et...
          >>>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.

          Comment

          Working...