How do i...an unhandled exception of type 'system.argumentexception' occurred in mscorlib.dll additional information: empty path name is not legal.

Question

1.00/5 (1 vote)

See more:

  Dim paraghraph As New Paragraph
        Dim pdfFile As New Document(PageSize.A4, 40, 40, 40, 20)
        pdfFile.AddTitle(TextBox1.Text)
        Dim write As PdfWriter = PdfWriter.GetInstance(pdfFile, New FileStream(TextBox2.Text, FileMode.Create))
        pdfFile.Open()

What I have tried:

help me with the one i bold. Thank you

Posted 21-Sep-17 23:24pm

Member 13341316

Updated 21-Sep-17 23:37pm

Add a Solution

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)

OriginalGriff · Answer 1 · 2017-09-21T23:37:00

Look at the error message:

an unhandled exception of type 'system.argumentexception' occurred in mscorlib.dll additional information: empty path name is not legal.

The bit on the end is pretty clear: it needs a valid path to a file and you aren't providing one. But we can't tell what you are trying to pass - we can't run your code under the same conditions you can.

So, its going to be up to you.
Put a breakpoint on the first line in the function, and run your code through the debugger. Then look at your code, and at your data and work out what should happen manually. Then single step each line checking that what you expected to happen is exactly what did. When it isn't, that's when you have a problem, and you can back-track (or run it again and look more closely) to find out why.

Sorry, but we can't do that for you - time for you to learn a new (and very, very useful) skill: debugging!