Assembly.LoadFr om throws PathTooLongExce ption unexpectedly.

[shrishjain]

Hi All,

I call Assembly.LoadFr om("C:\\MyDir\\ MyAssembly.dll" )- it works fine.

However when I call the following, it fails:

Assembly.LoadFr om("C:\\MyDir\\ ..\\MyDir\\..\\ MyDir\\..\\MyDi r\\..\\MyDir\\. .\\MyDir\\
...\\MyDir\\..\ \MyDir\\..\\MyD ir\\..\\MyDir\\ ..\\MyDir\\..\\ MyDir\\..\\MyDi r\\..\\MyDir\\. .\\MyDir\\..\\
MyDir\\..\\MyDi r\\..\\MyDir\\. .\\MyDir\\..\\M yDir\\..\\MyDir \\..\\MyDir\\.. \\MyDir\\..\\My Dir\\..\\
MyDir\\..\\MyDi r\\..\\MyDir\\. .\\MyDir\\..\\M yDir\\..\\MyDir \\..\\MyDir\\.. \\MyDir\\..\\My Dir\\..\\
MyDir\\..\\MyDi r\\MyAssembly.d ll")

Can someone tell me how can I get rid of it. Is there a way I can
compact the path before I pass it on to LoadFrom(string path).

Thanks,
Shrish

[Stoitcho Goutsev \(100\)]

Wow! Where did you get that string from?

I couldn't find anything in the framework that could help optimize this file
name, so I wrote one by myself

Here it is...

static string OptimizeFilePat h(string filePath)
{
string[] parts =
filePath.Split( System.IO.Path. DirectorySepara torChar,
System.IO.Path. DirectorySepara torChar);
Stack stack = new Stack();
foreach (string folder in parts)
{
if (folder == "" || folder == ".")
continue;
if (folder == "..")
stack.Pop();
else
stack.Push(fold er);
}

StringBuilder optimizedPath = new StringBuilder() ;
foreach (string folder in stack)
{
optimizedPath.I nsert(0, folder);
optimizedPath.I nsert(0,
System.IO.Path. DirectorySepara torChar);
}
optimizedPath.R emove(0, 1);

return optimizedPath.T oString();
}
--
HTH
Stoitcho Goutsev (100)

<sh********@gma il.com> wrote in message
news:11******** **************@ g44g2000cwa.goo glegroups.com.. .

Hi All,

I call Assembly.LoadFr om("C:\\MyDir\\ MyAssembly.dll" )- it works fine.

However when I call the following, it fails:

Assembly.LoadFr om("C:\\MyDir\\ ..\\MyDir\\..\\ MyDir\\..\\MyDi r\\..\\MyDir\\. .\\MyDir\\
..\\MyDir\\..\\ MyDir\\..\\MyDi r\\..\\MyDir\\. .\\MyDir\\..\\M yDir\\..\\MyDir \\..\\MyDir\\.. \\MyDir\\..\\
MyDir\\..\\MyDi r\\..\\MyDir\\. .\\MyDir\\..\\M yDir\\..\\MyDir \\..\\MyDir\\.. \\MyDir\\..\\My Dir\\..\\
MyDir\\..\\MyDi r\\..\\MyDir\\. .\\MyDir\\..\\M yDir\\..\\MyDir \\..\\MyDir\\.. \\MyDir\\..\\My Dir\\..\\
MyDir\\..\\MyDi r\\MyAssembly.d ll")

Can someone tell me how can I get rid of it. Is there a way I can
compact the path before I pass it on to LoadFrom(string path).

Thanks,
Shrish

[shrishjain]

Thank you very much. I am getting such long paths from some
automatically generated configuration, and therefore having the
problem.

Thanks,
Shrish

[David Levine]

Make sure the autogenerated path has a maximum length of 260 characters

<sh********@gma il.com> wrote in message
news:11******** **************@ z14g2000cwz.goo glegroups.com.. .

Thank you very much. I am getting such long paths from some
automatically generated configuration, and therefore having the
problem.

Thanks,
Shrish

[Stoitcho Goutsev \(100\)]

Actually I'm not sure about that. I read somewhere that MAX_PATH counts the
length of the path in C/C++ chars where the char type is 1 byte. For .NET
one char is 2 bytes so it should be devided by 2 - 130 chars.

As I said I read this in some posting in the ng, never tried, never checked
and it could be simply not true.
--

Stoitcho Goutsev (100)
"David Levine" <Sn************ *************@w i.rr.com> wrote in message
news:uI******** ******@TK2MSFTN GP10.phx.gbl...

Make sure the autogenerated path has a maximum length of 260 characters

<sh********@gma il.com> wrote in message
news:11******** **************@ z14g2000cwz.goo glegroups.com.. .

Thank you very much. I am getting such long paths from some
automatically generated configuration, and therefore having the
problem.

Thanks,
Shrish

[Mattias Sjögren]

Actually I'm not sure about that. I read somewhere that MAX_PATH counts the
length of the path in C/C++ chars where the char type is 1 byte. For .NET
one char is 2 bytes so it should be devided by 2 - 130 chars.

No MAX_PATH defines the number of characters, not bytes. So it's 260
in both worlds.
Mattias

--
Mattias Sjögren [C# MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

[Stoitcho Goutsev \(100\)]

Ok. It make sense. As I said I read it and I wanted to throw it here just to
see what the others have to say about it.

It didn't sound right to me in the first place.

However MAX_PATH is a constant in the SDK header files. It has nothing to do
with the reality. In NTFS the names could be big times longer than 260
characters. I don't know why this limit. I mean I know but it doesn't make
sense in .NET except that it uses the uderlying API.
--

Stoitcho Goutsev (100)

"Mattias Sjögren" <ma************ ********@mvps.o rg> wrote in message
news:es******** ******@TK2MSFTN GP10.phx.gbl...

Actually I'm not sure about that. I read somewhere that MAX_PATH counts
the
length of the path in C/C++ chars where the char type is 1 byte. For .NET
one char is 2 bytes so it should be devided by 2 - 130 chars.

No MAX_PATH defines the number of characters, not bytes. So it's 260
in both worlds.
Mattias

--
Mattias Sjögren [C# MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.