EDIT: I'm The Fool - It Is Not Broken - c# WinForms broken with latest VS2022 update 17.6.3 ?
-
Are you saying the IDE editor UI is not showing the controls correctly, or are you saying that your running app has issues? Remember, VS is an IDE, not the runtime - they are independent of each other.
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
-
In VS 2022 (and others) Help --> Send Feedback --> Report a Problem or just go here: Developer Community[^] I would search first if your issue has already been reported, if not, you really need to report it, especially if this was discovered after a recent update.
Cheers, I reported it, even just to see if I would get some pointers as to where the problem might be. ticket link.... [Developer Community](https://developercommunity.visualstudio.com/t/WinForms-controls-not-painting-on-Applic/10394580)
Dave Dave's Astrophotography Channel
Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject -
The running app after build and execution.
Dave Dave's Astrophotography Channel
Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProjectThen your issue has nothing to do with the VS version.
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
-
Then your issue has nothing to do with the VS version.
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
Could it not be compiling differently under the new version following a new build of the App, depending on what all they have changed/included with this release?
Dave Dave's Astrophotography Channel
Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject -
Could it not be compiling differently under the new version following a new build of the App, depending on what all they have changed/included with this release?
Dave Dave's Astrophotography Channel
Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProjectThe compiler is specific to the Framework version, not to the IDE.
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'm not seeing any such problems here: what controls, and what .NET version(s) are in play here? And do you see the effect in previously compiled apps, or just oned compiled after the update? I'm currently running 17.3.6, but a quick check says that 17.6.3 is ready to go ... :~
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Edit: I'm deleting this as it was ME who screwed up! Long story short, after updating VS I made some code changes and added a new usercontrol. and then had built the code and see the issue I had previously mentioned. I was convinced it must have been something I did, so walked back through the code changes I had made in the app, commenting out bit by bit until bingo the problem went away. What foolish mistake had I made? Well it all boiled down to a recursive paint / draw / refresh loop, that was basically blocking the parent panel from drawing, that appears to explain why it was the controls in that group that were impacted. Ah well, kept me busy for a few hours on a cloudy day...... :rolleyes:
Dave Dave's Astrophotography Channel
Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProjectTo err is human; to forgive is not our policy. :)
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
Edit: I'm deleting this as it was ME who screwed up! Long story short, after updating VS I made some code changes and added a new usercontrol. and then had built the code and see the issue I had previously mentioned. I was convinced it must have been something I did, so walked back through the code changes I had made in the app, commenting out bit by bit until bingo the problem went away. What foolish mistake had I made? Well it all boiled down to a recursive paint / draw / refresh loop, that was basically blocking the parent panel from drawing, that appears to explain why it was the controls in that group that were impacted. Ah well, kept me busy for a few hours on a cloudy day...... :rolleyes:
Dave Dave's Astrophotography Channel
Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject -
Edit: I'm deleting this as it was ME who screwed up! Long story short, after updating VS I made some code changes and added a new usercontrol. and then had built the code and see the issue I had previously mentioned. I was convinced it must have been something I did, so walked back through the code changes I had made in the app, commenting out bit by bit until bingo the problem went away. What foolish mistake had I made? Well it all boiled down to a recursive paint / draw / refresh loop, that was basically blocking the parent panel from drawing, that appears to explain why it was the controls in that group that were impacted. Ah well, kept me busy for a few hours on a cloudy day...... :rolleyes:
Dave Dave's Astrophotography Channel
Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProjectGood to hear that you figured it out.
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
-
Edit: I'm deleting this as it was ME who screwed up! Long story short, after updating VS I made some code changes and added a new usercontrol. and then had built the code and see the issue I had previously mentioned. I was convinced it must have been something I did, so walked back through the code changes I had made in the app, commenting out bit by bit until bingo the problem went away. What foolish mistake had I made? Well it all boiled down to a recursive paint / draw / refresh loop, that was basically blocking the parent panel from drawing, that appears to explain why it was the controls in that group that were impacted. Ah well, kept me busy for a few hours on a cloudy day...... :rolleyes:
Dave Dave's Astrophotography Channel
Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProjectIt happens. There have been times when I've made code changes to a wrong file (a copy of the file with the same name, at a backup location), recompiled the project, only to see that nothing has changed in the execution., then debugged for several hours; only to realize later that the file path is different. Must have happened to several members here.
