Making something a .Net application does not nessecarilly mean it's future proof. One of my old clients just payed me a sizable sum of money to upgrade their .NET 1.1 tools, so that they would work on .NET 2.0, and I have no doubt that in a few years they'll be doing the same to upgrade to .NET 3.0. Then 4.0 and so on. Face it. History tells us that Microsoft need at least 5 versions of something to get it just right (DOS 5.0, DirectX 5.0, Windows 2000 [which was really Windows NT 5.0]). So maybe by the time we have .NET 5.0 it would be worth seriously considering but until then, I don't see .NET offering much, except a simpler (if inconsistant and constantly changing) API than Win32.