shellexecute not working if path is large (buffer too small assertion)

Question

0.00/5 (No votes)

See more:

Hi,

IS shellexecute LPCTSTR lpParameters has any character limit ?

In my program if "lpparameter" is large it is not calling .exe file

ShellExecute(NULL, ("open"), ("XYZ.exe"),(strtext1 ) ,NULL,SW_SHOWNORMAL);

strtext1 is a path to input file

strtext1 = C:\TestProjectExample\project12345\test12\s1rn1.sie (not working)
strtext1=C:\TestProjectExample\project1\s1rn1.sie(working)

If path is shorter then it will work. If path is lager it won't work.

It is giving Buffer too small assertion.

Please help me to solve this issue.

Thank you,

Posted 18-Sep-14 8:46am

peoria123

Add a Solution

Comments

[no name] 18-Sep-14 14:49pm

Obvious thing to do would be to check and see what strtext1 is.

Sergey Alexandrovich Kryukov 18-Sep-14 15:03pm

Right, but the problems are: 1) MAX_PATH is defined as 260 characters, and OP's examples are all shorter, 2) according to documentation, UNC path should work, but I never managed to put it to work... (so far, I tried .NET only though.)
I put some answer, but this does not present an ultimate solution, just gives some ideas.
—SA

Sergey Alexandrovich Kryukov 18-Sep-14 14:59pm

Sigh... Well, this "path is too long" issue is one of those extremely idiotic Microsoft problems, known for many years, already totally archaic in nature but never properly fixed...
However... This is what makes me doubtful: both your path name examples are really short. Probably, there is something wrong in your observations.
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2014-09-18T09:02:00

Please see my comment to the question.

For some background: http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/48ea2ff7-fab6-4484-ab12-9307399cf47e/shellexecute-with-long-32k-unc-path-how-do-that-on-windows-7?forum=windowsgeneraldevelopmentissues[^],
http://blogs.msdn.com/b/bclteam/archive/2007/02/13/long-paths-in-net-part-1-of-3-kim-hamilton.aspx[^] (even though it is for .NET only, it gives some ideas).

Here is what seems to be a problem: in all your examples, file path is too short to cause a problem (MAX_PATH is defined as 260). Perhaps your observations were incorrect, by one or another weird reason.

<—SA