>I think that an application written in MR2 couldn't be converted into MR3 is a >big problem. Why choose MR3 with no assurances that MR4 will be compatible? I >suppose that most of users would like to update MR2 and keep following its >evolution, naturally.
Having moved on from, but built a big MR2 application I would suggest that if you go decide to maintanence mode MR2 and don't want to support an upgrade path to MR3, you suggest an upgrade path to ASP.NET MVC. MVC has (had?) support for Monorail view engines and its patters are similar enough it should be low effort. Not worth it for apps that are in maintenance mode, but you might want to think about it if you have an app in ongoing development. Your only problem here is fallout. Do you get bad PR along the lines of: never rely on an OS project? I don't think it makes sense as an argument b.t.w; just look at how MS mothballed L2S. But its worth giving advice here and for my part I would suggest advising MR2 customers to adopt ASP.NET MVC, so that you can get a clean break. -- 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.
