<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.oosterkamp.nl/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">Jo-wen Mei</title><subtitle type="html" /><id>http://blogs.oosterkamp.nl/blogs/jowen/atom.aspx</id><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.oosterkamp.nl/blogs/jowen/atom.aspx" /><generator uri="http://communityserver.org" version="3.1.20917.1142">Community Server</generator><updated>2009-10-01T12:35:33Z</updated><entry><title>Invoking an ICommand</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/30/invoking-an-icommand.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/30/invoking-an-icommand.aspx</id><published>2009-12-30T18:40:08Z</published><updated>2009-12-30T18:40:08Z</updated><content type="html">&lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;I wanted to reuse the logic of a Command defined in another usercontrol. &lt;/p&gt;  &lt;p&gt;The simple solution would be to create a separate, public method which I then could call from outside the control (and call this method in the Execute eventhandler).&lt;/p&gt;  &lt;p&gt;A more clean way is to directly invoke the Command!&lt;/p&gt;  &lt;p&gt;The ICommand interface supports the Execute(object parameter) method.&lt;/p&gt;  &lt;p&gt;I expose my commands as static properties, so I can have this code:&lt;/p&gt;  &lt;p&gt;SearchCommands.FilterProduct.Execute(null, SearchControl);&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;I don’t have to reference the commandBinding collection of the search control, which is very clean!&lt;/p&gt;  &lt;p&gt;You can/must specify the input-element with the implementation you want to invoke..... &lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;&lt;a href="http://blogs.msdn.com/mikehillberg/archive/2009/03/20/icommand-is-like-a-chocolate-cake.aspx"&gt;more info&lt;/a&gt;&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=289" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="WPF" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/WPF/default.aspx" /></entry><entry><title>WPF &amp; xaml guidelines</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/30/wpf-amp-xaml-guidelines.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/30/wpf-amp-xaml-guidelines.aspx</id><published>2009-12-30T18:10:00Z</published><updated>2009-12-30T18:10:00Z</updated><content type="html">&lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;Wpf and xaml has been out for a while now, so the community already knows the do’s and don’ts of programming in xaml.&lt;/p&gt;  &lt;p&gt;Thankfully, there are always some nice people who share this stuff with us.&lt;/p&gt;  &lt;p&gt;This is &lt;a href="http://dotnet.org.za/rudi/archive/2009/01/13/xaml-guidelines-released.aspx"&gt;a good resource&lt;/a&gt; and starting point. It also includes links to the channel 9 videos that give you some background info on the rationale of these guidelines.&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;Some other guidelines/info:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa511329.aspx"&gt;Designing with WPF&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/dd458877.aspx"&gt;XAML Guidelines for Creating a Composite UI&lt;/a&gt;&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=288" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="WPF" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/WPF/default.aspx" /><category term="Silverlight" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/Silverlight/default.aspx" /></entry><entry><title>Grid Size Sharing WPF</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/16/grid-size-sharing-wpf.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/16/grid-size-sharing-wpf.aspx</id><published>2009-12-16T21:32:00Z</published><updated>2009-12-16T21:32:00Z</updated><content type="html">&lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;The other day, I had to show different datatemplates depending on a specific property value. (The &lt;a href="http://msdn.microsoft.com/en-us/library/system.windows.controls.datatemplateselector.aspx"&gt;datatemplateSelector&lt;/a&gt; is your friend!)&lt;/p&gt;  &lt;p&gt;I used different foreground colors to visualize the states; however, the layout design was the same for each datatemplate.&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;I was using a Grid, and wanted to share the columnWidth’s and RowHeight’s. &lt;/p&gt;  &lt;p&gt;My first solution was specifying a double constant in xaml. Unfortunately, this doesn’t work out of the box. You would need to have a DoubleToGridLengthConverter.&lt;/p&gt;  &lt;p&gt;Then, after some searching I found this &lt;a href="http://msdn.microsoft.com/en-us/library/ms771508.aspx"&gt;Grid Size Sharing&lt;/a&gt; sample!&lt;/p&gt;  &lt;p&gt;Basically, you have to define the attached Grid.IsSharedSizeScope on the container element to set the scope of the shared sizes.&lt;/p&gt;  &lt;p&gt;Then when you set the SharedSizeGroup on a row/column definition (together with the width/height of course), other definitions with the same name will automagically adjust as well.&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;nice!&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=285" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="WPF" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/WPF/default.aspx" /><category term="Silverlight" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/Silverlight/default.aspx" /></entry><entry><title>Check some (runtime) characteristics of a dependency property</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/11/check-some-runtime-characteristics-of-a-dependency-property.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/11/check-some-runtime-characteristics-of-a-dependency-property.aspx</id><published>2009-12-11T16:52:48Z</published><updated>2009-12-11T16:52:48Z</updated><content type="html">&lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;It&amp;#39;s pretty easy to inherit from an existing control in WPF.&lt;/p&gt;  &lt;p&gt;For instance, &lt;a href="http://blog.catenalogic.com/"&gt;this great programmer&lt;/a&gt; I know has written an &lt;a href="http://blog.catenalogic.com/post/2009/10/22/WPF-ComboBoxEx.aspx"&gt;extended combobox&lt;/a&gt;. It has extra functionality, like:&lt;/p&gt;  &lt;p&gt;* Automatically select the value if only one item is available in the items source;&lt;/p&gt;  &lt;p&gt;* Disable the control when no items are in the items source;&lt;/p&gt;  &lt;p&gt;So, there&amp;#39;s logic in the inherited class that manages the IsEnabled property. &lt;/p&gt;  &lt;p&gt;Flexibility must remain, so consumers of this control should still be able to set the IsEnabled property, and overrule the default logic.&lt;/p&gt;  &lt;p&gt;Here&amp;#39;s a way to programmatically check if the property has been set:&lt;/p&gt;  &lt;p&gt;&lt;font face="Courier New"&gt;if (DependencyPropertyHelper.GetValueSource(this, ComboBox.IsEnabledProperty).BaseValueSource == BaseValueSource.Default)&lt;/font&gt;&lt;/p&gt;  &lt;p&gt;&lt;font face="Courier New"&gt;{&lt;/font&gt;&lt;/p&gt;  &lt;p&gt;&lt;font face="Courier New"&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; IsEnabled = !(IsDisabledWhenItemsSourceIsEmpty &amp;amp;&amp;amp; (_customItemsSource.Count == 0));&lt;/font&gt;&lt;/p&gt;  &lt;p&gt;&lt;font face="Courier New"&gt;}&lt;/font&gt;&lt;/p&gt;  &lt;p&gt;&lt;font face="Courier New"&gt;&lt;/font&gt;&lt;/p&gt;  &lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/system.windows.dependencypropertyhelper.getvaluesource.aspx"&gt;&lt;font face="ta"&gt;More info&lt;/font&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=284" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="WPF" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/WPF/default.aspx" /></entry><entry><title>When not implementing the ConvertBack method…</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/10/when-not-implementing-the-convertback-method.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/10/when-not-implementing-the-convertback-method.aspx</id><published>2009-12-10T20:33:48Z</published><updated>2009-12-10T20:33:48Z</updated><content type="html">&lt;p&gt;I really like WPF converters. I often don’t need the ConvertBack method though.&lt;/p&gt;  &lt;p&gt;Most programmers deal with this by leaving the &lt;font face="Courier New"&gt;throw new NotImplementedException() , &lt;/font&gt;or they return null.&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;I also see this method being marked with the [Obsolete()]&amp;#160; attribute. I think this totally gives you the wrong impression that it should not be used anymore.&lt;/p&gt;  &lt;p&gt;The attribute is used to inform &lt;u&gt;programmers&lt;/u&gt; , not the databinding system.&lt;/p&gt;  &lt;p&gt;And of course, the method is still valid and might get a different implementation later on.&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;Check out the &lt;a href="http://msdn.microsoft.com/en-us/library/system.windows.dependencyproperty.unsetvalue.aspx"&gt;DependencyProperty.UnsetValue&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=283" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="WPF" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/WPF/default.aspx" /><category term="Silverlight" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/Silverlight/default.aspx" /></entry><entry><title>WPF vs Silverlight</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/06/wpf-vs-silverlight.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/12/06/wpf-vs-silverlight.aspx</id><published>2009-12-06T20:38:09Z</published><updated>2009-12-06T20:38:09Z</updated><content type="html">&lt;p&gt;Last week, I was giving a Silverlight training in the beautiful Bergen (Norway). &lt;/p&gt;  &lt;p&gt;I have WPF experience, but I was still struggling with some demo’s because of its differences with Silverlight.&lt;/p&gt;  &lt;p&gt;Silverlight is supposed to be a subset of WPF but that’s not the case (yet). Silverlight even has functionalities that are not in WPF (yet), like the Visual State Manager.&lt;/p&gt;  &lt;p&gt;There’s a nice &lt;a href="http://wpfslguidance.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=28278"&gt;whitepaper&lt;/a&gt; that describes these differences. &lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=281" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="WPF" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/WPF/default.aspx" /><category term="Silverlight" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/Silverlight/default.aspx" /></entry><entry><title>How to debug WPF bindings</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/11/19/how-to-debug-wpf-bindings.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/11/19/how-to-debug-wpf-bindings.aspx</id><published>2009-11-19T19:04:56Z</published><updated>2009-11-19T19:04:56Z</updated><content type="html">&lt;p&gt;The databinding expert in the field, Bea Stollnitz, has a &lt;a href="http://bea.stollnitz.com/blog/?p=52"&gt;great post&lt;/a&gt; about different options to debug your wpf binding.&lt;/p&gt;  &lt;p&gt;In summary, the options are:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;The output window&lt;/li&gt;    &lt;li&gt;Trace sources&lt;/li&gt;    &lt;li&gt;Trace level (new in 3.5)&lt;/li&gt;    &lt;li&gt;Converter&lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;you’ve got to check them out, it will save you a lot of time!&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=276" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="WPF" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/WPF/default.aspx" /></entry><entry><title>Pin a debugger watch</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/11/13/pin-a-debugger-watch.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/11/13/pin-a-debugger-watch.aspx</id><published>2009-11-13T21:16:37Z</published><updated>2009-11-13T21:16:37Z</updated><content type="html">&lt;p&gt;The fact that Visual Studio has been designed in WPF exposes a ton of possibilities. &lt;/p&gt;  &lt;p&gt;Here’s a cool feature : &lt;a href="http://haacked.com/archive/2009/11/06/pinning-a-debugger-watch.aspx"&gt;pinning a debugger watch&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;Note: these &amp;quot;pinned-windows” even remain after restarting your application!&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=271" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="Visual Studio" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/Visual+Studio/default.aspx" /></entry><entry><title>Arithmetic operations in xaml</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/11/11/arithmetic-operations-in-xaml.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/11/11/arithmetic-operations-in-xaml.aspx</id><published>2009-11-11T19:53:15Z</published><updated>2009-11-11T19:53:15Z</updated><content type="html">&lt;p&gt;Many times, you want to bind a numeric value to another property AND perform some calculation over it.&lt;/p&gt;  &lt;p&gt;For instance, you would like to bind the width of your control to be half the size of its parent control.&lt;/p&gt;  &lt;p&gt;Take a look at &lt;a href="http://learnwpf.com/Posts/Post.aspx?postId=9b745fe8-7d51-4d01-a8c7-f31083c4be94"&gt;this converter&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;It enables a xaml syntax like this:&lt;/p&gt;  &lt;p&gt;&lt;font size="2" face="Courier New"&gt;{Binding ElementName=control, Path=ActualWidth, Converter={StaticResource arithConverter}, ConverterParameter=*0.5}&lt;/font&gt;&lt;/p&gt;  &lt;p&gt;&lt;font size="2" face="Courier New"&gt;&amp;#160;&lt;/font&gt;&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=270" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="WPF" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/WPF/default.aspx" /><category term="Silverlight" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/Silverlight/default.aspx" /></entry><entry><title>IObservable/IObserver are the non-blocking equivalents of IEnumerable/IEnumerator</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/30/iobservable-iobserver-are-the-non-blocking-equivalents-of-ienumerable-ienumerator.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/30/iobservable-iobserver-are-the-non-blocking-equivalents-of-ienumerable-ienumerator.aspx</id><published>2009-10-30T11:25:37Z</published><updated>2009-10-30T11:25:37Z</updated><content type="html">&lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;I’m experimenting with the new BCL updates in VS2010. One of these is the addition of the IObservable/IObserver interfaces.&lt;/p&gt;  &lt;p&gt;I’m still into grasping the whole thing, but reading this &lt;a href="http://themechanicalbride.blogspot.com/2009/07/introducing-rx-linq-to-events.html"&gt;blog&lt;/a&gt; gets me excited about this stuff! &lt;/p&gt;  &lt;p&gt;I think this could lead to a new paradigm in the world of asynchronous programming.&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=266" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="Design Patterns" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/Design+Patterns/default.aspx" /></entry><entry><title>Code Contracts in VS2010 Beta 2</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/29/code-contracts-in-vs2010-beta-2.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/29/code-contracts-in-vs2010-beta-2.aspx</id><published>2009-10-29T17:39:48Z</published><updated>2009-10-29T17:39:48Z</updated><content type="html">&lt;p&gt;Code Contracts helps to reduce bugs by helping you not write them in the first place, or at least catch them sooner.&lt;/p&gt;  &lt;p&gt;They allow the developer to specify pre- and postconditions and more.&lt;/p&gt;  &lt;p&gt;To use this stuff in Visual Studio 2008 you had to download and install a separate tool.&lt;/p&gt;  &lt;p&gt;I’m experimenting with this stuff the first time in Visual Studio 2010, and NetFx 4 contains the System.Diagnostics.Contracts.Contract class, so I assumed everything was in the box…….&amp;#160; [insert quote with assumption and f*ckup here]&lt;/p&gt;  &lt;p&gt;The only thing that ships in the SDK is the contract class - this makes it possible to author contracts and compile code containing contracts without an extra download. But the contracts have no effect in this scenario. &lt;strong&gt;So the tools need to be downloaded from DEVLABS to acquire all the functionality!!!&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;The team decided to stay out of the Visual Studio train, so they can update it more frequently. They’re trying to have a monthly release cycle.&lt;/p&gt;  &lt;p&gt;&lt;a href="http://social.msdn.microsoft.com/Forums/en-US/codecontracts/threads/"&gt;forum&lt;/a&gt; (with a link to the latest download)&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;note: after installing the tool, you should get an extra tab in the project-properties page which contains some cool settings. I had to restart Visual Studio before it popped up!&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=264" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author></entry><entry><title>Add Reference Dialog finally improved!!</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/29/add-reference-dialog-finally-improved.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/29/add-reference-dialog-finally-improved.aspx</id><published>2009-10-29T09:07:17Z</published><updated>2009-10-29T09:07:17Z</updated><content type="html">&lt;p&gt;I really dig Visual Studio, and its dev team always does an outstanding job in adding new (complex) features…&lt;/p&gt;  &lt;p&gt;That’s why it’s so frustrating they didn’t improve the “Add Reference dialog”.&lt;/p&gt;  &lt;p&gt;But I’m not aware of any dialog/feature that has been more complained about, so they could not ignore it anymore…. &lt;/p&gt;  &lt;p&gt;&lt;a href="http://weblogs.asp.net/scottgu/archive/2009/10/29/add-reference-dialog-improvements-vs-2010-and-net-4-0-series.aspx"&gt;they fixed it!!&lt;/a&gt;&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=263" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="Visual Studio" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/Visual+Studio/default.aspx" /></entry><entry><title>VS2010 Beta2 released</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/19/vs2010-beta2-released.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/19/vs2010-beta2-released.aspx</id><published>2009-10-19T17:56:59Z</published><updated>2009-10-19T17:56:59Z</updated><content type="html">&lt;p&gt;The beta2 versions of the following products are now downloadable from microsoft:&lt;/p&gt;  &lt;p&gt;Vs2010 Ultimate &lt;/p&gt;  &lt;p&gt;Vs2010 Professional&lt;/p&gt;  &lt;p&gt;Vs2010 Team Foundation Server&lt;/p&gt;  &lt;p&gt;Vs2010 Premium&lt;/p&gt;  &lt;p&gt;Vs2010 DSL SDK&lt;/p&gt;  &lt;p&gt;Vs2010 Team Explorer&lt;/p&gt;  &lt;p&gt;.NetFX 4&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;ps: this is not the complete list&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;happy testing!&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=258" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="Visual Studio" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/Visual+Studio/default.aspx" /></entry><entry><title>How to delete a Windows Service</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/16/how-to-delete-a-windows-service.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/16/how-to-delete-a-windows-service.aspx</id><published>2009-10-16T14:08:40Z</published><updated>2009-10-16T14:08:40Z</updated><content type="html">&lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;short version: &lt;/p&gt;  &lt;p&gt;you can use a command prompt and delete a service using following command: sc delete &amp;lt;SERVICE name&amp;gt;&lt;/p&gt;  &lt;p&gt;(check in the properties for the correct name)&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;&lt;a href="http://geekswithblogs.net/shahedul/archive/2006/10/13/93984.aspx"&gt;longer version&lt;/a&gt; (tnx Shahed!)&lt;/p&gt;  &lt;p&gt;&lt;a href="http://support.microsoft.com/kb/251192"&gt;more info on sc&lt;/a&gt;&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=257" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author><category term="Windows" scheme="http://blogs.oosterkamp.nl/blogs/jowen/archive/tags/Windows/default.aspx" /></entry><entry><title>Can’t connect to TFS after installing Visual Studio 2008 SP1</title><link rel="alternate" type="text/html" href="http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/01/can-t-connect-to-tfs-after-installing-visual-studio-2008-sp1.aspx" /><id>http://blogs.oosterkamp.nl/blogs/jowen/archive/2009/10/01/can-t-connect-to-tfs-after-installing-visual-studio-2008-sp1.aspx</id><published>2009-10-01T10:35:33Z</published><updated>2009-10-01T10:35:33Z</updated><content type="html">&lt;p&gt;I installed the VS2008 SP1 on our server, and couldn’t connect to the TFS anymore. &lt;/p&gt;  &lt;p&gt;As I was in the process of installing more software updates, I didn’t immediately realize which update caused these problems.&lt;/p&gt;  &lt;p&gt;So I googled on the error message: “&lt;em&gt;TF30059: Fatal error while initializing web service&lt;/em&gt;”&lt;/p&gt;  &lt;p&gt;and luckily others had the same issue and posted the solution: Install &lt;a href="http://www.microsoft.com/downloads/details.aspx?familyid=9e40a5b6-da41-43a2-a06d-3cee196bfe3d&amp;amp;displaylang=en"&gt;TFS 2008 SP&lt;/a&gt;&amp;#160; *sigh*&lt;/p&gt;&lt;img src="http://blogs.oosterkamp.nl/aggbug.aspx?PostID=254" width="1" height="1"&gt;</content><author><name>Jo-wen</name><uri>http://blogs.oosterkamp.nl/members/Jo_2D00_wen.aspx</uri></author></entry></feed>