Skip to main content

microsoft extends windows XP's lifecycle

heres a good news to XP fanatics . last year the rich guys from Richmond also collectively known as Microsoft announced that they will stop shipping windows XP to hardware vendors starting January 31 , 2008 fortunately because of some moves from PC makers , they took back their statement and reschedule it for june 30 , 2008 . now heres another shocker , realizing how resource-hungry their new flagship product is ( we all know it by the name of Vista ) they made another statement saying that they are extending Windows XP for another two years ! but , only PCs which Microsoft deems ultra-low cost will be able to use Windows XP. so you would expect that most of the machines coming out this year will carry Vista . what ? yes , we may not want it but Vista will be on them .

on a personal note , i am using Vista Ultimate now on my development machine with 3.5G of RAM . its not that i asked for it , its by coincidence . the interface is nice but performance wise , i'd rather be developing on XP machines . unfortunately , this is just one of the many changes that we have to accept and we have to live with everyday . as i always say , if you hate how microsoft runs the industry , be open and grab yourself a linux . a move that i have always been dreaming about but i could not make it happen . why ? my job requires me to love microsoft !!

Comments

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, …