Of course Visual Studio 2005 doesn't compile for .NET Framework v1.1. Of course you can't (easily) buy Visual Studio 2003 new. Who would want to do that? Well, me for one; at least until Adobe releases some Flash Remoting components for .NET v2.0.
In lieu of any built-in backwards compatibility support from Microsoft, there are a number of community solutions for Flash/Flex developers who through one circumstance or another are using VS2005 (or, of course, anybody else who wants to target v1.1 from VS2005). Microsoft has adopted MSBee as a VS Powertoy, so I guess that's as close to official as you're gonna get -- It's even got a fancy .msi installer. Jomo Fisher's blog entry explains what I suspect is going on under the hood of MSBee, and Gustavo Guerra created a build targets file that includes Mono and .NET Compact Frameworks, though it seems to be missing from Gustavo's link in that forum entry.
Of course, you could try to go the other way and fix Remoting instead of Visual Studio, which is what the developers of Flourine are trying to do with an Open Source (GNU Lesser GPL) Remoting library which supports both .NET v1.1 and v2.0. You have to build the gateway dll yourself, but once you do, you can use the wizard they provide for VS2003 or VS2005 to create and configure a project for your Remoting services.
Yep, this is all old news, but it took me a few hours to put the pieces together to figure out why my new Remoting services dll was telling me there was "No Such Service" when all I did was rebuild a dll that had been working just fine before. So here's hoping that this entry, with all the keywords I was using all in one place, finds its way into another set of Google search results and saves someone else a few hours.
Post new comment