Portable Class Library - Visual Studio 2012

Usually a traditional class library in .NET is capable of targeting only one framework ver. But many times you may want to build a class library which can target multiple versions of framework. I.e. the objective is to achieve cross-platform development of .NET Framewok applicatioans. This became a possibility with the release of Visual Studio 2012.

Visual Studio 2012 includes a new project template named Portable Class Library, As you can see in the image below, you can use this project to build portable assemblies that work without modification on multiple platforms like:

1- Windows 7, Windows 8

2- Silverlight

3- Windows Phone, and

4- Xbox 360

T














his project is pretty much like a Class Library project, except its References shows “.NET Portable Subset” instead of individual namespaces.

If you are targeting only one particular framework as many enterprise applications do, then standard Class Library project is the best choice.

Top 5% most viewed at LinkedIn

Value of Knowledge

A giant ship engine failed. The ship’s owners tried one expert after another, but none of them could figure out how to fix the engine. Then they brought in an old man who had been fixing ships since he was a young. He carried a large bag of tools with him, and when he arrived, he immediately went to work. He inspected the engine very carefully, top to bottom. 

Two of the ship’s owners were there, watching this man, hoping he would know what to do. 

After looking things over, the old man reached into his bag and pulled out a small hammer. He gently tapped something. Instantly, the engine lurched into life. He carefully put his hammer away. The engine was fixed! 

A week later, the owners received a bill from the old man for ten thousand dollars. “What?!” the owners exclaimed. “He hardly did anything!” So they wrote to the old man saying, “Please send us an itemized bill.” 

The man sent a bill that read: 

Tapping with a hammer…… …… ……… $ 2.00

Knowing where to tap……… …… ……… $ 9,998.00 

Moral :- Effort is important, but knowing where to make an effort makes all the difference! Keep studying hard. Don’t give up!

 

Why .NET 4.5 doesn't have a Client Profile

In this post I will explain why .NET 4.5 doesn't support and what is the benefit .NET 3.5 and .NET4.0 provides with their supported Client Profile flavor.
As we all know there are many type of applications and hence what is required by one application may not be necessarily required by other type of application. For example, System.Web is only used by ASP .NET / Web apps, this is of no use for Windows Forms app.

Now if you think from a deployment's point of view, you would want your installer to be as optimized and small as possible, so it takes minimum and required on the client machine, and this can be achieved by Client Profile flavor of.NET 3.5 and 4.0.
Let's see how Microsoft made .NET Client Profile.Microsoft removed ASP .NET, MSBuild, Advanced WCF and Data support for Oracle to cut the framework into smaller and optimized footprint.

.NET 4.5 is already optimized and tuned for quicker deployment and takes small disk space. Hence, no more .NET 4.5 Client Profile.