PDFsharp & MigraDoc Foundation

Hello

Thanks a lot for this great library!, I downloaded it some minutes ago - and already have a working tool...

I noticed, that we can define a Filename in PdfDocument's constructor -
and then it's needless to be forced to define a filename again in the Save() function.

Maybe it would be useful if null or string.empty is passed and PdfDocument
already has a filename, then this filename is ised.

Kind regards,
Thomas

Hello

I have noticed, that PdfDocument's constructor with a file argument and
PdfDocument.Save() with the same filename behaves strange: the exception
'the file is used by another process' is thrown.

I think this is one more reason for supporting PdfDocument.Save() command
without an argument, which just saves the file passed in the constructor.

Kind regards,
Thomas

Hi, Thomas,

I put this issue onto our bug list, should be fixed with the next release.

_________________
Regards
Thomas Hoevel
PDFsharp Team

Hi, Thomas, all!
Late reply: it's not a bug, it's a feature.

When you pass a filename or a stream to the constructor, just call Close() when you are done and the document will be saved - to the file or the stream.
I think there won't be a "Save()" without parameters.

_________________
Regards
Thomas Hoevel
PDFsharp Team