My personal opinion:
1. I've never used it, so I won't miss it if it goes away
2. I have to say that when I started with Monorail the wizard was very
helpful in setting up a project/solution.
Now, I don't tend to use it at all :(
To me what is important is to have something that quickly sets me
up so I can start to do my work, so I guess empty sample projects like
the one that comes with "VS new web service application" would do the
job quite well.
3. I think this would only be useful if you user NVelocity templates.
4. Yes please use the trunk versions, that is what I use currently and
not going back!
In regards to that, and now that the castle projects have been
split, has anyone consider multiple Msi's (multiple installers)? The
reason I ask is because of point1, and I'm not sure if it's going to
be an easy task to coordinate updates to one single Msi and different
versions of project releases and dependencies?
5.It would be nice to have things like:
- Toggle between container integration or not for Monorail
projects;
- Add new view(whatever view engine) I currently do this with
Resharper templates
- Add new controller, filter, .... (not sure if these would be
useful)
- And definitely most important, something to add/test routing
entries in monorail projects
6. No, VS2008 only
On Jan 22, 12:19 am, Jonathon Rossi <[email protected]> wrote:
> The current VS new project wizards are out of date with Castle and with
> supporting VS2008. I have a few questions I want to ask everyone about there
> thoughts in this area. Feel free to reply to as much or as little as you
> like.
>
> 1. Personally, I don't know if a ActiveRecord project template is very
> useful because you can use ActiveRecord in different ways (ActiveRecordBase
> or not), while the current wizard seems to be promoting ActiveRecordBase
> when most of us don't use it. Do we really need this wizard since it is
> pretty basic? The real question is, do you see it helping new users over a
> getting started page in the docs or a basic sample project included in the
> docs?
>
> 2. There are also quite a few ways to set up MonoRail, so I propose we cut
> the functionality of the current wizard back to a basic wizard that builds
> you an instantly runnable MonoRail app (with your choice of view engine),
> where you can then use the docs to set up more complex things. This comes
> back to the point of do we really need new project wizards, are empty sample
> projects enough? New users to castle are welcome to reply with their opinion
> to this.
>
> 3. Does anyone see value in integrating Castle Visual Studio Integration
> from the contrib with the new project wizards (all installed from one
> installer)?
>
> 4. Does anyone see a problem with the Castle MSI being released with the
> newest build of each project, with some being built from the trunk until
> they have an official release, as long as the installer specifies what
> versions it comes with?
>
> 5. Are there any VS integration features that we should be employing to make
> any Castle project easier to use?
>
> 6. Does anyone see any problems with dropping support for VS2005 since we
> are only supporting 3.5 from now on?
>
> --
> Jono
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" 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-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
