What about C9 staking out some independence from corporate and being an advocate for developers? I am actually getting down on MSFT lately. It takes way too much time to deal with things that just don't work.
Some parts of Access 2010 are really hard to learn. The forms designer is brutal. There is a minimum of intellisense in the embedded/prompted macro language that Access uses as an alternative to VBA. All of Office 2010 is still so 1980s with it reliance
on VBA. C9 tells me Sharepoint is great, great, great. Then I find out I have to upgrade my server to 8GB of RAM and a sharepoint license costs a huge amount of money. ( min $5K ). Come on, C9, be an advocate for managed code in Office!
WCF can be very hard to troubleshoot. The VS wizards create all this code for you, which is great. But when problems occur, like size limits imposed by IIS, and it can take a lot of concentration and slogging thru the wizard created code to get the solution.
The SQL server I installed as part of my MSDN subscription last year decided to shut itself down. Trial period ended. Go to MSDN forums, 20 minutes of solid work searching for an answer, then composing a question. Wait a few hours, told to do an edition
upgrade. Download and install the upgrade. Install fails, some sort of authority error. But I am running as admin on the server. Research, post question on the forum, find out about this and that, run as admin using a command line script, still fails. Post
more questions, wait, wait, wait, my test data is locked up in the expired sql server, days are going by. I am learning about how to recover by databases from the DATA folder, the many ways to install sql server, the different security accounts and where the
error logs are. All great to know, but so time consuming and what does this have to do with writing software applications? After a few days of this, I still don't have the problem solved. I place an MSDN support incident call. The support techs can't work
out the problem. More than a few hour long sessions with the tech taking remote control of my system. Capturing huge process explorer trace logs. I can understand there being a bug in sql server. But how can server 2008 R2 and sql server not have facilities
built in that allow better troubleshooting?
One last mini rant. How can it be that a.) a visual studio add-in is still really hard to write ( just look at the code the wizard creates when you create an addin project ) and b.) you still can't enumerate all the commands and command bars of the VS2010 IDE?
http://social.msdn.microsoft.com/Forums/en-US/vsx/thread/90cd3c1b-0057-45ed-a072-bc32703872c8 Not very important of course. But didn't C9 just spend the last 6 months broadcasting video after video about the totally rewritten visual studio 2010? Sure,
DSLs are great ( based on what C9 tells me ), but why is it still so much work to add code generating components to VS2010? And where is the access that an addin developer needs to the CodeDOM for use in generating code? I don't think VS2010 introduced any
more features on this front. VS is great at compiling your project on the fly. But the addin developer can't get at what is likely a wealth of data about the code of a project.