There is an interesting article over at the blogs on ZDNET where Paul Murphy is discussing the on going debate between which is better Open Office or Microsoft Office. Personally we can see where both applications have merits, but Open Office will never rise to the level of collaboration that MS Office currently contains as well as the features future versions will have. There is a video that was done a while back on MSDN's channel 9 where the project managers on the office team where discussing the advantages of the new version of Office and how the collaboration the application will be able to offer the information worker is impressive. In a active directory network where other Microsoft Technologies like SharePoint are also deployed, the ability of information workers to more effectively collaborate on projects will greatly increase as Office 2007 hits the selves. Now the cool part about the next version of Office with the ability of Vista to share applications these users will be able to work on copies of the same document at the same time. Open Office

We recently received the latest version of Red Gate Software’s Ants Profiler along with the rest of their suite. Red Gate offers versions of their software to influential members of the community and uses the feedback received form those avenues to improve the product. Red Gate produces some of the finest software available for identifying potential bugs and performance bottlenecks in your code. We have used several versions of these products over the years and have always found them very easy to use and they are very effective. We requested copies of the latest versions one because we wanted to see what was new as well as we have realized we need to identify some bottlenecks in DotNetNuke. This latest version

There are many varying opinions on whether DotNetNuke can be an effective content management system. Overall DotNetNuke is a very robust Web Application framework, but I would not refer to it as a Content Management solution. The main reason DotNetNuke is not really a Content Management System is because it does not have a mechanism for controlling the approval of content. DotNetNuke does have some simple ability to control the start date and end dates of content, but this is very elementary and is not very robust. There are some DotNetNuke modules available on sites like Snowcovered that enable you to utilize more content management functions, but the ones of those I’ve seen are not totally effective and still leave  a lot to be desired, since for a web application to be a true content management system, then it should possess some workflow logic built into the base logic of the application. For a system to be truly classified as a content management system then it needs to allow a company to create a web prescience that will allow them ...