The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Unfortunately it looks like what a prototype of the iMac may have looked like 2 years before the iMac release. Just before Steve wandered into the room, looked at the grey box under the screen, and yelled "what the F*** is that thing?".
Love the specs and the fact that it's Microsoft's own, but frankly I would have preferred them to simply make it a nice big touchscreen monitor I can use for my laptop if that meant they could slim it down.
One huge thing I love about my 27" iMac is I can pick it up with one hand and move it around. It's crazy solid. The double folding legs of the Studio don't fill me with confidence. I could be wrong, though.
Oh well - we'll see what Apple has up it's well designed sleeves today.
It seems that this is a progression of the "Surface" table that Microsoft demoed many years ago and is aimed at artists and the like who would work directly on the monitor, rather than have a wacom device or the like.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
Anything that is unrelated to elephants is irrelephant Anonymous - The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 - I'd just like a chance to prove that money can't make me happy. Me, all the time
I have a task that is maybe three calls deep from the MVVM Login command to the Web API call for a token. The API had an erroneous connection string, to an older version of the database*, and the UserManager.CreateUser method was failing in the Register action. It took about fifteen minutes, and a hard break-point, e.g. Debug.Fail(), to find the error.
The stack trace was most confounding, and it mentioned the Account controller and the error once that I could see in an 86 line long stack track, most of which were exceptions on a MoveNext() method on a slew of async tasks.
It is clear that I have some learning to do regarding configuring the innermost task, the long running one that is to be awaited, and that learning will begin tomorrow morning at 04h30, my normal starting time. Time to consult the venerable Mr. Skeet's seminal tome on C# 5.
* It's damned annoying how EF drops a default connection string, like a turd, into your config file, that points to the new fangled LocalDb. Then you forget to set one up, your first migration creates the DB there, then when you can't connect to where you expect it, you fix the connection string, and re-run the migration in the right database. Then, when you have done a few more migrations, and add e.g. a test project, it is once again pointing to the out-of-date LocalDb version.
Well, if you would use a flat file and single thread the thing, then you wouldn't have these problems!
#SupportHeForShe Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
Last Visit: 31-Dec-99 19:00 Last Update: 25-Mar-17 15:56