Don't let your constructor create the world around it
I recently listened to a developer podcast about the async/await feature in .Net. And I was terrified when the host asked about using those key words in the constructor.
Naturally you can't create an asynchronous constructor because the constructor should not do a lot of things. That reminded me of this other article I read that pretty well explains what to do and why. Read it!