Another Bug Report, Another Denial
-
The latest one : Batch Build Clean Error With Only Some Configurations Selected - Developer Community[^] To shorten the story, when I use batch build and select only some of the options to be cleaned, VS19 cleans them all. In their minds that is not a bug. In mine it most definitely IS a big. I included a screenshot of the options and results in one of my comments. Their "solution" is just a plain denial of facts and is ridiculous. I have done a fair number of experiments and all demonstrate there is a bug in this scenario. I have several solutions containing multiple projects and this is the only that causes VS19 (and VS17) to behave incorrectly. Somehow, they don't think this is really a bug. Things that make you go, hmm... Followed shortly thereafter by a stream of expletives.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
The latest one : Batch Build Clean Error With Only Some Configurations Selected - Developer Community[^] To shorten the story, when I use batch build and select only some of the options to be cleaned, VS19 cleans them all. In their minds that is not a bug. In mine it most definitely IS a big. I included a screenshot of the options and results in one of my comments. Their "solution" is just a plain denial of facts and is ridiculous. I have done a fair number of experiments and all demonstrate there is a bug in this scenario. I have several solutions containing multiple projects and this is the only that causes VS19 (and VS17) to behave incorrectly. Somehow, they don't think this is really a bug. Things that make you go, hmm... Followed shortly thereafter by a stream of expletives.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
And the parrot is not dead, no it is just resting :-\
-
And the parrot is not dead, no it is just resting :-\
And pinin' for the fjords.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
-
The latest one : Batch Build Clean Error With Only Some Configurations Selected - Developer Community[^] To shorten the story, when I use batch build and select only some of the options to be cleaned, VS19 cleans them all. In their minds that is not a bug. In mine it most definitely IS a big. I included a screenshot of the options and results in one of my comments. Their "solution" is just a plain denial of facts and is ridiculous. I have done a fair number of experiments and all demonstrate there is a bug in this scenario. I have several solutions containing multiple projects and this is the only that causes VS19 (and VS17) to behave incorrectly. Somehow, they don't think this is really a bug. Things that make you go, hmm... Followed shortly thereafter by a stream of expletives.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
The latest one : Batch Build Clean Error With Only Some Configurations Selected - Developer Community[^] To shorten the story, when I use batch build and select only some of the options to be cleaned, VS19 cleans them all. In their minds that is not a bug. In mine it most definitely IS a big. I included a screenshot of the options and results in one of my comments. Their "solution" is just a plain denial of facts and is ridiculous. I have done a fair number of experiments and all demonstrate there is a bug in this scenario. I have several solutions containing multiple projects and this is the only that causes VS19 (and VS17) to behave incorrectly. Somehow, they don't think this is really a bug. Things that make you go, hmm... Followed shortly thereafter by a stream of expletives.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
Typical Microsoft response to a bug report: your perception of the product behavior is at fault.
Software Zen:
delete this; -
That's either a bug or awful UI design. The UI screams that it should only be applying those operations to what's selected in the box.
That's exactly my opinion too. Their "work-around" is ridiculous. They said I should disable those options in the solution configuration. If that's the case then why even have options in the Batch Build dialog? To make it worse, I did several experiments with different configurations, solutions, and options and found that this is the only case that actually fails. I can select those same projects and click build and only they are built.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
Typical Microsoft response to a bug report: your perception of the product behavior is at fault.
Software Zen:
delete this; -
The latest one : Batch Build Clean Error With Only Some Configurations Selected - Developer Community[^] To shorten the story, when I use batch build and select only some of the options to be cleaned, VS19 cleans them all. In their minds that is not a bug. In mine it most definitely IS a big. I included a screenshot of the options and results in one of my comments. Their "solution" is just a plain denial of facts and is ridiculous. I have done a fair number of experiments and all demonstrate there is a bug in this scenario. I have several solutions containing multiple projects and this is the only that causes VS19 (and VS17) to behave incorrectly. Somehow, they don't think this is really a bug. Things that make you go, hmm... Followed shortly thereafter by a stream of expletives.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
"This behavior is by design."
-
Typical Microsoft response to a bug report: your perception of the product behavior is at fault.
Software Zen:
delete this;Sometimes, that is what we have to do in our software. Someone sends a bug report that a feature is not working and their perception of the product's behavior is not what we intended. But will consider it for a change request in a future version.
-
Sometimes, that is what we have to do in our software. Someone sends a bug report that a feature is not working and their perception of the product's behavior is not what we intended. But will consider it for a change request in a future version.
Since I do the user interfaces for our stuff, I go through that as well. After I finally learned to read and interpret bug reports, I figured out some of them weren't bugs. The interaction I designed didn't make sense to the user. As a result, I've gotten better making things work for my target audience and get fewer of those sorts of reports.
Software Zen:
delete this; -
The latest one : Batch Build Clean Error With Only Some Configurations Selected - Developer Community[^] To shorten the story, when I use batch build and select only some of the options to be cleaned, VS19 cleans them all. In their minds that is not a bug. In mine it most definitely IS a big. I included a screenshot of the options and results in one of my comments. Their "solution" is just a plain denial of facts and is ridiculous. I have done a fair number of experiments and all demonstrate there is a bug in this scenario. I have several solutions containing multiple projects and this is the only that causes VS19 (and VS17) to behave incorrectly. Somehow, they don't think this is really a bug. Things that make you go, hmm... Followed shortly thereafter by a stream of expletives.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
..A big amen to you brother.. ..please let me know when you make it big.. 🤩🤩🤩🤩