Saturday, April 28, 2007
In my left hand there is the blue pill...
It turns out he sent me the link for a movie, or a look into the future (by a Google fanatic). It really does feel like I'm in the Matrix! Or the first 10 minutes of the 'Terminator' movie. Anyway, I'll leave you to see for yourself: http://www.albinoblacksheep.com/flash/epic.
You think this is air you're breathing...
Enjoy the movie!
Monday, April 16, 2007
Now for the real stuff; the other day I was trying to uninstall WDS (Windows Desktop Search) and since I did not find the uninstaller in 'Add or Remove Programs' I had to do it manually. I found an entry on the net that explains in detail how to remove WDS and it involved removing the installation folder in the 'Program Files' directory.
When I tried to delete the folder, I could not because it was 'locked'. A quick search online turned up this utility that enables you to unlock ANY folder and subsequently delete it. Lovely tool indeed. It will also give you a list of all locking threads and you can decide which to kill / remove.
On other news, remember a company called Sysinternals? Well, Microsoft acquired the company back in 2006. (You will be redirected to a Microsoft Technet site.) Sysinternals had some extremely wonderful tools that enabled you to monitor literally everything on your computer. You can monitor the entries to your registry (RegMon) in real time! You can monitor your hard disk activity (FileMon). You can monitor the processes running on you computer (Process Explorer); it even shows .Net assemblies and other JIT (just in time) information.
The one I liked most, was Autoruns which allows you to view and switch on or off all the applications that start with Windows. Please note that RegMon and FileMon have been replaced by Process Explorer which, apparently, will do the same job.
Check it out!!
Wednesday, April 11, 2007
My main area of trouble was properly estimating the timeframe for a project, and then sticking to that timeframe. Seems easy enough, only it ain't. You see, there is a very large number of unforeseen variables, that kinda pop up on you.
First of all, allow me to introduce 2 facts. One: a project is a set of tasks. Two: a successful project is one that is completed on time, within budget and meets the defined specifications / features it was set out to complete. Anything other than that is deemed a failed project.
According to that latter piece of information, almost 75% of all software projects are failures. In fact, according to that fact, all my projects are failures.
Now, when planning for a project, the simplest and perhaps the most important piece of information you should know is that there are 3 pivots to every project; features, timeframe and resources.
- Features: what is the project set out to complete. In other words 'the scope of the project.'
- Timeframe: the period of time within which the project should be completed.
- Resources: the budget within which the project is to be completed and / or the number of people involved.
When communicating with project sponsor (the owner of the project and most importantly who will pay for it) you should say "You have 3 important factors; features, timeframe and resources; pick any two?" What this means, is that if 2 factors are set, the third factor is affected either upwards or downwards.
To explain this better, here's an example. A project has 20 tasks, and must be completed within 3 days. This means that the number of people to work on this project should be increased to 5. The same project, but to be completed in 10 days would require only 2 people.
Another project with 50 tasks, where ONLY 4 people (maybe because of money shortage) can work on, would require 30 days to be completed. Get the drift?
Another issue to take care of is: scope creep. Scope creep is when the number of features / tasks in the project seems to increase as time goes by. This would result in a never ending project, and a sure failure.
One parting piece of information: if you fail to plan, you plan to fail.
Monday, April 2, 2007
Well, some cool dude has created one for SQL Server 2005. I have to say, WOW! It looks absolutely astounding and supports versions 2000 and 2005 of SQL.
Now, this guy is an SQL expert and he's even posted a few articles such as 'SM0 2005 - Populating a list of SQL Servers' which I've always wanted. How cool would it be to add it to your application?!
Download it from www.getpaint.net.
Sunday, April 1, 2007
I'll cut to the chase. I strongly disagree. I have nothing against C# but VB is still the language of choice.
Here is what I think;
- If you are migrating from VB, then migrate to VB.Net. You're still gonna have to learn a lot, but the syntax is still 70% the same. Unlike C# where the syntax is 90% different.
- The VB developer environment is at least twice as productive as that of C#. A bit more verbose, but still more productive.
- Compiled VB code is smaller than that of C# (even though by a very small margin).
- Where I live, VB developers average salary is MUCH higher than that of the C# counterpart.
- Both VB and C# can do 99% of what the other can do.
- In Orcas (the new Visual Studio from Microsoft, set to be released later this year) VB.Net supports a wider range of Lambda expressions.
- More people have downloaded the Express edition of VB than C# (Source: Microsoft at MVP Global Summit).
- Your sister site is VB .Net Heaven :-)
Otherwise it won't be able to recognize the other SQL server.
Just thought I'd let you know.
A few days ago, when writing an application on .Net v2, I needed to store similar settings and it had me thinking; should I use an INI file, the registry or even an XML file. The logical answer seemed to be to use an XML. So, I started searching the internet for possible solutions.
For the better part of half-an-hour I went through a number of articles, knowledge bases, forums and blogs and then it struck me. A pure and simple answer on the Microsoft MSDN forums (http://forums.microsoft.com/msdn). Why not use My.Settings?
When using My.Settings, you are actually saving the settings in the app.config file in XML format. Simply double click on 'My Project', select the 'Settings' tab and enter the settings you require for your application. Remember these settings are unique for the local machine and shall NOT be available on any other machine.
Now, when adding new settings, you need to add a name for the setting, which cannot include spaces. You need to select the type, which is the data type. You also need to specify the scope. For this you have 2 settings, either 'User' which means that this setting is a 'read-write' setting, or 'Application' which simply means that this is a 'read-only' setting. You also need to specify a value.
Now, in code, whenever you need to read a particular setting then simply use My.Settings to access the setting value. You can also save a new value to pre-defined setting. Lost? Well, so was I at the beginning; so lets show an example. Lets assume we have 2 settings, named 'Username' and 'Password' (you would NOT usually save the username and password in a settings file; this is only for demonstrational purposes). Lets also assume that we have a textbox called 'tbUsername' and another called 'tbPassword'.
In code, to read the settings into the textboxes you would simply write:
tbUsername.Text = My.Settings.Username
tbPassword.Text = My.Settings.Password
Now, assuming the user changes these and you'd like to store the new values, you'd write:
My.Settings.Username = tbUsername.Text
My.Settings.Password = tbPassword.Text
and then you'd type:
Read more here and here