I can't believe it. Same thing happened last time. I spend hours, if not days dealing with a problem i have.
Once i can't take it any more, i decide it's worth a post to ask for some help. And once i posted, five minutes later, i think of something new, try it and fix the problem. Well in this case, it's not fixed, but i found out that it comes from the custom HttpHandlerFactory i'm using. I'm going to compare it with the one in the source code to see if it's missing some registration process for the components. Sorry for polluting. On Feb 23, 4:38 pm, Allan <[email protected]> wrote: > Hi all, > > I recently upgraded several websites from RC3 to the net-2.0 branch. > After a few quick and easy refactoring, i got it to compile and run. > > I then encountered a problem with the view components we have defined. > > I got the message "Castle.MonoRail.Framework.MonoRailException: > ViewComponent 'FieldErrorComponent' could not be found. Was it > registered? ..." which i saw in other posts on this list but they all > mention windsor and how components should be registered with the > container. > > However we are not using windsor Integration. We used to just simply > give the Assembly containing the view component (different to the > website's) in <monorail><viewcomponents><assembly> in the Web.Config > file. > > The component extends ViewComponent, and overrides Initialize and > Render. > > Is there anything that has changed in how components are being handled > and how to define our own components > without using windsor integration? > > Many thanks for your help. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
