http://weblogs.asp.net/rosherove/archive/2006/05/30/ShellMegaPackReview.aspxThis week I’m happy to put up an ad and review for Shell MegaPack by SSWare . I’ve used parts of Shell MegaPack by SSWare in a couple of small projects I did(Windows Forms), and was wonderfully surprised to find their controls fully featured, easy toenCommunityServer 2007 SP1 (Build: 20510.895)http://weblogs.asp.net/rosherove/archive/2006/05/30/ShellMegaPackReview.aspx#449611Tue, 30 May 2006 00:20:45 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:449611Dean HardingDean HardingLooks great. But with the EZShellExtensions.Net product, I'd be very careful writing shell extensions in .NET, because there can be a lot of versioning problems there. <br> <br>The ideal solution would be similar to ASP.NET where the .NET stuff is hosted in a totally separate process, and the &quot;framework&quot; that they provide is in unmanaged code. <br> <br>The problem isn't that you might have .NET 1.1 and .NET 2.0 extensions at the same time (which the .NET folks have tried very had to get right anyway). The problem is that if you run a .NET 1.1 application which then pops up a file Open/Save dialog, that dialog uses loads the shell into it's process, which will try to load your extension. If your extension is .NET 2.0, then it's going to crash.<img src="http://weblogs.asp.net/aggbug.aspx?PostID=449611" width="1" height="1">