Re: Xamarin update warning

Agreed. This wasn't the highest quality release, lots of regressions on basic functionality [1]. Disappointing. [1] https://bugzilla.xamarin.com/show_bug.cgi?id=44402 On 19 September 2016 at 12:58, Greg Keogh wrote: > Folks, on Friday Xamarin Studio told there were updates

Re: Entity Framework - the lay of the land

Well there you go, signs they are continuing to invest... as now it's moved from an organic form into solid form ... i.e., it was a virus last time I saw it, now its an actual physical metal object (bullet). *drops mic* --- Regards, Scott Barnes http://www.riagenic.com On Tue, Sep 20, 2016 at

RE: Entity Framework - the lay of the land

When I posted on Facebook about it the other day, another Microsoft friend noted that he was going to be the product manager for EF, but commented that he managed “to dodge that bullet”. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax

RE: Entity Framework - the lay of the land

Hey Craig, I often get coy when I hear comparisons with Stack Overflow, Twitter, Facebook, Blog Engines, etc. though. Most of those platforms are happy to just throw away transactions when the going gets heavy. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410

Re: Xamarin update warning

I've had this happen to me a couple of times. Now I won't do an update until there is a lull in project work and I think I can survive the time it would take to get things working again. Which is annoying because each update brings the hope that some of the annoying bugs will be fixed. Including

Re: Entity Framework - the lay of the land

To give more info, 99% of the CUD was done via NHibernate. For simple select queries like for lookup lists was also done via NHibernate, using the built in caching and Redis cache, but more complicated queries were straight SQL and PetaPoco. Craig On Tue, Sep 20, 2016 at 1:30 PM, Craig van

Re: Entity Framework - the lay of the land

Not EF but have used NHibernate in application, in conjunction with optimised SQL where required, and easily supported 1000+ users. But it is very easy to stuff it up and find you can't support 5 simultaneous users. Even StackOverflow before it used Dapper used LinqToSql. Of course, they had to

RE: Entity Framework - the lay of the land

Thanks everyone for their contributions to my original questions. I am a little surprised about how poor people’s real world experience has been with the EF and other ORMs. A little poll; Is anyone successfully using EF in a production environment for a non-trivial application? And if yes,

RE: Entity Framework - the lay of the land

Agreed Ken. Actually I had another odd one about a year ago with a large bank (which bank?). If I did a transaction search with: From Date: start of the month To Date: end of the month a particular transaction on the last day of the month appeared. But if I selected: From Date: end of the

RE: Entity Framework - the lay of the land

A large bank (like one of the Big4 in Aus) has a staggering number of applications. Even running what you’d think is the simplest product results in multiple applications being involved, whether opening an account through to day-to-day transacting, especially given the multiple channels that