Pakistan's software industry recently feted some of its own success stories, handing out awards for various products. The achievements highlight Pakistan's growth as a destination for outsourcing thanks to its skilled and relatively inexpensive labor pool.
To read more please follow: http://www.ecommercetimes.com/story/65046.html
Confused…. Yes, now a local variable (method level variable) can be declared without declaring its type In Csharp 3.0, something new to Csharp. The type is then infered by the value assigned to it. Once you assign a value to such variable then it’s type is infered by the compiler and thus making it type safe. Following are the impliaction towards it uses.
1) Can only be defined in local scope (Mehtod level).
2) Declaration must follow var keyword i.e. var myVariable = (value | Expression). Please note that if you are declaring and assigning a var type with a literal then it is much wiser to use explicitly typed variable 
var myVar;
var myVar = row["SomeColumn"]; // Where row is of type DataRow and contains.
var myVar = 0; //Valid but since you know the type in advance it's not a good style use int myVar = 0;
var myVar = [Some expression];
3) Implicity type identification is not to be mixed up with Variant type in VB and Boxing and Generics in Dotnet. Variant is such a type whose type is variable or can be changed. Boxing and UnBoxing at the otherhand are performed at runtime and so does some part of Generic implementation is. At the other hand implicit type inference is completely compile time and doesn’t effect performance of your code. It is just that the compiler infer the type and then replace it in the declaration at the place of var keyword (just thinking abruptly).
4) Initialization with null is not supported by these variable. i.e. you can’t use the following.
var myStringOrObject = null; //Invalid statement. No way for the compiler to infer.
if (someThingIsTrue)
myStringOrObject = MyClass.MyMethodWhichReturnsObjects();
else if (someThingElseIsTrue)
myStringOrObject = MyClass.MyMethodWhichReturnsStrings();
if(myStringOrObject == null) //Sequence of actions goes here.
else if (myStringOrObject is String) //Sequence of actions goes here.
else if (myStringOrObject is Object) //Sequence of actions goes here.
Consider the following block of code…
//Csharp code snippet..Line 1: Thread t = new Thread (Go); // Assume Go is some static methodLine 2: t.Start();Line 3: t.Join(); // Wait (block) calling thread until thread t ends //End
- In calling thread at line 1 we created a thread object.- On Line 2 we started the thread t.- Then on line 3 we are calling Join() method of Thread t which serves the other way around. I mean if you think logically t.Join() causes the calling thread to wait untill thread T completes.
The join() method is a busy waiting technique… i.e. The main thread is engaged in a continuous
loop checking for thread t.IsAlive property to be false. t.Join() syntax is also an invalidation of an important OOP concept, “Encapsulation”… i.e. in t.Join() we are actually blocking Main thread instead of working on Thread t.
I don’t know how many of you agree that logically it should be the other way around (i.e. Oneshould be calling Thread.CurrentThread.Join(t) instead of t.Join()).
Any one thinks of a reason why the Thread.Join() method was implemented like this??
Many of us might have heard the term Surface Computing and for those who didn’t, “Its the term for the use of a specialized computer GUI in which traditional user Interface elements are replaced by everyday objects. Instead of a keyboard and mouse, the user interacts directly with a touch-sensitive screen.” Hence a surface computer is a computer that interacts with the user through the surface of an ordinary object, rather than through a monitor and keyboard.
Earlier work in this area was done at the University of Toronto, Alias Research, and MIT. However Recent minor innovations in the surface computing field are attributed to Apple, Inc and to Microsoft Corporation. Apple had demonstrated surface computing interfaces intended for professional use since 2006, with no expected product release date. Microsoft unveiled plans for the Microsoft Surface in May 2007. The Microsoft Surface (code name Milan) seems to be closer to production. Finally, there is Linux surface computing software aswell, called Linux MPX.
The Surface is a horizontal display on a table-like form. Somewhat similar to the iPhone, the Surface has a screen that can incorporate multiple touches and thus uses them to navigate multimedia content. Unlike the iPhone, which uses fingers’ electrical properties to detect touch, the Surface utilizes a system of infrared cameras to detect input. Uploading digital files only requires each object (e.g. a Bluetooth-enabled digital camera) to be placed on the Surface. People can physically move around the picture across the screen with their hands, or even shrink or enlarge them. This could be the next generation of KIOSK. Below is the diagram from Microsoft Surface (Codename Milan).
1. MultiTouch Screen: This is the multitouch screen display. The Surface is so far advanced than we could imagine that it can recognize objects by their shapes or by reading coded “domino” tags when placed on the table.
2. Infrared: Used for collection input/s. When objects touch the tabletop, the light reflects back and is picked up by multiple infrared cameras.
3. CPU: Surface uses many of the same components found in everyday desktop computers.
4. Projector: These are set of projectors inside to display images.
references: http://www.microsoft.com/surface/index.html
As we all know we are entering into cloud era where to build an application like Youtube, mySpaces, etc an individual does not have to worry about massive infrastructure to serve millions of user requests, data centers, database space, memory, scalability and moreover administration and maintenance of such a big infrastructure. Amazon, Google and Microsoft have provided us these infrastructure for minimal cost and with application platform to build such big applications.
Amazon is in cloud business for quite long time with its Amazon Web Services, S3 (Simple Storage Service), EC2 (Elastic Compute Cloud) and SQS (Simple Queue Service) services, Google have provided this platform few moths back with its GAE (Google App Engine) and BigTable for Data Storage and now Microsoft came up with its Windows Azure, Live Services, .Net Services, SQL Services, Dynamics CRM Services, etc. Now an individual or small firms can easily access world level ground to compete with old big giants. Good thing is that Google and Microsoft have provided these services initially free to a certain limit so any one can start building such application right now without any constraint.
Below is an article explaining the advantage of cloud war to Asian software firms and individuals.
http://www.zdnetasia.com/news/software/0,39044164,62048490,00.htm
