SFTP.NET Help File (General questions)

A question and a comment about the help file included with the SFTP.NET component. First off, I'm not sure whether you know, but the Events section of the SFTP Class is not under the SFTP Class section. It's located incorrectly under SFTP Class -> Methods -> Rename Method -> Events. Just thought you'd like to know. :o)

Also, Is there documentation anywhere that defines what the errors returned by the SFTP.NET Component are, such as authentication errors, timeouts, etc... I'm looking for actual text returned by the component and any error codes that may be associated with them.

Thanks!
-Jason

Jason,

Events section of the SFTP Class is not under the SFTP Class section

Thank you! This is now fixed.

Also, Is there documentation anywhere that defines what the errors returned by the SFTP.NET Component are, such as authentication errors, timeouts, etc... I'm looking for actual text returned by the component and any error codes that may be associated with them.

No, we don't have that in docs. For this purpose we created several specialized Exceptions which can be found in helpfile, but actual text is not available. It's not a secret, we just didn't provide it since exception type seems more important. You disagree?

It's not that I disagree with the new exceptions. Believe me, I think they're great. However, I'm building an automated solution, which will, of course, have log files associated with all of the applications. These logs will be stored in a database, rather than be left as text. In any relational database, numbers referencing errors is always better than writing the actual error over and over again. This is the reason I'm inquiring about the error text itself.

-Jason

Jason,

I see your point.

However.... :)

If we slightly change text in the expection (such as invalid packet xxx arrived) you will end up with unknown number of error representations, so...

Ahh yes. It's easily addable to a database later, though.

On the other hand, I'm sure I could just write up a lookup script to compare the actual text with what I have in the database. If it's not there, or it's different, then just add the text as a new entry. I may just take that route. It was just a thought for the future, though. A list of error codes and text may be useful for someone other than me, also.

-Jason