Another Visual Studio Update, Another Level of Ineptitude.
-
I can not believe how badly they have screwed the pooch on this. I've posted about this before and submitted bug reports and and they have done it yet again. With the 17.4.4 update (I think it was) Visual Studio's batch build option lost the ability to remember which of your build targets you want to build. They then fixed it a release or two later. With the 17.5.0 update it was broke again and fixed again at the next release. Yesterday they released 17.6.0 and this is broken again. :rolleyes: For me, this is a major pain in the backside. I have one solution with 24 projects, another with 40, and several more with 10. Now I have to waste a considerable amount of time selecting the desired build targets whenever I load one of those or I build them all and that wastes even more time. I am so infuriated right now that I think I will wait until tomorrow to update my bug report. It won't matter very much because this is an issue raised by quite a number of people. One guy remarked that he gave up on it and has resorted to batch files. I am dang nearly at that point myself. :sigh: Actually, what I should be doing is waiting until I see what new and annoying bugs there are with each new release before I do any updates. I certainly will in the future. ETA: 17.6.3 was released today and it is still broken. A corporate representative posted on 25 May that the issue is fixed and awaiting release. ETA: 17.7.0 was released today and it is FIXED! At long, long last. It was still broken in releases 17.6.4 and 17.6.5 so this is very welcome news. ETA: they have released versions 17.7.1, 17.7.2, and 17.7.3 and it wasn't broken on any of them. I have to state that I am very, very surprised but in a good way. ETA: While 17.7.3 did not break this option, it changed a whole bunch of my settings and it has been very annoying resetting them.
"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?"
-
I can not believe how badly they have screwed the pooch on this. I've posted about this before and submitted bug reports and and they have done it yet again. With the 17.4.4 update (I think it was) Visual Studio's batch build option lost the ability to remember which of your build targets you want to build. They then fixed it a release or two later. With the 17.5.0 update it was broke again and fixed again at the next release. Yesterday they released 17.6.0 and this is broken again. :rolleyes: For me, this is a major pain in the backside. I have one solution with 24 projects, another with 40, and several more with 10. Now I have to waste a considerable amount of time selecting the desired build targets whenever I load one of those or I build them all and that wastes even more time. I am so infuriated right now that I think I will wait until tomorrow to update my bug report. It won't matter very much because this is an issue raised by quite a number of people. One guy remarked that he gave up on it and has resorted to batch files. I am dang nearly at that point myself. :sigh: Actually, what I should be doing is waiting until I see what new and annoying bugs there are with each new release before I do any updates. I certainly will in the future. ETA: 17.6.3 was released today and it is still broken. A corporate representative posted on 25 May that the issue is fixed and awaiting release. ETA: 17.7.0 was released today and it is FIXED! At long, long last. It was still broken in releases 17.6.4 and 17.6.5 so this is very welcome news. ETA: they have released versions 17.7.1, 17.7.2, and 17.7.3 and it wasn't broken on any of them. I have to state that I am very, very surprised but in a good way. ETA: While 17.7.3 did not break this option, it changed a whole bunch of my settings and it has been very annoying resetting them.
"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?"
For me, the issue with editing JavaScript in CSHTML files[^] is the biggest pain introduced in 17.6.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I can not believe how badly they have screwed the pooch on this. I've posted about this before and submitted bug reports and and they have done it yet again. With the 17.4.4 update (I think it was) Visual Studio's batch build option lost the ability to remember which of your build targets you want to build. They then fixed it a release or two later. With the 17.5.0 update it was broke again and fixed again at the next release. Yesterday they released 17.6.0 and this is broken again. :rolleyes: For me, this is a major pain in the backside. I have one solution with 24 projects, another with 40, and several more with 10. Now I have to waste a considerable amount of time selecting the desired build targets whenever I load one of those or I build them all and that wastes even more time. I am so infuriated right now that I think I will wait until tomorrow to update my bug report. It won't matter very much because this is an issue raised by quite a number of people. One guy remarked that he gave up on it and has resorted to batch files. I am dang nearly at that point myself. :sigh: Actually, what I should be doing is waiting until I see what new and annoying bugs there are with each new release before I do any updates. I certainly will in the future. ETA: 17.6.3 was released today and it is still broken. A corporate representative posted on 25 May that the issue is fixed and awaiting release. ETA: 17.7.0 was released today and it is FIXED! At long, long last. It was still broken in releases 17.6.4 and 17.6.5 so this is very welcome news. ETA: they have released versions 17.7.1, 17.7.2, and 17.7.3 and it wasn't broken on any of them. I have to state that I am very, very surprised but in a good way. ETA: While 17.7.3 did not break this option, it changed a whole bunch of my settings and it has been very annoying resetting them.
"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?"
But hey, the icons are shiny! :-\
-
I can not believe how badly they have screwed the pooch on this. I've posted about this before and submitted bug reports and and they have done it yet again. With the 17.4.4 update (I think it was) Visual Studio's batch build option lost the ability to remember which of your build targets you want to build. They then fixed it a release or two later. With the 17.5.0 update it was broke again and fixed again at the next release. Yesterday they released 17.6.0 and this is broken again. :rolleyes: For me, this is a major pain in the backside. I have one solution with 24 projects, another with 40, and several more with 10. Now I have to waste a considerable amount of time selecting the desired build targets whenever I load one of those or I build them all and that wastes even more time. I am so infuriated right now that I think I will wait until tomorrow to update my bug report. It won't matter very much because this is an issue raised by quite a number of people. One guy remarked that he gave up on it and has resorted to batch files. I am dang nearly at that point myself. :sigh: Actually, what I should be doing is waiting until I see what new and annoying bugs there are with each new release before I do any updates. I certainly will in the future. ETA: 17.6.3 was released today and it is still broken. A corporate representative posted on 25 May that the issue is fixed and awaiting release. ETA: 17.7.0 was released today and it is FIXED! At long, long last. It was still broken in releases 17.6.4 and 17.6.5 so this is very welcome news. ETA: they have released versions 17.7.1, 17.7.2, and 17.7.3 and it wasn't broken on any of them. I have to state that I am very, very surprised but in a good way. ETA: While 17.7.3 did not break this option, it changed a whole bunch of my settings and it has been very annoying resetting them.
"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?"
-
But hey, the icons are shiny! :-\
the shine so overwhelming you cannot see the issues anymore
In Word you can only store 2 bytes. That is why I use Writer.
-
I can not believe how badly they have screwed the pooch on this. I've posted about this before and submitted bug reports and and they have done it yet again. With the 17.4.4 update (I think it was) Visual Studio's batch build option lost the ability to remember which of your build targets you want to build. They then fixed it a release or two later. With the 17.5.0 update it was broke again and fixed again at the next release. Yesterday they released 17.6.0 and this is broken again. :rolleyes: For me, this is a major pain in the backside. I have one solution with 24 projects, another with 40, and several more with 10. Now I have to waste a considerable amount of time selecting the desired build targets whenever I load one of those or I build them all and that wastes even more time. I am so infuriated right now that I think I will wait until tomorrow to update my bug report. It won't matter very much because this is an issue raised by quite a number of people. One guy remarked that he gave up on it and has resorted to batch files. I am dang nearly at that point myself. :sigh: Actually, what I should be doing is waiting until I see what new and annoying bugs there are with each new release before I do any updates. I certainly will in the future. ETA: 17.6.3 was released today and it is still broken. A corporate representative posted on 25 May that the issue is fixed and awaiting release. ETA: 17.7.0 was released today and it is FIXED! At long, long last. It was still broken in releases 17.6.4 and 17.6.5 so this is very welcome news. ETA: they have released versions 17.7.1, 17.7.2, and 17.7.3 and it wasn't broken on any of them. I have to state that I am very, very surprised but in a good way. ETA: While 17.7.3 did not break this option, it changed a whole bunch of my settings and it has been very annoying resetting them.
"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?"
-
I can not believe how badly they have screwed the pooch on this. I've posted about this before and submitted bug reports and and they have done it yet again. With the 17.4.4 update (I think it was) Visual Studio's batch build option lost the ability to remember which of your build targets you want to build. They then fixed it a release or two later. With the 17.5.0 update it was broke again and fixed again at the next release. Yesterday they released 17.6.0 and this is broken again. :rolleyes: For me, this is a major pain in the backside. I have one solution with 24 projects, another with 40, and several more with 10. Now I have to waste a considerable amount of time selecting the desired build targets whenever I load one of those or I build them all and that wastes even more time. I am so infuriated right now that I think I will wait until tomorrow to update my bug report. It won't matter very much because this is an issue raised by quite a number of people. One guy remarked that he gave up on it and has resorted to batch files. I am dang nearly at that point myself. :sigh: Actually, what I should be doing is waiting until I see what new and annoying bugs there are with each new release before I do any updates. I certainly will in the future. ETA: 17.6.3 was released today and it is still broken. A corporate representative posted on 25 May that the issue is fixed and awaiting release. ETA: 17.7.0 was released today and it is FIXED! At long, long last. It was still broken in releases 17.6.4 and 17.6.5 so this is very welcome news. ETA: they have released versions 17.7.1, 17.7.2, and 17.7.3 and it wasn't broken on any of them. I have to state that I am very, very surprised but in a good way. ETA: While 17.7.3 did not break this option, it changed a whole bunch of my settings and it has been very annoying resetting them.
"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?"
I think I ran into something similar a while back. 29 projects in the solution and it would forget which projects depended on which and build them out of order. I ended up setting the max number of concurrent project builds to 1 and it seems to have worked around the problem.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave Kreskowiak -
I think I ran into something similar a while back. 29 projects in the solution and it would forget which projects depended on which and build them out of order. I ended up setting the max number of concurrent project builds to 1 and it seems to have worked around the problem.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave KreskowiakI'm a bit slow on the uptake here but that's what I always do (one concurrent build at a time) and that made no difference for me.
"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?"
-
I can not believe how badly they have screwed the pooch on this. I've posted about this before and submitted bug reports and and they have done it yet again. With the 17.4.4 update (I think it was) Visual Studio's batch build option lost the ability to remember which of your build targets you want to build. They then fixed it a release or two later. With the 17.5.0 update it was broke again and fixed again at the next release. Yesterday they released 17.6.0 and this is broken again. :rolleyes: For me, this is a major pain in the backside. I have one solution with 24 projects, another with 40, and several more with 10. Now I have to waste a considerable amount of time selecting the desired build targets whenever I load one of those or I build them all and that wastes even more time. I am so infuriated right now that I think I will wait until tomorrow to update my bug report. It won't matter very much because this is an issue raised by quite a number of people. One guy remarked that he gave up on it and has resorted to batch files. I am dang nearly at that point myself. :sigh: Actually, what I should be doing is waiting until I see what new and annoying bugs there are with each new release before I do any updates. I certainly will in the future. ETA: 17.6.3 was released today and it is still broken. A corporate representative posted on 25 May that the issue is fixed and awaiting release. ETA: 17.7.0 was released today and it is FIXED! At long, long last. It was still broken in releases 17.6.4 and 17.6.5 so this is very welcome news. ETA: they have released versions 17.7.1, 17.7.2, and 17.7.3 and it wasn't broken on any of them. I have to state that I am very, very surprised but in a good way. ETA: While 17.7.3 did not break this option, it changed a whole bunch of my settings and it has been very annoying resetting them.
"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?"
I don't know about the update but the bugginess of VS2022 is infuriating. I'm programming a WinForms project and the Tools in the Tool window disappear on a regular basis or are grayed out. The properties window is blank at times. Sometimes designers refuse to load...on and on! WTF, is there no QA anymore? This is not a new product, it's been out as a preview for quite a while. So again I say WTF?
I don't think before I open my mouth, I like to be as surprised a everyone else. PartsBin an Electronics Part Organizer - Release Version 1.1.0 JaxCoder.com Latest Article: Simon Says, A Child's Game
-
I don't know about the update but the bugginess of VS2022 is infuriating. I'm programming a WinForms project and the Tools in the Tool window disappear on a regular basis or are grayed out. The properties window is blank at times. Sometimes designers refuse to load...on and on! WTF, is there no QA anymore? This is not a new product, it's been out as a preview for quite a while. So again I say WTF?
I don't think before I open my mouth, I like to be as surprised a everyone else. PartsBin an Electronics Part Organizer - Release Version 1.1.0 JaxCoder.com Latest Article: Simon Says, A Child's Game
I have a few close friends that work for Microsoft, and they are developers there. I am not saying this is the reason, but it may be a contributing factor: too many young people with subpar work ethic. I've preached about this in other threads over the years, but my friends brought this up to me before, a few times. I guess its becoming a big deal/issue there. It would explain or partially explain the increased lackluster rollouts and releases, the bugs that should have been caught during normal testing processes, etc. - the silly, stupid stuff that should never occur. Hey, go woke, go broke. You get what you pay for. If Microsoft wants to pay for shite, then they get shite. Just saying...
-
I have a few close friends that work for Microsoft, and they are developers there. I am not saying this is the reason, but it may be a contributing factor: too many young people with subpar work ethic. I've preached about this in other threads over the years, but my friends brought this up to me before, a few times. I guess its becoming a big deal/issue there. It would explain or partially explain the increased lackluster rollouts and releases, the bugs that should have been caught during normal testing processes, etc. - the silly, stupid stuff that should never occur. Hey, go woke, go broke. You get what you pay for. If Microsoft wants to pay for shite, then they get shite. Just saying...
Things that are a thing of the past; Customer Service Work Ethic Responsibility for ones actions Privacy Unity etc.. I could go on and on but the soap box is no longer available!
I don't think before I open my mouth, I like to be as surprised a everyone else. PartsBin an Electronics Part Organizer - Release Version 1.1.0 JaxCoder.com Latest Article: SimpleWizardUpdate
-
Things that are a thing of the past; Customer Service Work Ethic Responsibility for ones actions Privacy Unity etc.. I could go on and on but the soap box is no longer available!
I don't think before I open my mouth, I like to be as surprised a everyone else. PartsBin an Electronics Part Organizer - Release Version 1.1.0 JaxCoder.com Latest Article: SimpleWizardUpdate
Not just Microsoft, it's everywhere.
Graeme
"I fear not the man who has practiced ten thousand kicks one time, but I fear the man that has practiced one kick ten thousand times!" - Bruce Lee
-
I don't know about the update but the bugginess of VS2022 is infuriating. I'm programming a WinForms project and the Tools in the Tool window disappear on a regular basis or are grayed out. The properties window is blank at times. Sometimes designers refuse to load...on and on! WTF, is there no QA anymore? This is not a new product, it's been out as a preview for quite a while. So again I say WTF?
I don't think before I open my mouth, I like to be as surprised a everyone else. PartsBin an Electronics Part Organizer - Release Version 1.1.0 JaxCoder.com Latest Article: Simon Says, A Child's Game
Mike Hankey wrote:
WTF, is there no QA anymore?
Almost as bad, inept QA. Our esteemed QA department (what I call our one guy) closed a Jira that wasn't even yet in his queue. I had to call him out in Standup yesterday. I asked him how he tested the change, in all 5 different applications it went in, when I intentionally had NOT moved the code into the branch that builds the QA environment. "I just saw it was related to the one application as the other stories I was testing and moved it over." Later I went back and checked the story and sure enough in my description was what he SHOULD have seen if the code had been migrated over. Since it wasn't, the message wouldn't have appeared and he should have Failed the story. I now know he didn't even READ the story before passing it. This is not the first time he has done this.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
I can not believe how badly they have screwed the pooch on this. I've posted about this before and submitted bug reports and and they have done it yet again. With the 17.4.4 update (I think it was) Visual Studio's batch build option lost the ability to remember which of your build targets you want to build. They then fixed it a release or two later. With the 17.5.0 update it was broke again and fixed again at the next release. Yesterday they released 17.6.0 and this is broken again. :rolleyes: For me, this is a major pain in the backside. I have one solution with 24 projects, another with 40, and several more with 10. Now I have to waste a considerable amount of time selecting the desired build targets whenever I load one of those or I build them all and that wastes even more time. I am so infuriated right now that I think I will wait until tomorrow to update my bug report. It won't matter very much because this is an issue raised by quite a number of people. One guy remarked that he gave up on it and has resorted to batch files. I am dang nearly at that point myself. :sigh: Actually, what I should be doing is waiting until I see what new and annoying bugs there are with each new release before I do any updates. I certainly will in the future. ETA: 17.6.3 was released today and it is still broken. A corporate representative posted on 25 May that the issue is fixed and awaiting release. ETA: 17.7.0 was released today and it is FIXED! At long, long last. It was still broken in releases 17.6.4 and 17.6.5 so this is very welcome news. ETA: they have released versions 17.7.1, 17.7.2, and 17.7.3 and it wasn't broken on any of them. I have to state that I am very, very surprised but in a good way. ETA: While 17.7.3 did not break this option, it changed a whole bunch of my settings and it has been very annoying resetting them.
"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?"
I'm a bit late to this party.... I have learned to export my install config (VS Installer > More > Export Configuration) and export settings (VS IDE > Tools > Import and Export Settings). Especially important when working with the Preview editions. When it is time to do a major update, I tend to Repair, then apply the update. If there are any issues, I can uninstall and use the exported configuration to quickly reinstall, then Import the settings back into the IDE after updating. Flushing an install tends to have less issues after the update. Re-installing things like ReSharper and other extensions, not that I use many, doesn't take long to do.
Graeme
"I fear not the man who has practiced ten thousand kicks one time, but I fear the man that has practiced one kick ten thousand times!" - Bruce Lee
