posted 22 Aug 2011 22:40 by Robert Wood
I'm beginning to start the work required to make smtp4dev run as a service. Quite a few people have asked for this feature and I think it would be very useful.
I'm planning to do this by dividing the core part of the application into a Windows service, and then having the front end communicate with it using .NET Remoting over named pipes. This means it will be possible for the front end to connect to to the service from any session on the same machine, and at this stage I'm not planning to add any authorisation controls because I think that's good enough.
Not everybody wants to run as a service, so I'll also need to make sure the core part can run in the front end process as it does now. |
posted 20 Aug 2011 23:55 by Robert Wood
[
updated 21 Aug 2011 22:39
]
http://visualstudiomagazine.com/articles/2011/06/01/pfint_free-tools.aspx
I just found out that Peter Vogel included smtp4dev in the above article in Visual Studio Magazine "17 Free Tools for Visual Studio". Unfortunately his feedback isn't totally positive because he had some problems with the message inspector window crashing (thought that was fixed in an early 2.0 version?). A subsequent letter from a reader recommended PaperCut...
I'm sorry that Peter had problems. Unfortunately he didn't provide any detail about the problems he had, so I'm still none the wiser. Nobody has logged this problem on the issue tracker either. Anyway, I'll get to the point... If you are having problems with smtp4dev, please please please tell me about them and if possible provide details on the issue tracker. That way I can actually resolve them rather than just speculate what's going on. For most bugs people have emailed me about or put into the issue tracker, where I could reproduce them, I've been able to provide a release containing the fix within a few days. |
posted 20 Aug 2011 23:34 by Robert Wood
[
updated 20 Aug 2011 23:51
]
I've just uploaded an alpha release of smtpdev 2.1 to the CodePlex releases page:
Changes since 2.0: - Message searching:
You can now filter the message list to search for message where their "to", "from", or "subject" contains a particular string. - Message saved to a folder:
You can now configure the folder to which message/sessions are saved to. Previously messages and session contents were kept in memory only, and this was the reason for the conservative default for the max messages limit of 10. Currently the saved files are deleted when the corresponding message/session is deleted, but it's my intention to provide an option to disable this if you prefer. - Error simulation:
You can now enable one of several error simulation options which allow the application to simulate various common SMTP server errors. This is useful so that you can see how your client code will react, and ensure that your program will gracefully survive these various common errors. - Unit testing - Quality improvements:
In an effort to improve the quality of the code base I have spent a lot of time writing unit tests for each component of the server used by smtp4dev. In order to achieve this I have had to do a lot of re-factoring to allow everything to be testing in isolation. Writing the tests highlighted a number of previously unknown bugs which have now been fixed. Whilst the tests are by no means comprehensive yet, it's my intention to ensure as much of the application is covered by them in future.
|
|
