Does it happen if you just create a trivial empty .NET 3.5 solution with console project that just creates the container?
@K On 28 March 2012 02:11, harlam357 <[email protected]> wrote: > One of my users has experienced the following exception. I am using > Windsor v2.5.3 .net v3.5 binaries. > > My code simply instantiates a new container as such: IWindsorContainer > container = new WindsorContainer(); > > System.TypeInitializationException: The type initializer for > 'Castle.MicroKernel.SubSystemConstants' threw an exception. ---> > System.AccessViolationException: Attempted to read or write protected > memory. This is often an indication that other memory is corrupt. > at Castle.MicroKernel.SubSystemConstants..cctor() > --- End of inner exception stack trace --- > at Castle.MicroKernel.DefaultKernel.RegisterSubSystems() > at Castle.MicroKernel.DefaultKernel..ctor(IDependencyResolver > resolver, IProxyFactory proxyFactory) > at Castle.Windsor.WindsorContainer..ctor() > > -- > 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. > > -- 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.
