So, the blog is up and running!
We have our designers coming up with some ideas and we are looking at developing some widgets also. We did have a bit of a, well, aggravating time today. Mainly this was down to installation and the fact we forgot all about .NET as a whole. I guess this happened because we were installing a pre-built application and didn't think about this stuff. Anyway, to get to the point, here is a few gotchas to keep in mind.
Don't forget who's running your new Blog site!
If your hosting your new blog with a shared hosting provider, you must ensure that your App_Data folder has Read/Write permissions set to it. This will ensure that you can add posts, change settings etc.
If, like us, you are running on dedicated machines, you need to look at your application pool under IIS 6/7 and check the Identity of the process running the website. To do this follow these steps;
- Open the properties of your new blog website by right clicking the website icon and selecting properties;
- Select the Home Directory tab and make a note of the Application Pool at the bottom of this window. Click Cancel to dismiss the website properties;
- Expand the Application Pools folder and right click the pool you previously noted;
- Select the Identity tab. In here it will display the security account which is running your new blog.
Once you have the account which is running the application pool, you need to grant this user Read/Write permissions on the App_Data folder. The BlogEngine.net website discusses adding permissions to the ASPNET user which is correct for your development machine or localhost, however in IIS 6/7 this is unlikely to be the case.
Let me know if you need any further help on this.
Hey, .NET 1.1 don't get so upset!
So we have copied our blog to the server and setup a bog standard website in IIS 6. Then, hold on! everything stopped working! Hey BlogEngine.Net, thats not fair, whats going on?
Then we remembered, we have .NET 1.1 applications running and we setup the new website in the same application pool. The key thing here to remember is to setup your new website along with a dedicated application pool if you have multiple applications running. Then again, it doesn't need to be dedicated, it can be shared across applications as long as they are running the same version of .NET. Make sense?
Here's a few links that may help also on these issues and more.
Have fun, its a great solution, well done chaps!