I have fixed the contrib viewcomponents build, set it up in TeamCity,
removed the obsolete MonoRail2 directory and got rid of a heap of obsolete
VS2005 project files.

@Cesar: Contact Henry or Hammett offlist and they'll set you up a subversion
account for the castle contrib.

On Sat, May 23, 2009 at 3:23 AM, Mauricio Scheffer <
[email protected]> wrote:

>
> There are two repositories: the project's repository and the contrib
> repository.
> For an explanation of what contrib means, see
> http://www.castleproject.org/others/contrib/index.html
> MonoRail2 was an experiment, it's dead now AFAIK.
>
> On May 22, 2:02 pm, "Cesar Sanz" <[email protected]> wrote:
> > Do you mean, Vs2005 support will be death soon?
> >
> > BTW, this is a little confusing to me, why are there some many source
> code
> > repositories??
> > I have donwloaded thehttp://
> svn.castleproject.org:8080/svn/castlecontrib/
> > trunk, but you mention
> > another one from fisheye2, is there a way to unify this, for clarity
> sake?
> > (I am very new to all of this)
> >
> > I update daily the castle project (Good Job Guys!!!) and one thing I see
> is
> > that
> > there are two directories for monorail, one called MonoRail and one named
> > MonoRail2.. Why is that?
> >
> > What is MonoRail? What is MonoRail2?
> >
> > Thanx in advance for replying..!
> >
> >
> >
> > ----- Original Message -----
> > From: "Mauricio Scheffer" <[email protected]>
> > To: "Castle Project Users" <[email protected]>
> > Sent: Friday, May 22, 2009 10:48 AM
> > Subject: Re: MonoRail and Tree View
> >
> > VS2005 is being dropped as far as I can see (
> http://fisheye2.atlassian.com/changelog/castleproject?cs=5469)
> > I would advise you to upgrade as soon as you can.
> > It's possible that the VS2005 solution was accidentally left
> > unmaintained, especially since it's not under continuous integration
> > AFAIK.
> > I don't have vs2005 to try this.. can anyone confirm?
> > net-2.0 support is available through the net-2.0-trunk branch:
> http://fisheye2.atlassian.com/browse/castleproject/branches/net-2.0-t...
> >
> > On May 22, 12:55 pm, "Cesar Sanz" <[email protected]> wrote:
> > > thanx, although no tree view, maybe is may chance to write that one.
> >
> > > One thing I did notice is that the Contrib project do not compile..
> >
> > > I am using Vs2005 so, I opened the VS2005 solution file, there are
> > > missings files like
> > > MobileFilter.cs
> > > WhitespaceTransformFilter.cs
> >
> > > It is using automatic getters an setters (get; set;) when the correct
> for
> > > vs2005 is to use this properties with backed fields,
> > > It seams like an assembly is missing (Castle.Components)
> >
> > > Where do I report this? How can I do to improve this issues?
> >
> > > Regards
> >
> > > ----- Original Message -----
> > > From: Colin Ramsay
> > > To: [email protected]
> > > Sent: Friday, May 22, 2009 7:48 AM
> > > Subject: Re: MonoRail and Tree View
> >
> > >http://svn.castleproject.org:8080/svn/castle/trunk/MonoRail/Castle.Mo.
> ..
> > >http://svn.castleproject.org:8080/svn/castlecontrib/viewcomponents/tr.
> ..
> >
> > > On Fri, May 22, 2009 at 2:37 PM, [email protected]
> > > <[email protected]> wrote:
> >
> > > Hello,
> >
> > > Has anybody programmed a tree view for monorail, maybe a
> > > viewcomponent?
> >
> > > I want one like is in this page
> > >http://using.castleproject.org/pages/listpages-dirview.action?key=MR&;.
> ..
> > > Can somebody share a code like that?
> >
> > > It would be nice if there would be a repository of viewcomponents
> > > where we can share stuffs like that..
> > > I mean, like built in components..
> >
> > > Regards and Thanx
> >
>


-- 
Jono

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to