Replaceing the default difference/merge tool in Visual Studio with WinMerge is fairly easy, but I keep forgetting, so I figured I'd do a quick write-up.

Subversion (SVN)

After installing WinMerge, in Visual Studio, go to 

Tools -> Options -> Source Control and depending on your Source Control selection (in the case here Subversion) look for a 'Tools' menu (with Subversion its under Subversion User Tools):

If you are using Subversion/TortoiseSVN you can simply select WinMerge from the 'External Diff Tool' and 'External Merge Tool' combo boxes:

As always feel to ask or comment.

Hi All,

Just a quick extension this time.

This one returns an IEnumerable<T> where all source items that fulfills a given conditions has been removed.

I've called it RemoveWhere.

Anyway - here you are:

Can be used as:

As always feel to ask or comment.

Hi,

In this post I will gather my Visual Studio code snippets

First a snippet for creating a property and backing field, and raising OnPropertyChanged when the backing field has changed.

It will create the following code:

Another one for creating a 'lazy loading property' or 'self initializing property'

It will create the following code:

Very often I call my return variable 'result', so a snippet that 'return result' would be nice for me. Here it is:

and the output:

As always feel to ask or comment.

In Visual Studio (at least 2017) you can add a WPF Window to a WinForms project by slighty modifying the .csproj file.

Just add

To the end of the first

 tag.

It ends up looking something like this:

As always, feel free to comment, or ask.

Her follows a simple WPF DataGrid.

In the Visual Studio Design view it look like this:

The DefaultButtonStyle and DefaultDataGrid style can be found elsewhere in this blog.

Ill include the XAML for the entire Window.

Allthough using the MVVM design patten, I've opted to handel  event in the codebehind, as in my opinion this is View releated. Here is the event handler

As always, feel free to comment, or ask.

The System.Linq.Distinct extension returns a list (or more to the point, an IEnumerable<>) of ... surprise ... distinct items in a list.

This is all well and good for simple data types (e.g. integers). But what if you have more complex data types, and you want to get a distinct list based on a specific property.

Well - Distinct extension enumerates the Object.Equals method on all items in the list, and returns a new list list based on the result. An object is only equal to another object if they have the same hash code. So running List<T>.Distinct() would only exclude items from List<T> where T are the same object, and not items with the same information.

Say you have a Student type:

And a Class:

Running 

would give you 3 items, as both "John Doe" have unique HashCode - they are not the same object.

There are two ways of getting about this.

Either override Object.Equals(object obj) and Object.GetHashCode() on the Student type:

This executes fairly fast, but you would only be able to get unique items based on their ID.

If you want a more customisable way, you could write an extension:

and user it like this:

As always, feel free to comment, or ask.

You can delete a TFS branch from the Visual Studio Developer Command Prompt, using the 'tf destroy' command. The syntax is as follows:

C:\tf delete $/TeamProject/Branch

This is also valid for folder or files.

C:\tf delete $/MyTeamProject/Folder
C:\tf delete $/MyTeamProject/Folder/File

Of course remember to put any Branch/Folder/Files with spaces in, inside quotes:

C:\tf delete $/MyTeamProject/"Branch No 1" 

As always, feel free to comment, or ask.

Getting an ancestor property value can be done by binding to its element name. Here's an example

As always, feel free to comment, or ask

Sounds like there are som exciting new stuff in waiting for C# programmers.

Personally, I've never like tuples, but it looks like they are going to make sense, since you can now give the var's names.

Anyway - a link to the 2016 build presentation: https://channel9.msdn.com/events/build/2016/b889

And here is another from the Visual Studio 2017 Launch: https://channel9.msdn.com/Events/Connect/2016/105?ocid=player

More from the VS2017 Launch: https://channel9.msdn.com/Events/Visual-Studio/Visual-Studio-2017-Launch/140

WPF Controls has no ‘InvokeRequired’/’Invoke’ like WinForms, so making accessing a WPF Window/Control threadsafe can be accomplished by using the System.Windows.Threading.Dispatcher. Here are some examples. First a property: 

  A void method

And lastly a method with a return value

As always, feel free to comment, or ask.