Yes...All of my tests pass when running the Windsor .Net 3.5 binaries on the .Net CLR and Mono 10.2.4. Currently my tests referencing the Mono Binaries (which I compiled myself by adding compiler directives to several files) fail with the proxying exception while running on Mono 10.2.4.
Chris On Aug 19, 11:50 pm, Krzysztof Koźmic <[email protected]> wrote: > The test with proxying exception that you mentioned - does it pass if > you run it on .NET? > > Krzysztof > > On 20/08/2011 1:33 PM, Chris Mancini wrote: > > > > > > > > > Thanks for the reply Krzysztof. > > > I have since upgraded to 2.10.4. While I have gotten a bit further > > (with the Mono binaries), a few tests (mine) still fail with the > > following exception: > > > Castle.MicroKernel.ComponentActivator.ComponentActivatorException : > > ComponentActivator: could not proxy InterceptorFixture+TestJobStep > > ----> System.TypeInitializationException : An exception was thrown by > > the type initializer for Castle.Proxies.ITestJobStepProxy > > ----> System.ArgumentException : Cannot resolve method because it's > > declared in a generic class. > > > With that said, I did run my tests in Mono 2.10.4 against the > > Castle .Net 3.5 binaries and all of my tests passed...I haven't tried > > running the Castle Tests under Mono 2.10.4, but I suspect a few will > > fail. > > > While I would rather target the .Net 4.0 CLR, unfortunately my > > requirements are to run on a Linux box...I would love to help out, as > > I find Windsor to be the premier IoC Container, but I struggle through > > Mono daily... > > > Thanks again for the reply. > > > Chris > > > On Aug 19, 6:17 pm, Krzysztof Koźmic<[email protected]> > > wrote: > >> Hi Chris, > > >> Basically the problem is no one currently is working on Mono support in > >> Windsor. Even mono Build is failing. > >> Patrick McEvoy was doing some work on getting the mono build running but > >> I don't think that ever got completed. > > >> I'm happy to release Windsor on Mono but I need someone to take > >> ownership of that and there's no one like that at the moment. > >> Also I'm not sure if we want to support Mono 2.6, or just the most > >> recent one (2.10 AFAIK)... > >> What are your reasons for not upgrading to the latest version? > > >> Krzysztof > > >> On 20/08/2011 12:18 AM, Chris Mancini wrote: > > >>> I am attempting to use Windsor 3 Beta 1 in MONO 2.6 and I am > >>> encountering a few issues. > >>> With the .net 3.5 binaries, an exception is being thrown upon > >>> constructing a WindsorContainer (i.e. new WindsorContainer()) > >>> System.ArrayTypeMismatchException : Source array type cannot be > >>> assigned to destination array type. > >>> at (wrapper stelemref) object:stelemref (object,intptr,object) > >>> at > >>> System.Collections.Generic.Dictionary`2[System.Type,Castle.Windsor.Diagnost > >>> ics.IDiagnostic`1[System.Object]].Add > >>> (System.Type key, IDiagnostic`1 value) [0x00000] in<filename unknown>: > >>> 0 > >>> at > >>> Castle.Windsor.Diagnostics.DefaultDiagnosticsSubSystem.AddDiagnostic[IAllCo > >>> mponentsDiagnostic] > >>> (IAllComponentsDiagnostic diagnostic) [0x00000] in<filename unknown>: > >>> 0 > >>> at Castle.Windsor.Diagnostics.Extensions.AllComponents.Init (IKernel > >>> kernel, IDiagnosticsHost diagnosticsHost) [0x00000] in<filename > >>> unknown>:0 > >>> at Castle.Windsor.Diagnostics.DefaultDiagnosticsSubSystem.Add > >>> (IContainerDebuggerExtension item) [0x00000] in<filename unknown>:0 > >>> at > >>> Castle.Windsor.Diagnostics.DefaultDiagnosticsSubSystem.InitStandardExtensio > >>> ns > >>> () [0x00000] in<filename unknown>:0 > >>> at Castle.Windsor.Diagnostics.DefaultDiagnosticsSubSystem.Init > >>> (IKernelInternal kernel) [0x00000] in<filename unknown>:0 > >>> at Castle.MicroKernel.DefaultKernel.AddSubSystem (System.String key, > >>> ISubSystem subsystem) [0x00000] in<filename unknown>:0 > >>> at Castle.MicroKernel.DefaultKernel.RegisterSubSystems () [0x00000] in > >>> <filename unknown>:0 > >>> at Castle.MicroKernel.DefaultKernel..ctor (IDependencyResolver > >>> resolver, IProxyFactory proxyFactory) [0x00000] in<filename unknown>: > >>> 0 > >>> at Castle.MicroKernel.DefaultKernel..ctor (IProxyFactory proxyFactory) > >>> [0x00000] in<filename unknown>:0 > >>> at Castle.MicroKernel.DefaultKernel..ctor () [0x00000] in<filename > >>> unknown>:0 > >>> at (wrapper remoting-invoke-with-check) > >>> Castle.MicroKernel.DefaultKernel:.ctor () > >>> at Castle.Windsor.WindsorContainer..ctor () [0x00000] in<filename > >>> unknown>:0 > >>> at (wrapper remoting-invoke-with-check) > >>> Castle.Windsor.WindsorContainer:.ctor () > >>> So I then attempted to compile the source myself using the MONO26 > >>> flag, and I am receiving compile errors (i.e. Unknown ISet<>). I > >>> suspect this is because the compiler directives haven't been completed > >>> vetted for MONO? > >>> Any help would be appreciated...Thanks > >>> Chris -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
