|
Kevin McFarlane wrote: they have customers who won't use non-MS originated technology
Ah I see. This is a perfectly valid business strategy that makes sense.
But someone should tell these customers that MS is not the holy grail of software development but just a company who does not care too much about their customers if it pays for them otherwise...
Regards
Thomas
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Programmer - an organism that turns coffee into software.
|
|
|
|
|
I had a go at it when 3.5 SP1 came out. It has nice features but it is not ready for production work. For example it has bugs when you try to change an existing design you have made and just refuses to change it, so many times I had to delete the whole design and start again. This was OK in the small project I've tried it but completely unacceptable for a bigger project. I will wait before using it in a bigger/production level project, probably when its next version comes out I will try again.
|
|
|
|
|
I have to concur. I have been looking for a ORM suitable for winforms. I took a look at EF and decided that it complete enough for use. There are also many more mature ORM frameworks available, nHibernate being one of the more popular ones. The link below lists some of the limitations of EF:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2623082&SiteID=1
MS is continuing to develop the framework but do you really want to risk embracing a framework that could be abandoned in a couple of year for the next new thing?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
