Skip to main content

An Open Source CMS from Microsoft ?????

Perhaps the open source thing has been running around Microsoft . Microsoft dont like showing their codes, that is why even just a glimpse of MS Windows code can be worth a million. But of course , they support learning , that is why they have codePlex. Now going back to the topic , ZDNet announce today that Microsoft is developing an Open Source CMS !! Yes , an open source Content Management System. For what ? I dont know. as far as I know , they released Blogengine.net on codePlex a few months ago which is mainly an opensource solution for blogging. Now they are going for the CMS. Is it not that Microsft already have the MOSS or the Microsoft Office Sharepoint Server or even the outdated Community Server?

It is a welcome development indeed for Open source fanatics . I just hope that it will receive great appreciation from those who are currently using famous Opensource CMS such as Drupal , Joomla , PHPNuke or even DotNetNuke .

One main concern why I prefer OpenSource CMS which can run on linux is its cheapness to maintain and operate. Most free and cheap web hosting runs linux on their servers. Drupal , which I have already used in Online aparri , for example, uses MySQL and runs on top of apache in a linux box. Will this new OpenSource CMS has the ability to run on top of MySQl and Apache environment? I bet it doesnt unless maybe they have used Mono , then there is a slim chance. Nonetheless , for a budget sensitive guy , I will still prefer CMS that run on top of open source softwares such as Linux, MySql and apache.

By the way, MS is naming it initially as "Oxite".
Labels:

Comments

Post a Comment

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...
Post a Comment
Read more

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true
Post a Comment
Read more

How to Kill a Slow Process using DOS Batch File Script with TaskKill and TaskList

If you are still trapped in the era of batch files and command lines in Windows environment, here is something you can add to your DOS cheat codes.  Lucky for us here, we are still using DOS batch file to implement installation of some updates to our system. Here is a simple batch file script that is designed for slow systems that requires a significant amount of time to kill a particular process. The requirement is simple,  do not start any copying or moving of files until  the process ( i.e. MyProcess.exe) is totally killed by DOS. The simplest solution would be to use TASKKILL to kill the process, wait for a few seconds  then start copying/ moving of files there after. Unfortunately, while we were testing this simple step on a slow machine, DOS would take an awful lot of minutes to kill the process in question. Thus, when our delay is reached, we would encounter error on copying/moving files that is currently used by the unkilled process causing a failure on ...
1 comment
Read more