Amazing Graphics..EA Rocks!!!

Check these screenshots of Need for speed Most wanted...amazing graphics...EA Games rocks..

C# 3.0 - What's new?

Hello! everyone. This is festive time here in India. Yesterday we all celebrated Diwali, festival of light. I must tell you that lot of things have changed, things like playing with crackers, going out with friends and watching the way people decorated their houses using lights and ribbons. Yesterday, after having our Diwali prayer I just watched a movie (CHUCK) @ home and slept at around 11. Nothing new for me and it turned out to be yet another holiday. I wish things remained the same way as they were before.

Now let's talk technology. Microsoft have another a new set of features to C# in its third avatar. There is complete list available at MSDN, but I just wanted to add my comments to it as I study new features one by one. What I am planning is, I'll study one new feature everyday, post it here with my comments.

1. Implicitly Typed Local Variables
• Type is inferred by the expression used to initialize the variable
• Only applicable to local variable
• Variable declared using keyword 'var'
• There should be no Type with name 'var' defined in scope. Only then type inferring will work
• We should initialize the variable where we declaring it
• Initialized must be an expression.
• Local variable declaration should not include multiple variables
• Initializer should not refer to variable itself
• Some Examples: [ <=> is Same as ]
  var i = 5; <=> int i = 5;
  var s = "Hello"; <=> string s = "Hello";
  var d = 1.0; <=> double d = 1.0;
  var numbers = new int[] {1, 2, 3}; <=> int[] number = new int[]{1,2,3};
• Some incorrect use of var:
  var x; // Error, no initializer to infer type from
  var y = {1, 2, 3}; // Error, collection initializer not permitted
  var z = null; // Error, null type not permitted
  var u = x => x + 1; // Error, lambda expressions do not have a type
  var v = v++; // Error, initializer cannot refer to variable itself
• for, foreach and using (resource acquisition) can also use var. Like,
  int[] numbers = { 1, 2, 3, 4, 5 };
  foreach (var n in numbers) { //Do some thing }
• COMMENTS
  Why do we need to use var? Everything should be Type Strict. I think this will impact performance as compiler will use some kind of intelligence to find out variable type and it will surely take up some time. This is no scripting language...man this is C#. It will just complicate things even more and add to huge list of keywords that we already have like sealed, virtual, override, abstract, new, internal etc. I don't see any use of this so called added feature. Please let me know your opinions.
  

Currently Listening To: Shadow of the day-LINKIN PARK
~eNjOy cOdinG~

Debug ASP.net apps on VISTA

There is a lot of criticism going around regarding debugging capabilities of Windows VISTA and Visual Studio 2005. A lot of guys that are using Vista Home (cheapest and all laptops comes with HOME) think that it's only a problem with Vista Home edition and MS must have done this as a marketing gimmick. I think this is not true. Last night I was not able to debug a simple web application on my computer, that's running Windows Vista Ultimate X86 edition. So I just googled for few seconds and solution was in front of me.

You can either go to msdn web Dev blog or check out steps and links given below. Actually all the content that you see below is just copy pasted from above link. So it will be much better if you check out the link.

The Visual Studio team has just released a down loadable hot fix, which fixes problems resulting in such errors, and also enables the ability for Visual Studio 2005 to F5 debug web applications on IIS7 in Vista Home versions.

The following steps should be done to properly configure your IIS7/Vista environment for building ASP.NET web applications using Visual Studio 2005:

1. Install Visual Studio 2005 SP1
2. Install Visual Studio 2005 Update for Vista
3. Install Visual Studio 2005 hot fix for F5 authentication errors
4. Configure required IIS7 components
5. Run Visual Studio using the "Run As Administrator" option on the right-click menu

Currently Listening To: What Have I done-LINKIN PARK
~eNjOy LiFe~