I work with dlls. LOTS of dlls. I've got a couple other threads on here about complaints I've had with VS2019, but now I've encountered one that is intolerable.
I was debugging something and stepped into a method that was in a dll directly referenced by the main project (most of my dlls are dynamically loaded). The code stepping was terribly incorrect. It was appearing to take paths that it clearly wasn't taking, such as stepping to return statements in the wrong branch of conditionals, then stepping on into the next condition as if the last one hadn't happened...which it clearly hadn't, since it shouldn't have been in there and the return statement didn't execute.
I felt this might be because I was referencing the release version rather than the debug version, so I switched over to referencing the debug version...and all objects defined in the dll became undefined. I tried rebuilding, but that did nothing. Then I noticed that the dll in the bin\debug folder was roughly a third the size of the dll in the bin\release folder, and some other things that were in the bin\release folder, such as resources, weren't in the bin\debug folder at all.
My next step was to delete the obj and bin folders and rebuild the whole thing. This time around, while VS said it was building in debug, the bin\debug folder ended up completely empty. The bin\release folder rebuilt correctly. Nothing I have done will get VS to build a debug build. It says it is, as it shows the building graphic, and says rebuilding down in the lower left status area, but nothing results from it.
So, I couldn't link to the debug build if I even wanted to, and stepping through the release build is too erratic to be meaningful.
At this point, I'm going to uninstall VS and reinstall. After all, there are other issues, but they show up on both computers that I have VS installed on. The most notable one is that the "Recent" list of dlls referenced remains stubbornly empty, so I always have to browse for any dll.
There are other issues, as well, and I'm not optimistic that the reinstall will fix them, especially since I have VS 2019 on three computers, and issues appear on at least two of them (I haven't looked for the issues on the third).
I guess I'm just not impressed with the stability of VS2019 and am just venting that frustration, but if anybody has any suggestions as to how to improve things, let me know.
I was debugging something and stepped into a method that was in a dll directly referenced by the main project (most of my dlls are dynamically loaded). The code stepping was terribly incorrect. It was appearing to take paths that it clearly wasn't taking, such as stepping to return statements in the wrong branch of conditionals, then stepping on into the next condition as if the last one hadn't happened...which it clearly hadn't, since it shouldn't have been in there and the return statement didn't execute.
I felt this might be because I was referencing the release version rather than the debug version, so I switched over to referencing the debug version...and all objects defined in the dll became undefined. I tried rebuilding, but that did nothing. Then I noticed that the dll in the bin\debug folder was roughly a third the size of the dll in the bin\release folder, and some other things that were in the bin\release folder, such as resources, weren't in the bin\debug folder at all.
My next step was to delete the obj and bin folders and rebuild the whole thing. This time around, while VS said it was building in debug, the bin\debug folder ended up completely empty. The bin\release folder rebuilt correctly. Nothing I have done will get VS to build a debug build. It says it is, as it shows the building graphic, and says rebuilding down in the lower left status area, but nothing results from it.
So, I couldn't link to the debug build if I even wanted to, and stepping through the release build is too erratic to be meaningful.
At this point, I'm going to uninstall VS and reinstall. After all, there are other issues, but they show up on both computers that I have VS installed on. The most notable one is that the "Recent" list of dlls referenced remains stubbornly empty, so I always have to browse for any dll.
There are other issues, as well, and I'm not optimistic that the reinstall will fix them, especially since I have VS 2019 on three computers, and issues appear on at least two of them (I haven't looked for the issues on the third).
I guess I'm just not impressed with the stability of VS2019 and am just venting that frustration, but if anybody has any suggestions as to how to improve things, let me know.