If you have tried in the past to use Windows Live Writer with Community Server on DotNetSlackers you might have realized that it doesn't actually work. The reason behind this is that we are using the custom cookie authentication module (SSO - Single Sign On), which basically creates the user in CS automatically with a random password. Therefore the password that you are using in your main application won't properly match with the password in CS. There are three workarounds for this:
- Create a new user from within CS using the control panel
- Assign the user as an owner to the blog.
- Send the username and password info to the blog owner and let him use Windows Live Writer to create some test posts.
- Since the password created automatically is random, there is no way that you could change it via the control panel. Therefore you will need to access to the database.
- Login to sql server
- Find out the users email and run the following sql statement for that user:
- update
aspnet_membership
set password = 'pa$$w0rd',
passwordformat = 0
from
aspnet_membership
where
email='username@example.com' - Send the username and password info to the blog owner and let him use Windows Live Writer to create some test posts.
- Integrate the new feature from Community Server called Morpheus, which allows you to use your own membership provider.
If you would like to use windows live writer with your blog on DotNetSlackers, please contact me and will set you up asap. I plan to integrate Morpheus soon as well, so that this step can be avoided.