I concur with Tim about being able to use the current binaries in .NET 4.0. I'm pretty sure that Microsoft will support running .NET 2.0 assemblies on the .NET 4.0 runtime. I have recently installed .NET 4.0, but haven't done any extensive testing yet. Also, I still have .NET 2.0 installed, so I'm not sure if it will be chosen by the loader when a .NET 2.0 assembly is running.
Also, a minor correction to the use of .NET 3.5 APIs. There is some code in the NMS utility functions that take advantage of some of the new features of .NET 3.5: specifically, extension functions. There are .NET 3.5 specific versions of the assemblies that allow a cleaner syntax usage of the utility functions. You can search the code for NET_3_5 for these additions. If you are targeting .NET 3.5, you don't have to use these .NET 3.5 assemblies. You can use the .NET 2.0 versions of the assemblies just fine. If you are encountering any specific problems when running under .NET 4.0, please post a more detailed explanation so we can look into it further. Thanks! - Jim On Mon, Jun 21, 2010 at 5:26 PM, Timothy Bish <tabish...@gmail.com> wrote: > On Mon, 2010-06-21 at 17:19 -0700, slyfox wrote: > > have nms working well with activemq and c#. Does not seem like the > current > > binaries work with the new .NET 4. Are there binaries that handle this > or > > is it possible to build from source and target .NET 4? > > > > Thanks, > > Bobby > > You should be able to use the current binaries along with your .NET 4 > application, the NMS client doesn't use any .NET 4 or .NET 3.5 specific > APIs for that matter. > > Regards > > > -- > Tim Bish > > Open Source Integration: http://fusesource.com > ActiveMQ in Action: http://www.manning.com/snyder/ > > Follow me on Twitter: http://twitter.com/tabish121 > My Blog: http://timbish.blogspot.com/ > >
