Official Castle Project feedback forum

Welcome to the official feedback forum for Castle Project. Do you have an idea? Do you recognize a good idea when you see one? Than share it!

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Support WinRT and Windows 8-style apps

    Add support for the Windows Runtime and Windows 8-style applications.

    13 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    • Add a new category in debug visualizer for Castle Windsor

      The debug visualizer lists components that may be misconfigured, because the container does not know how to resolve all their dependencies. However, components show up here even if there is also registered a factory that will supply these dependencies. So, I don't really see these as "potentially misconfigured", though certainly some code could ask the container to resolve directly rather than going through the factory.

      I'd still like to know about these components, but they seem a bit "noisy" when lumped with components that really cannot be resolved.

      I think it would be helpful to add a separate category to…

      1 vote
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        under review  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
      • [DP] Unify proxy creation API

        Instead of current four types of proxies that add to the steepness of the learning curve for DP (and have their downsides) DynamicProxy should expose single type and single method (with overloads) that would handle different scenarios while not requiring user to learn too much lingo.

        More on it here (with sketches of the API and some discussion): http://using.castleproject.org/display/CASTLE/Dynamic+Proxy+3+design+meeting

        1 vote
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          0 comments  ·  Flag idea as inappropriate…  ·  Admin →
        • [DP] Add Type Wrapping

          Type Wrapping would allow to wrap a type with another type (without inheriting from it) and mimic it's public interface (without overriding it) to add dynamic proxy capabilities to sealed methods/classes. This would work with scenarios that don't rely on the actual type, like WPF data binding or C# 4.0 dynamic.

          More on it here: http://using.castleproject.org/display/CASTLE/Dynamic+Proxy+3+design+meeting

          7 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            5 comments  ·  Flag idea as inappropriate…  ·  Admin →
          • Add a resolve method like ResolveInScope<IFoo>(IDisposable scope [, object args])

            We have implemented the new(?) LifeStyleScope. We begin a new scope for each new dialog/window to enable e.g. an optimale use of unit of works. It works well, but I had a lot of trouble to enable using factories (for our view models). Reason: because the components are created lazily within a factory, Windsor cannot select the correct instance. What we have done is to also make the factory's lifestyle scoped and pass all scoped components to it right after creation. The factory then passes those cached components as anonymous types during creation. That works for most scenarios.

            What I…

            6 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              0 comments  ·  Flag idea as inappropriate…  ·  Admin →
            • Include samples in each project's release

              Please include in each project's release its sample application from /trunk/Samples (new samples are also welcome).
              This will help the new users to start using the projects.

              18 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                1 comment  ·  Flag idea as inappropriate…  ·  Admin →
              • Don't see your idea?

              Official Castle Project feedback forum

              Feedback and Knowledge Base