After much anticipation, I am sure, from my zealous readers, I offer to you Simple CMS. This is a simple content management system, hence the name, which plugs into existing applications. This ASP.NET 2.0 plug-in is not meant to be a full blown application. This is for someone who has a site, and wants to easily add content to the site. With Simple CMS you can through a web interface create content for you pages, and control the addresses of these pages within your site.
Simple CMS is currently in Beta, but support will be offered most prominently through the Simple CMS Forum, which is also where I would like people to let me know of any features they would like to see in later versions. I already know of some large changes I plan to make for future versions of Simple CMS.
I hope you enjoy Simple CMS, and you can expect some articles to be written and posted on ASPAlliance.com about how I made Simple CMS. I will probably write these as separate articles about interesting and useful topics I employed in the creation of my content management system. If you think Simple CMS is cool, you should also check out this Cache Manager on which Simple CMS is loosely based. It is a very useful little tool.
Steve Smith did a nice release post for Simple CMS yesterday, so rather than duplicate the content I will just link to his post.
Thanks for reading my Blog. Keep reading it and maybe you will get a free cookie, but you probably won’t.
Don’t worry. I am still around, and I have just written my review of AppDev’s Professional Training via DVD-ROM course called Microsoft® Visual C#® 2005: Developing Applications. It was a very good course, and I would recommend it to others. My review is called Review: AppDev Visual C# 2005: Developing Applications. To write the article, all I had to do was go to ASP Alliance.com and click on the link entitled Write for Us. From there I was able to submit a request for the article. It was accepted shortly afterwards, and I soon after started writing the article by following their set of article guidelines. For those of you who read my blog, expect to read more of my articles on ASP Alliance.
Well after a frustrating time trying to figure out how to make embedded resources work, I finally understand. This makes everything much easier. As some of you may know I have been working on a content management tool. (This is not a full blown content management system) Since it is designed to be portable to existing ASP.NET web sites, it is just a dll file. Even though it uses a couple of images, I don’t want anyone to have to copy image files just to get the app working correctly.
To accomplish this I decided to use embedded resources, something I had never done before. Starting out I fumbled a lot trying to figure out how to display these, bad idea. Well I started googling for a solution to my problem, and I tried doing what Microsoft said to do. Following what they said to do got me nowhere, and left me a bit more confused. The site makes many assumptions about what I all ready know. Since I did not know these things, I took some guesses. Sadly incorrect ones. I think the authors of those resources need to learn the value of a hyperlink. It would allow them to reference old material so I could learn what they assume I know.
After reading that I had a better reference to start googling. I started looking for the GetWebResourceUrl method, and this led me to other web sites, which had some better explainations. At first I went to an article on codeproject explaining how to access embedded image resources. This was much better than the previous one I read, but I still could not get this one working right. My example didn’t quite fit with what they did, and they didn’t explain each part of the process.The problem is that even if I had incorrect code in my file, GetWebResourceUrl still returned a url that looked like it was supposed to. Again I needed to find something to get this working, or I would have to go back and start writing a lot of code I did not want to write.
So I tried another link I found on google, and this article on Embedding Resources in ASP.NET 2.0 Assemblies explained to me very well how to get my embedded resources working. It explicitly told me where each part of code belonged It mentioned some specifics I might need that were not even part of that example. Not only that but it had more than one type of embedded resource that it accessed. If you are ever trying to use embedded resources I recommend it, but I suggest reading this article first. I may have to start reading more articled written by Mark Hines. If you are interested in this topic, I suggest reading this article as well Embedding Resources in ASP.NET 2.0 Assemblies - Part 2.
I recently added caching to my Content Management System. Since I am no caching expert I wanted to make sure I had created the functionality that I wanted to make. I wanted to ensure durations were as I expected, and wanted to make sure that items were cached when they should be and removed when they shouldn’t be cached anymore. I could have changed the program to debugging mode and debugged the code. I could also have added code to check and see the values of the cache object at certain times, but I found a much easier solution.
I found that by adding this Cache Manager plug-in to my site I was able to quickly and easily check at any moment what was in the cache. All it took to add this to my site was copying this file into my bin folder, and copying a line of code into my web.config file. Since I was just using this while debugging the application there was no need to worry about the optional security on the cache manager. When I was done setting up the caching, I simply removed the dll file and the line of code from my web.config file.
I recommend checking out that cool little plug-in if you are doing any work with caching. I plan to use that tool any time I am working with caching on any ASP.NET web site. I like things that make my job easier.
Lately I have been working on a simple content management system. This CMS will not be like a lot of what is currently available. The software applications that currently exist tend to be applications which are the site. Simple CMS will plug into an existing web page. This is beneficial because it will allow people who have one or more web sites to quickly and easily add content to that site.
So far I have been able to keep the install down to one executed SQL script, a dll file, and some copying and pasting into a web.config. This may be changing a bit as I add more to the functionality of the system.
I have been working with the httphandlerfactory class. I have my SimpleCms handler factory inherit from that class, and I use to handle the content which the system creates. Creating these pages often gets complicated, because I have to find ways to get the controls to render correctly. Sometimes I cannot use the controls I want to use because I cannot get them to render. I am working still to get them working, but for the time being I want to have a working CMS.
Inheriting from System.Web.UI.Page, I create my base pages for the system, and from there I have a couple of custom administrative pages built into the system. This is the interface which users connect to to manage the content. Since these pages are classes the user is able to change the location with which to connect to them.
Soon I will be passing this assembly to Zach Bussinger, who is going to try to implement and use this. I like to think that he is a test subject or guinea pig. If he can't get it working I think I need to go back to the drawing board, but if he can then it should be usable. He will also probably let me know what kinds of problems he finds in the application that I did not notice.
Once I have a version of the application to release I will make sure to blog more about it. I will probably talk more about how to use it and its features when I am farther along with the project.