Actually, it does have a killer feature for us: native spatial processing. That will cut our processing times by a huge amount.

Yup. That's what they say. That they want to verify everything. These are the same people that write stored procs with spaces in the column names, # signs, etc. We once spent a day tracking down a crash because the SQL dev "accidently" put a trailing space in the column name "ColumnName ". He swore up and down that he didn't change any column names and dev swore up and down that he did. Like I said before, I'm not a SQL expert and database doesn't interest me that much in general, so I'm not up on all the latest & greatest best practices, but I still know you shouldn't put spaces in column names, keep everything consistent, etc. Not have 11 copies of the same data copied all over the place, etc.

I've learned not to waste my time chasing after people here. If somebody important comes asking me for status, I just say "so & so is road blocking the project" and let them worry about it. Sometimes they ask me to follow up with the road blocker to which I usually respond "I've already sent them 4 or 5 emails on it with no response, I can send a 6th email if you want..." sometimes they want me to and sometimes they don't.

Yup. My favorite dev story is that at one company I worked at, there was a change control board. You weren't allowed to touch code without their approval, so basically: *user or QA reports bug *bug goes to CCB *CCB reviews bug and decides if its worth doing anything about it *assuming CCB approved bug, it gets sent to dev group router *router routes it to proper mgr *assuming router got it right (1/2 the time they didn't) the mgr distributed it to developer for RESEARCH ONLY *there was no ownership of code, so a bug might get routed to a person who has never touched, looked at or even heard of that component *developer would research it, it usually took quite a while to research it, because you had to track down the original developer and ask them all sorts of questions to get up to speed *developer would report back the finding to the CCB *CCB would either approve, deny or request more info *if they want more info, rinse/repeat *only after approval could you fix it -- problem was, you general got approval MONTHS after you researched it, so you completely forgot everything about it -- no point in shelving the changes or anything, since they literally had thousands of branches, and you'd never be able to find your branch. So anyways, due to all the red tape, it actually took me 6 months just to change a bool from true to false :).

We have 2 SQL devs that write the SPs. One of them is fairly OK, but tbh, I think his skills are antiquated and he has no interest in learning new stuff. He only knows Microsoft SQL and tends to develop SPs using tons of temp tables and tends to "work around" issues rather then fix them. The other dev is awful. Us devs suspect he is a former C/C++ developer who picked up a "SQL for dummies" book one weekend and decided to become a SQL developer. Just due to the way he writes SQL code. The first project they gave him, he released an SP that took 30 minutes to run!!! He actually released it like that. They've restructured everything many times over and have got it down to 5 to 10 seconds now which still doesn't meet the requirements LOL. 30 minutes to 5 to 10 seconds is a huge improvement obviously, but it just shows how bad the SQL is at my company.

We are a B2B data provider, so the database is behind a firewall and the web services access it. We devs aren't allowed to touch the databases anymore. The DB team lead locked them all down. I agree on that, you shouldn't have people randomly do stuff to production databases. Due to the slowness of the database and ETL groups, most of us devs just sit around all day. Nothing to do while we wait on those groups. What's sad is that even with all this time we give them, the databases still suck. They go down all the time, have lots of timeouts, etc.

The last time our DBA group quoted us 3 months, it took them 9 months. I'm still "waiting" for them to complete tasks from like 3 yrs ago LOL. The team lead is horrible. So easily distracted. You basically ask him "how's it going" as a courtesy before jumping into work and you have to listen to his stories for like 30 minutes at least. Then somebody comes up to his desk and interrupts and he is distracted again for another 30 minutes. Rinse, repeat.

Dumb question... if you are a DBA and I came up to you and said "Here's a physical beastly box... 24 cores, ~140GB of RAM, plenty of flash storage... I need you to set up SQL 2016 on it and migrate this 10TB database from SQL 2008 R2" Assuming of course proper security and best practices, etc. Let's even "complicate" it and assume this 10TB database includes spatial data. How long would it take you? I have ZERO SQL admin experience other then slamming a few SQLs onto local machines or VMs and I think I could realistically get it setup and running in a day or two with plenty of breathing room. Yet, our supposedly experienced DBAs claim its going to take them 3 months!!! LOL... Unbelievable.

I'm just using it on my personal side project, so I probably use it maybe 3 hrs a week tops. If I had to use it 8 hrs a day for my work (especially if it was 99% WPF), I'd be hatin'... From one WPF guy to another, I would not use this in a professional environment right now. Too buggy still. I do like the runtime "Spy++" type tool that can hyperlink to the element in the XAML... kind of cool, but also kind of kludge to use with the weird focus behavior. Switching properties at runtime? I guess if you're debugging something that's hard to repro... I would call VS2013 "rock solid"... if that is the basis for a "10", I'd give this a 2 or 3 in the **WPF areas**.

I do C# and WPF work. I don't know what they did to the XAML parser in VS2015, but it flat out stinks. It blue squiggles pretty much everything intermittently, gives random / incorrect errors intermittently, etc. There are a few other nitpicks in the general environment, but this is pretty much unusable. Very disappointed. Any other WPF people seeing the same thing?

Try run that... Windows doesn't let you create a window that wide. Height wise, you can create as big as you want... I really just need to add 18 measly pixels of width to my Window for rendering purposes and it won't let me... Any way around this?

I did discover that setting ResizeMode=None blocks the Aero-snap commands just for the specific window, but there still wasn't any way to catch the Win+Left that I could find. The regular keyboard hook would only catch it on the release. I tried catching WM_GETMINMAXINFO, but the samples I saw used Marshal.PtrToStructure, so I guess that makes a copy of the struct and you can't modify the original data? Regardless, I also tried catching the various sizing messages, and yeah, I guess I was able to kind of trap Height = 100% / Width = 50%, but there was no way to tell if that was from the user mouse or from Aero-snap and that would kind of be the same situation if I got the WM_GETMINMAXINFO message working. So, I guess the only solution is to use the low level keyboard hook -- with a twist :). I only need it to catch Win+Left, Win+Right and Win+Up... so I can catch the Win down in my app and then I install the system wide hook so I can catch the 3 Win+XXX combinations and when the Win button is released, or my app loses focus I remove it. Rinse. Repeat. Still don't like installing a system wide hook, but I'm only keeping it installed when they press the Win key, so I guess its not too bad. Better then leaving it installed the whole time my app is up.

I'm writing a WPF app with a custom window frame (not a specific WPF question though). Due to the necessary "macgyverising" of the window and window frame to get things to work correctly (i.e. hidden transparent window borders, etc.), it kind of messed up the aero-snapping a little bit. I want to catch the Win+Left, etc. hot keys so I can "fix" my window. All the usual suspects don't work for this. Keydown, PreviewKeydown, custom window proc, etc. Only thing I've found that works for this (so far) is a low level keyboard hook. I'm not thrilled about the low level keyboard hook, as its a global hook and if my EXE is running, the system will call my app for ALL keys in ALL apps. That's not really an acceptable solution in my book. Any other options?

The generally accepted solution is to use something like EventToCommand.

I'm trying to sign my assembly. When I run my GUI, I get the infamous: "The located assembly's manifest definition does not match the assembly reference" exception. A Google search listed about "8 trillion" possible causes for this exception. In my case, it was using a wildcard version number in the AssemblyInfo.cs: [assembly: AssemblyVersion("3.00.*")] // doesn't work [assembly: AssemblyVersion("3.00.0000")] // can change versions all day long So it seems like wildcard versions don't work with signing?? How come? Is the wildcarding applied AFTER signing? Any work-around?

Hmm... that seems to be the concept of the left toolbar. Interesting... Thanks.

Well, its not really a programming question. Yeah, I got a lot of smart ass useless responses.. but if I posted in the C# forum, I'd get an equal number of forum nazis telling me its not a C# question LOL. *Sigh*... I really have to switch over to SO one of these days LOL. That place seems a lot more useful and helpful.

Hmm... that seems like its conceptual theory more then the left bar is called a fly bar or whatever and the top buttons are for x and the bottom buttons are for y. That's really what I'm looking for.

Not sure if this is the right place to ask this... I have been googleing terms all day and can't find a good write up on this topic. http://www.neowin.net/news/windows-10-build-10051-a-closer-look-at-the-new-mail-app[^] Based on those screen shots: 1) what is that UI style officially called? Modern? 2) I know people call it the hamburger, but does that button have an official name? 3) what is the left bar officially called? 4) on the left bar, whats the significance of the upper group of icons vs the lower group of icons? If somebody has a good link to a good write up about the design and the significance of everything, that would be awesome!

Actually, from watching Air Crash Investigation :), lots of things can cause the auto pilot to turn itself off: certain input to the controls, faulty sensors, etc. Basically, when the auto-pilot doesn't know what to do, or is confused by the information it gets, it turns off automatically.