Rip,

>>If you want to write a lot of code waiting for MS to deliver two-data binding in ASP.NET but I don't.<

Ya know, it didn't take a whole helluva lotta code to implement two-way data binding in ASP.NET. I did it and it simply wasn't that hard.

>> If you implement it in your own framework aren't you going in a direction all your own?<

Hmmm, well, unless Microsoft implements something that's totally compatible with the way Kevin has done it, then it could be problem there too. Who knows ...

~~Bonnie



>>Yet another who doesn't get the point! I'm not specifically attacking MM.NET, I'm just saying a commercial framework will never be quite as flexible as your own.
>
>Only if you build a good one.
>
>>It doesn't take that many hours of experience, at least not many more then learning a commercial framework like MM.NET. I think most of the people in here know HOW to write a flexible Data Access class, (at least I hope). I mean there are some serious conceptual changes of .NET from other languages, but those need to be learned no matter what framework you use.
>>
>Why? If the data access class is written why do I need to learn how to write it?
>
>>
>>Techincally it is. Just like Microsoft is lik ANY other computer software company.. Hmmm... Yeah.. .NET Framework is commerical true, but that is like saying Yoda was just another plan Jedi.
>
>Kevin is Yoda.
>
>
>>he might make some great features that will be coming, but it is scary to have a small group of ppl.. (even if they are UTers) determine the direction of ASP.NET or .NET.
>
>If you want to write a lot of code waiting for MS to deliver two-data binding in ASP.NET but I don't. If you implement it in your own framework aren't you going in a direction all your own?
>
>>
>>That is a pretty bold statement saying where it is "suppose" to be and where it will be. It might be a nice framework, but after all.. It started in FoxPro, how good could it REALLY be? (Sorry.. needed to take a shot at VFP).
>
>I don't think Kevin would agree that it started in FoxPro. VFP and .Net are so different and he started from scratch with this framework. I'm sure he utilized his experience from building a framework in VFP but thats it.
>
>
>>Making money is the point, but I think in the long run, you will have less headaches, better skills as a developer, and more flexible and solid product, if you build your own framework. IMHO.
>
>Better skills as a developer?, perhaps. Every thing else I would have to disagree.
>
>As an inexperienced developer why would I rely on my skills to write the most important part of my application? A framework must be built before everything else. It will be the first thing I build as an inexperience developer. If it sucks my whole application is crap. I would much rather rely on the expertise of someone else.
>
>There are superstar developers out there, I'm not one of them.
>
>Also from a RAD perspective, when time is of the essence, building your own just isn't an option.