Thread: ASP to ASP.NET
View Single Post
Old 10-22-2004, 07:58 AM   #4 (permalink)
eanda9001
Upright
 
Great Feedback

Well, it would seem .net is the way to go. I am surprised that .net does not provide a persistence layer generator, this is very common in the J2EE world. JDeveloper (Oracle's IDE for Java) will generate a set of classes that mirror a database for example. You can extend the classes.

My experience is that to have a persistence layer is the way to go. I am still learning about the ADO but it seems like are really fair way to handle tables as it handles relationships etc.

Besides the fact that I have been yelling at my computer to the point I lost my voice since I am unable to get Visual Studio to install ( missing something it wants but it wont tell me what), .net seem like the best development platform currently available. I am not a MS supporter, but this stuff is just too well thought out. Way easier the J2EE which is complex beyond reasonable. C# is the best language I have ever seen and ASP.NET is basically the same functionally.

I am thinking that there will be a 100% productivity increase in .net code vs. asp. Based on that I can figure how much effort a full rewrite will take. The hardest part is going to be retraining as the development team is no OO at all. Probably need to bring in .net developers.
eanda9001 is offline  
 

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73