>>I echo what Charles has said exactly. Not to mention, the frameworks will support both EF and vanilla ADO and you can use linq or not. This gives the team an opportunity to learn new technology without needing to get deep into the grits of functionality the framework will do for you.
>>Tim
>
>Yes, I have a license for the latest MM and I like it a lot. Problem will be convincing a tight fisted management to spend the money for the other developers.
>
>I know I'm whining, but I feel that I'm just the little guy trying to sell this thing and nobody wants to listen. We have a huge task of moving some 250 VFP applications to C# ASAP and I'm the only one who knows C# and I think it's going to be a mountain of work.


Maybe a bit of effort investment in estimating how much it will cost to build (roll) your own framework and compare that to the cost of purchasing the mm licenses. Then also compare to the maintenance of that purchase as well as new technology or changes come out. I also think the purchased framework hides so much complexity that your programmers will have to deal with otherwise. There job of learning and developing will be much easier if they are not trying to develop/ learn/ maintain/ and figure out a custom framework. These are not the hard costs up front, but certainly are cost investments the management will have to pay for. I feel your pain in this as I have been in those situations also.
Tim