I uploaded a test website that demonstrates the issue. Please see
http://groups.google.com/group/castle-project-users/web/WindsorTest.zip
Thank you!
On Jan 26, 8:08 am, Krzysztof Koźmic krzysztof.koz...@gmail.com
wrote:
were you able to create a reproduction you could post here?
Krzysztof
Mark,
Windsor is fine.
Your class does not implement that interface.
Krzysztof
On 26 Sty, 13:48, Mark Richman markarich...@gmail.com wrote:
I uploaded a test website that demonstrates the issue. Please
seehttp://groups.google.com/group/castle-project-users/web/WindsorTest.zip
Thank you!
Try commenting out the component line in web.config, and uncomment
the line in Global.asax. You'll see it works fine using it that way.
So, what's wrong with my syntax in the web.config? This worked until I
upgraded Castle.
On Jan 26, 8:19 am, Krzysztof Koźmic (2) krzysz...@kozmic.pl wrote:
Mark,
That's what I did. You did succeed at registering the component,
because AddComponentLifeStyle does not check if you pass valid types.
However if you tried to resolve the component you would get an
exception then.
Krzysztof
On 26 Sty, 14:23, Mark Richman markarich...@gmail.com wrote:
Try
Thanks, we can track issue at
http://support.castleproject.org/projects/AR/issues/view/AR-ISSUE-280
On 22 Sty, 15:09, Krzysztof Koźmic (2) krzysz...@kozmic.pl wrote:
To send a bug report use donjon:http://support.castleproject.org/projects/AR/
On 22 Sty, 13:53, Bartosz Pierzchlewicz
It actually resolves the instance just fine. I can even step into the
implementation class' source code while debugging. I have a helper
class called GenericTypeResolver which I use to resolve component
instances from the container. I call the helper on this component as
follows:
var urlsProvider
I tried both clear/ and removing the StaticFileHandler like so:
handlers
remove name=StaticFile /
add name=Monorail path=*.html verb=*
modules=IsapiModule
scriptProcessor=%windir%\Microsoft.NET\Framework
\v2.0.50727\aspnet_isapi.dll
Other than the check that throws the exception (rightfully so) that
was added, no other changes were made for this release in this part of
the codebase.
My guess is that recently someone from your team made a change either
to inheritance structure or to the registration in the .config file
and
I'm actually the only one working with this code...regardless, thanks
for your help and I'm glad I was able to get past it! Please let me
know if I can do any future beta testing for you to reciprocate.
On Jan 26, 9:49 am, Krzysztof Koźmic (2) krzysz...@kozmic.pl wrote:
Other than the check that
Finally got it sorted. Looks like I had to do several things. Here's
the mappings:
handlers
remove name=StaticFile /
add name=Monorail path=*.html verb=*
modules=IsapiModule
scriptProcessor=%windir%\Microsoft.NET
great news:) I'm glad it sorted out for you at the end.
On Tue, Jan 26, 2010 at 5:16 PM, JakeS jakesteven...@gmail.com wrote:
Finally got it sorted. Looks like I had to do several things. Here's
the mappings:
handlers
remove name=StaticFile /
I am working on a project where we are using WcfIntegration to create
client-proxies. Typical code is shown i text below:
public void Init()
{
var container = new WindsorContainer();
container.AddFacilityWcfFacility();
WSHttpBinding binding;
binding = new WSHttpBinding
12 matches
Mail list logo
