Single Instance App on Whidbeyhttp://blogs.msdn.com/pedrosilva/archive/2005/03/09/391381.aspxIn prior versions of .NET, there were lots of discussions about how to support single-instance WinForms applications. Here are a couple of links discussed some ways to do that: here and here and here's one in C++ . For Whidbey, some of that functionalityen-USCommunityServer 2.1 SP1 (Build: 61025.2)re: Single Instance App on Whidbeyhttp://blogs.msdn.com/pedrosilva/archive/2005/03/09/391381.aspx#391428Thu, 10 Mar 2005 03:28:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:391428mattSo why isn't this in the Base Class Library instead of being VB specific? I have no real problem with referencing the VB application services from C# but it sure seems like Microsoft is trying to play the game with two competing teams again. <br>Single Instance App on Whidbeyhttp://blogs.msdn.com/pedrosilva/archive/2005/03/09/391381.aspx#391445Thu, 10 Mar 2005 06:52:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:391445どっとねっとふぁん blogSingle Instance App on Whidbeyre: Single Instance App on Whidbeyhttp://blogs.msdn.com/pedrosilva/archive/2005/03/09/391381.aspx#392292Thu, 10 Mar 2005 18:13:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:392292Pedro SilvaThis is part of the My library that Visual Basic created for simplifying some of the concepts in the .NET Framework. And, make it easier to develop applications. <br> <br>It just so happens that this class is very useful for this type of functionality (whether on VB or C#). I'm going to have to spend some time investigating some of the other stuff that's in that library, because there could be other similarly simplified concepts that would really benefit C# developers as well.