Castle Windsor for Win8 RT?

[Lundberg, Per]

Hi!

 

Has anyone investigated how hard it would be to port Castle Microkernel and Castle Windsor to Windows 8? (making it possible to use our favorite IoC controller when writing Windows 8 apps, i.e. “Windows Store” apps.)

 

Best regards,

Per

 

[Berke Sokhan]

Hello Per,

What is preventing you to run current Castle projects in Windows 8?

2012/11/7 Lundberg, Per <Per.Lu...@ecraft.com>

--
You received this message because you are subscribed to the Google Groups "Castle Project Users" group.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.

--
Berke SOKHAN.

http://twitter.com/berkesokhan
http://blog.berkesokhan.com
http://www.birliktegelistir.com/editors.aspx

[Lundberg, Per]

Hi,

 

The current version of Castle works correctly under Windows 8, AFAIK, if we are talking about regular .NET mode.  What I’m talking about more specifically is “WinRT mode”, i.e. for Metro-style apps. (those that run as tiles on the Windows start screen.) Such applications don’t access the full .NET Framework, but a much more limited subset of the .NET Framework where .e.g Reflection.Emit seems to be missing… Did a futile attempt to compile Castle.Core on this platform with around 500 compiler errors so I think there is some work needed… :-)

 

http://en.wikipedia.org/wiki/Windows_Runtime

 

Then again, they have the DLR languages running on WinRT I think, which means that it *must* be possible somehow to generate dynamic code.

 

Best regards,

Per

[Krzysztof Kozmic]

Hi,

Yeah, currently there's no plan for WinRT version of Windsor. As mentioned certain APIs that Windsor relies on (like reflection emit) are not available at all, whereas some other APIs are severely limited.

So to port WIndsor to WinRT would be a significantly more complex task than, say, Silverlight version, since many features would have to be rewritten and possibly removed.

About DLR, as far as I know, it uses System.Expression classes to do dynamic code.

-- 

Krzysztof Kozmic

[hammett]

The spirit of OSS is that you contribute the things you feel are
missing. Complaining wont get you far.

Btw, the WinRT api surface is supposed to be a more modern view of the
general framework, and shouldnt be too far apart from SL. So
strategically it's a good idea to start experiment with it.


On Mon, Jan 7, 2013 at 6:14 PM, Jon Rista <jri...@gmail.com> wrote:
> Hi Krzysztof,
>
> I'm really bummed to hear you say there are no plans to migrate or port
> Windsor to WinRT. Even if some features would have to be dropped, Windsor
> is...hands down...my favorite IoC container. I've used it for years, love
> every bit of it, and will greatly miss it developing Metro apps. If there
> are no plans to port Windsor...is there any chance you might create a Metro
> (RT)-specific IoC container instead? I love your approach to IoC, and I
> honestly can't really imagine not having that amazing power in the Windsor
> way (even part of it) at my finger tips. It seems the only alternative I
> might look to, Ninject, is also lacking a version compatible with WinRT...
>
> It's a barren IoC landscape for Metro, it seems... :'( Sad day...sad day...

> To view this discussion on the web visit
> https://groups.google.com/d/msg/castle-project-users/-/Td8Tf6PyrMwJ.

>
> To post to this group, send email to castle-pro...@googlegroups.com.
> To unsubscribe from this group, send email to
> castle-project-u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/castle-project-users?hl=en.



--

Cheers,
hammett
http://hammett.castleproject.org/