MS Marketing for MSBuild and this year's Dilbert Award...
-
A while back Microsoft took a poll on MSBuild users to see what they would most like added in the next build 4.0/VS2010. Overwhelmingly (and even more overwhelming is that they were shocked and did not expect the #1 choice because they are experts at it and therefore everyone else must also be) debugging (or the ability to actually get a project working and keep one's job) was #1. Who'd of "thunk it" right? But ironically, it did not make it in the product despite the fact 7 other lesser desired features did. So, a n MS Development lead, Dan Moseley, seeing his marketing department's demonstration in the practice of "Full Metal Jacket Moronics" decided to step in and develop one on his vacation. He did a pretty decent job http://blogs.msdn.com/b/visualstudio/archive/2010/07/06/debugging-msbuild-script-with-visual-studio.aspx[^]. I remind you, he was on vacation! But, it did not make it into the release formally so it is somewhat incomplete, but mercifully, Dan did leave it in the product, you have to use a backdoor trick to get into debugging. Far better than nothing, I can tell you that. Kudos, Dan! You are our hero! Now, back to the geniuses that progress into Marketing where the customer's interests are "all" they care about. They added 7 of the 15 top requested features (though #1 was not one of them). What is peculiar is that if Dan could get it working this well, on his own initiative, and it being the #1 care-about, then why was it not the #1 feature to have appeared in new VS2010 since it was low hanging fruit so to speak? [WARNING! Marketing pseudo logic commentary and staunch sarcasm follows this warning!!] Did the customer-careabouts-are-most-important focus change and they instead they insisted on hiring icon consultants to get new colors for Visual Studio icon or something far less meaningful and that override the time and money to get the customers what they need? Who in MS Marketing said "We can't do it this release, the customers don't want it as much and that's why the voted it #1 because they want these lesser interesting features first, and besides, its too doable! Take it off the 2010 feature list! I am in Marketing and I know what I am doing! Have you not seen the new VS icon! I, that's right I pro
-
A while back Microsoft took a poll on MSBuild users to see what they would most like added in the next build 4.0/VS2010. Overwhelmingly (and even more overwhelming is that they were shocked and did not expect the #1 choice because they are experts at it and therefore everyone else must also be) debugging (or the ability to actually get a project working and keep one's job) was #1. Who'd of "thunk it" right? But ironically, it did not make it in the product despite the fact 7 other lesser desired features did. So, a n MS Development lead, Dan Moseley, seeing his marketing department's demonstration in the practice of "Full Metal Jacket Moronics" decided to step in and develop one on his vacation. He did a pretty decent job http://blogs.msdn.com/b/visualstudio/archive/2010/07/06/debugging-msbuild-script-with-visual-studio.aspx[^]. I remind you, he was on vacation! But, it did not make it into the release formally so it is somewhat incomplete, but mercifully, Dan did leave it in the product, you have to use a backdoor trick to get into debugging. Far better than nothing, I can tell you that. Kudos, Dan! You are our hero! Now, back to the geniuses that progress into Marketing where the customer's interests are "all" they care about. They added 7 of the 15 top requested features (though #1 was not one of them). What is peculiar is that if Dan could get it working this well, on his own initiative, and it being the #1 care-about, then why was it not the #1 feature to have appeared in new VS2010 since it was low hanging fruit so to speak? [WARNING! Marketing pseudo logic commentary and staunch sarcasm follows this warning!!] Did the customer-careabouts-are-most-important focus change and they instead they insisted on hiring icon consultants to get new colors for Visual Studio icon or something far less meaningful and that override the time and money to get the customers what they need? Who in MS Marketing said "We can't do it this release, the customers don't want it as much and that's why the voted it #1 because they want these lesser interesting features first, and besides, its too doable! Take it off the 2010 feature list! I am in Marketing and I know what I am doing! Have you not seen the new VS icon! I, that's right I pro
And then I moved to NANT with NANT builder as my debugger. Building and debugging just in time to get home to the little ones :)
Alberto Bar-Noy --------------- “The city’s central computer told you? R2D2, you know better than to trust a strange computer!” (C3PO)
-
A while back Microsoft took a poll on MSBuild users to see what they would most like added in the next build 4.0/VS2010. Overwhelmingly (and even more overwhelming is that they were shocked and did not expect the #1 choice because they are experts at it and therefore everyone else must also be) debugging (or the ability to actually get a project working and keep one's job) was #1. Who'd of "thunk it" right? But ironically, it did not make it in the product despite the fact 7 other lesser desired features did. So, a n MS Development lead, Dan Moseley, seeing his marketing department's demonstration in the practice of "Full Metal Jacket Moronics" decided to step in and develop one on his vacation. He did a pretty decent job http://blogs.msdn.com/b/visualstudio/archive/2010/07/06/debugging-msbuild-script-with-visual-studio.aspx[^]. I remind you, he was on vacation! But, it did not make it into the release formally so it is somewhat incomplete, but mercifully, Dan did leave it in the product, you have to use a backdoor trick to get into debugging. Far better than nothing, I can tell you that. Kudos, Dan! You are our hero! Now, back to the geniuses that progress into Marketing where the customer's interests are "all" they care about. They added 7 of the 15 top requested features (though #1 was not one of them). What is peculiar is that if Dan could get it working this well, on his own initiative, and it being the #1 care-about, then why was it not the #1 feature to have appeared in new VS2010 since it was low hanging fruit so to speak? [WARNING! Marketing pseudo logic commentary and staunch sarcasm follows this warning!!] Did the customer-careabouts-are-most-important focus change and they instead they insisted on hiring icon consultants to get new colors for Visual Studio icon or something far less meaningful and that override the time and money to get the customers what they need? Who in MS Marketing said "We can't do it this release, the customers don't want it as much and that's why the voted it #1 because they want these lesser interesting features first, and besides, its too doable! Take it off the 2010 feature list! I am in Marketing and I know what I am doing! Have you not seen the new VS icon! I, that's right I pro
rittjc wrote:
If these "geniuses" are not interested in our answers then why did they take a poll
See thats where you made the mistake, you think the poll has a purpose, a poll has a value unto itself, it can be analysed, studied, generates innumerable meetings, now that is what polls are for. Pffft the idea that the poll would be acted on, ridiculous.
Never underestimate the power of human stupidity RAH
-
A while back Microsoft took a poll on MSBuild users to see what they would most like added in the next build 4.0/VS2010. Overwhelmingly (and even more overwhelming is that they were shocked and did not expect the #1 choice because they are experts at it and therefore everyone else must also be) debugging (or the ability to actually get a project working and keep one's job) was #1. Who'd of "thunk it" right? But ironically, it did not make it in the product despite the fact 7 other lesser desired features did. So, a n MS Development lead, Dan Moseley, seeing his marketing department's demonstration in the practice of "Full Metal Jacket Moronics" decided to step in and develop one on his vacation. He did a pretty decent job http://blogs.msdn.com/b/visualstudio/archive/2010/07/06/debugging-msbuild-script-with-visual-studio.aspx[^]. I remind you, he was on vacation! But, it did not make it into the release formally so it is somewhat incomplete, but mercifully, Dan did leave it in the product, you have to use a backdoor trick to get into debugging. Far better than nothing, I can tell you that. Kudos, Dan! You are our hero! Now, back to the geniuses that progress into Marketing where the customer's interests are "all" they care about. They added 7 of the 15 top requested features (though #1 was not one of them). What is peculiar is that if Dan could get it working this well, on his own initiative, and it being the #1 care-about, then why was it not the #1 feature to have appeared in new VS2010 since it was low hanging fruit so to speak? [WARNING! Marketing pseudo logic commentary and staunch sarcasm follows this warning!!] Did the customer-careabouts-are-most-important focus change and they instead they insisted on hiring icon consultants to get new colors for Visual Studio icon or something far less meaningful and that override the time and money to get the customers what they need? Who in MS Marketing said "We can't do it this release, the customers don't want it as much and that's why the voted it #1 because they want these lesser interesting features first, and besides, its too doable! Take it off the 2010 feature list! I am in Marketing and I know what I am doing! Have you not seen the new VS icon! I, that's right I pro
How are they going to sell the next version if they get this one right?
This sig, like my mind intentionally left blank.
-
A while back Microsoft took a poll on MSBuild users to see what they would most like added in the next build 4.0/VS2010. Overwhelmingly (and even more overwhelming is that they were shocked and did not expect the #1 choice because they are experts at it and therefore everyone else must also be) debugging (or the ability to actually get a project working and keep one's job) was #1. Who'd of "thunk it" right? But ironically, it did not make it in the product despite the fact 7 other lesser desired features did. So, a n MS Development lead, Dan Moseley, seeing his marketing department's demonstration in the practice of "Full Metal Jacket Moronics" decided to step in and develop one on his vacation. He did a pretty decent job http://blogs.msdn.com/b/visualstudio/archive/2010/07/06/debugging-msbuild-script-with-visual-studio.aspx[^]. I remind you, he was on vacation! But, it did not make it into the release formally so it is somewhat incomplete, but mercifully, Dan did leave it in the product, you have to use a backdoor trick to get into debugging. Far better than nothing, I can tell you that. Kudos, Dan! You are our hero! Now, back to the geniuses that progress into Marketing where the customer's interests are "all" they care about. They added 7 of the 15 top requested features (though #1 was not one of them). What is peculiar is that if Dan could get it working this well, on his own initiative, and it being the #1 care-about, then why was it not the #1 feature to have appeared in new VS2010 since it was low hanging fruit so to speak? [WARNING! Marketing pseudo logic commentary and staunch sarcasm follows this warning!!] Did the customer-careabouts-are-most-important focus change and they instead they insisted on hiring icon consultants to get new colors for Visual Studio icon or something far less meaningful and that override the time and money to get the customers what they need? Who in MS Marketing said "We can't do it this release, the customers don't want it as much and that's why the voted it #1 because they want these lesser interesting features first, and besides, its too doable! Take it off the 2010 feature list! I am in Marketing and I know what I am doing! Have you not seen the new VS icon! I, that's right I pro
rittjc wrote:
I mean the release of VS2010 was almost 3 years after the release of VS2008.
I believe they did get in some fairly hefty service packs in between. I'd argue that's the right approach, as otherwise many customers (non-MSDN-subscribers) would need to buy a new copy each bl**dy time. Saying that, I'm no big fan of MSBuild generally - seems to me that the evolvution of build tools has been too influenced by the verbosity of XML. Too many of the rules for tools etc. are hidden in include files (to give them a more honest name) and the documentation is not great (often referring to some MS Press book)
