[Test]
public void TestStandardInstance()
{
MockRepository mockRepository = new MockRepository();
IShowDialogCommand showDialogCommand = new ShowDialogCommand();
IWindsorContainer container = new WindsorContainer();
public class ShowDialogCommand : IShowDialogCommand
{
}
public interface IShowDialogCommand
{
}
}
the above unit tests produce these errors:
Error 1 TestCase
'SigmaDelta.Test.ShowDialogCommandFixture.TestDynamicMock'
failed: Castle.MicroKernel.ComponentNotFoundException : No component
for supporting the service SigmaDelta.Test.IShowDialogCommand was
found
at Castle.MicroKernel.DefaultKernel.get_Item(Type service)
at Castle.Windsor.WindsorContainer.Resolve(Type service)
at Castle.Windsor.WindsorContainer.Resolve[T]()
at SigmaDelta.Test.ShowDialogCommandFixture.TestDynamicMock() in X:
\SigmaDelta\Trunk\Code\SigmaDelta\SigmaDelta.UnitTests\MVP
\Class1.cs:line 19 X:\SigmaDelta\Trunk\Code\SigmaDelta
\SigmaDelta.UnitTests\MVP\Class1.cs 19
Error 2 TestCase
'SigmaDelta.Test.ShowDialogCommandFixture.TestStandardInstance'
failed: Castle.MicroKernel.ComponentNotFoundException : No component
for supporting the service SigmaDelta.Test.IShowDialogCommand was
found
at Castle.MicroKernel.DefaultKernel.get_Item(Type service)
at Castle.Windsor.WindsorContainer.Resolve(Type service)
at Castle.Windsor.WindsorContainer.Resolve[T]()
at SigmaDelta.Test.ShowDialogCommandFixture.TestStandardInstance()
in X:\SigmaDelta\Trunk\Code\SigmaDelta\SigmaDelta.UnitTests\MVP
\Class1.cs:line 31 X:\SigmaDelta\Trunk\Code\SigmaDelta
\SigmaDelta.UnitTests\MVP\Class1.cs 31
....
Am i doing something wrong? or is this a problem in Windsor/RC3?
Roelof Blom
unread,
Jan 28, 2008, 9:51:42 AM1/28/08
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to castle-pro...@googlegroups.com
Hi,
I am not sure if it's a bug, but it looks like it because this call behaves differently on trunk.