Sammani Palansuriya

Visual Studio have brought some new facilities which makes the developers to debug their code in a more effective manner. Thought of blogging some of some fancy features which seems very tiny things but makes our lives easier. 1. Labeling Break Point Now you can add labels for your break points which in a way supports to categorize the breakpoints. By using this features we can enable or disable list of break points as we want based on the category. You can write click on a break point & then click on Edit Label. Then you will get the following dialog where you can add the label. It will list down the existing labels so that you can reuse it. After you label your breakpoints you can get the list of breakpoints in your solution in the breakpoint window. Breakpoint window can be found in Debug –>Windows->Breakpoints. Now VS 2012 have this fancy featues where we can search any tool using the quick search. If you all are not sure about where exacly the to...

When we working with collection of objects & when we need to select the distinct objects out of it, linq Distinct() does not work as we expect.That supports to get the distinct of some know types like,string, Guid, int and etc. What if we need to get the distinct members of a collection where collection is made up of complex object type. You can use the following code snippet. Suppose the Class is Defined as follows where each member object will have a unique name for it. public class Member { public string UniqueName{get;set;} public int MemberLevel{get;set;} public string HeirachyName{get;set;} } List<Member> memberCollection=new List<Member>(); if we want to get the distinct members from the above collection. List<Member> DistinctMember=memberCollection.GroupBy(x=>x.UniqueName).Select(x => x.ElementAt(0)).ToList(); This will select the distict member objects from the collection.

WCF 4.5 supports contract first development. Means it allows to create all the data contract classes can be auto generated using the WSDL. one of the advantage in using the is if we start developing the service from the data contracts & then generating the WSDL we might end up in creating from data contracts with .net specific data types. But when using contract first development as WSDL is xml based only xml based data types are allowed to create so no .net specific contract will be created. This feature can be very useful when WSDL file is produced through design phase either by a solution architect or through mutual parties that agree on a contract prior to development and build phases.  When this is the case, either the contract can be created for a future service implementation or contracts can be created so that developers can begin coding for the client side of an interface prior to the endpoint being available. The contract-first tool is integrated into Visual Studio 2...