I have an app running on two environments: my local machine, and a deployment environment. I'm using opensmtp in the app to create emails with attachments. The deployment environment instantiates the attachment objects without any problem. However, whenever I try to instantiate a new attachment object on my local machine, opensmtp throws a "The directory name is invalid." exception.
On my local machine (the instance that's screwing up), if I go into the debugger and change the file name around to something else (for example, a file or path that doesn't exist), the attachment object will instantiate fine. It only throws when I try to instantiate the attachment object using a string parameter of an actual existing file.
The apps are asp.net web apps, installed to the same physical directories and same virtual directories on both machines, and use the exact same code base and dlls. I'm stumpted as to why this is happening on one environment and not the other. I wish I could give more information but unfortunately the exception message isn't any more verbose (nor does there seem to be any help out there regarding this issue).
Any support would be appreciated. Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have an app running on two environments: my local machine, and a deployment environment. I'm using opensmtp in the app to create emails with attachments. The deployment environment instantiates the attachment objects without any problem. However, whenever I try to instantiate a new attachment object on my local machine, opensmtp throws a "The directory name is invalid." exception.
On my local machine (the instance that's screwing up), if I go into the debugger and change the file name around to something else (for example, a file or path that doesn't exist), the attachment object will instantiate fine. It only throws when I try to instantiate the attachment object using a string parameter of an actual existing file.
The apps are asp.net web apps, installed to the same physical directories and same virtual directories on both machines, and use the exact same code base and dlls. I'm stumpted as to why this is happening on one environment and not the other. I wish I could give more information but unfortunately the exception message isn't any more verbose (nor does there seem to be any help out there regarding this issue).
Any support would be appreciated. Thanks!