Skip to main content

Open workbench an MS Project Open Source Alternative

For a project manager , planning is your bread and butter . A good software tool is a complement ,as long as it doesn't come with a high price . MS Project , a Microsft product , is one of the most commonly used project management tool around . But if your just a low earning firm with little money to invest on project management tool you may not be able to afford this tool.

Open source software , as I always mention it on some of my blogs , free users of high prices from large software companies . It may not be always free , but it is cheaper . Additionally , the source code comes with it , so if you are that technically adventurous , you can always customize it to fit your need. Open Workbench aims to be a direct alternative to Microsoft Project . Open Workbench provides project planning and scheduling together with resource management. Open Workbench even offers import of Microsoft Project files - to make migration easier . So if you dont mind investing a little of your time to learn the software , in the long run , you may appreciate how much is being saved on using this software. Personally , I have tried using the software (my project management task was short lived so i was really able to jump into it deeper) and all I can say is that , the software can be easily learned to achieve the productivity you want.



Visit their website , it has a lot of information regarding the software plus they have a SAVING section on the page that shows how much can you save. Dont forget to download it and give it a test drive.

Comments

Emmy said…
It's a good blog, smile for you 1

Popular posts from this blog

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

renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!



I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Automatic Properties and Object Initializers in .Net 3.5

With the release of .Net 3.5 alongside with Visual Studio 2008 , new enhancements was again introduced . Some maybe well pronounced such as the inclusion of WCF, WPF , LINQ in .Net 3.0 and some just came unnoticed. If you have been accustomed of using a particular method or technique in implementing a certain code in .Net 2.0 , because of backward compatibility , you may not even notice that there are new ways of implementing it in .Net 3.5.

Here are two new concepts in .Net 3.5 that a developer may not notice ( at least in my opinion ) : Automatic Properties and Object Initializers . To illustrate these two , I am going to present the pre-.Net 3.5 way (.Net 2.0) and the .Net 3.5 way in creating a simple class with simple properties.

Automatic Properties

Creating a class can be tedious , especially when working with a list of properties , . One way to get around having to type the code for a private field and its public property getter and setter is to use a refactoring tool. However, …