Quote:
|
Well I used both for a period of time. My findings are that when developing with J2EE you have a greater reusability of backend code then when developing with .NET
|
It's funny, I've been in the same situation and I prefer .NET. I've done a fair amount of Java and .NET coding and I very much prefer .NET. Regarding the reusability of backend code, I think if you place your data access code and dataset schemas in an external library you'll find that you can reuse them extensively. I have three medium to large ASP.net apps that all use the same data access layer.
Also, if you go the .net route you can use strongly typed datasets which if used properly can save you a lot of coding in the validation of business rules department.
Based on the tools that are provided with ASP.net I can't see recommending any other method.
J2EE is leaps and bounds above classic ASP and if it were a choice between those two, J2EE hands down. But it's not and I think ASP.net has some big advantages.