Most tutorials show how to either load the mail-properties from a file or setting them programmatically. These properties include an user name and a password to an SMTP-Server but connecting to said server fails if the server requests an user name and a password to connect. So setting these properties isn’t sufficient. Digging deeper reveals a solution that isn’t part of the most tutorials or even mentioned in most of the books like this one (German), albeit it’s not the current edition but the one with the highest Page-rank in Google and the description was fixed in a later edition and for some reason removed in the current.
Setting up a unit test for a form containing an AjaxCheckBox seems pretty straightforward and simple. So simple that it’s easy to forget two essential steps…
I’m stuck with an ancient version of DevPartner at work. For those of you luckily not knowing, what DevPartner is - It’s a Profiler and it’s the single worst documented software I was ever forced to use.
When trying to build stateless pages without the user noticing, like building an application using AjaxFallBackLinks and reusing the fall-back to provide a search-engine-friendly version of your application, you’ve got to put the state into PageParameters, which can be transported via bookmarkable links.
For my current project which is in alpha-test right now, I wanted to verify a user’s mail address on sign up, using the usual approach of sending him an email containing a link to a landing page, he has to visit to activate his account. To my surprise I couldn’t find an existing implementation of this.