Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. EDIT: I'm The Fool - It Is Not Broken - c# WinForms broken with latest VS2022 update 17.6.3 ?

EDIT: I'm The Fool - It Is Not Broken - c# WinForms broken with latest VS2022 update 17.6.3 ?

Scheduled Pinned Locked Moved The Lounge
csharphelpvisual-studiowinformscom
15 Posts 7 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D DaveAuld

    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

    OriginalGriffO Offline
    OriginalGriffO Offline
    OriginalGriff
    wrote on last edited by
    #3

    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!

    "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

    D 2 Replies Last reply
    0
    • OriginalGriffO OriginalGriff

      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!

      D Offline
      D Offline
      DaveAuld
      wrote on last edited by
      #4

      It is basic Labels and Buttons that don't show correctly on App Startup, thing is, it is not all of them, only some of them! Plus the listbox not rerendering to include new received serial message (except if i resize the form forcing a controls overlap redraw, I haven't finalised the layout yet, so not locked the form size yet, allowing me to force this overlap condition). It was with .Net 6, but as a test, I also switch the build to target .Net 7 and then re-built and copied the .Net 7 version across to the target machine, installed .Net 7 when prompted then ran the app and it does the same thing. This is a new utility App I'm writing for the observatory Dome system, the previous App I wrote for the SkyQualityMeter is still working fine, although I think it was built to target .Net 4.8, can't remember now.

      Dave Dave's Astrophotography Channel
      Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject

      Graeme_GrantG 1 Reply Last reply
      0
      • D DaveAuld

        It is basic Labels and Buttons that don't show correctly on App Startup, thing is, it is not all of them, only some of them! Plus the listbox not rerendering to include new received serial message (except if i resize the form forcing a controls overlap redraw, I haven't finalised the layout yet, so not locked the form size yet, allowing me to force this overlap condition). It was with .Net 6, but as a test, I also switch the build to target .Net 7 and then re-built and copied the .Net 7 version across to the target machine, installed .Net 7 when prompted then ran the app and it does the same thing. This is a new utility App I'm writing for the observatory Dome system, the previous App I wrote for the SkyQualityMeter is still working fine, although I think it was built to target .Net 4.8, can't remember now.

        Dave Dave's Astrophotography Channel
        Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject

        Graeme_GrantG Offline
        Graeme_GrantG Offline
        Graeme_Grant
        wrote on last edited by
        #5

        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

        “I fear not the man who has practised 10,000 kicks once, but I fear the man who has practised one kick 10,000 times.” - Bruce Lee.

        D 1 Reply Last reply
        0
        • Graeme_GrantG Graeme_Grant

          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

          D Offline
          D Offline
          DaveAuld
          wrote on last edited by
          #6

          The running app after build and execution.

          Dave Dave's Astrophotography Channel
          Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject

          Graeme_GrantG 1 Reply Last reply
          0
          • S Slacker007

            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.

            D Offline
            D Offline
            DaveAuld
            wrote on last edited by
            #7

            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

            1 Reply Last reply
            0
            • D DaveAuld

              The running app after build and execution.

              Dave Dave's Astrophotography Channel
              Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject

              Graeme_GrantG Offline
              Graeme_GrantG Offline
              Graeme_Grant
              wrote on last edited by
              #8

              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

              “I fear not the man who has practised 10,000 kicks once, but I fear the man who has practised one kick 10,000 times.” - Bruce Lee.

              D 1 Reply Last reply
              0
              • Graeme_GrantG Graeme_Grant

                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

                D Offline
                D Offline
                DaveAuld
                wrote on last edited by
                #9

                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

                Graeme_GrantG 1 Reply Last reply
                0
                • D DaveAuld

                  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

                  Graeme_GrantG Offline
                  Graeme_GrantG Offline
                  Graeme_Grant
                  wrote on last edited by
                  #10

                  The 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 fear not the man who has practised 10,000 kicks once, but I fear the man who has practised one kick 10,000 times.” - Bruce Lee.

                  1 Reply Last reply
                  0
                  • OriginalGriffO OriginalGriff

                    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!

                    D Offline
                    D Offline
                    DaveAuld
                    wrote on last edited by
                    #11

                    It was me all along! Edited the original post with the tldr;

                    Dave Dave's Astrophotography Channel
                    Find Me On:Web|Youtube|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject

                    1 Reply Last reply
                    0
                    • D DaveAuld

                      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

                      D Offline
                      D Offline
                      Daniel Pfeffer
                      wrote on last edited by
                      #12

                      To 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.

                      1 Reply Last reply
                      0
                      • D DaveAuld

                        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

                        L Offline
                        L Offline
                        Lost User
                        wrote on last edited by
                        #13

                        DaveAuld wrote:

                        I'm deleting this as it was ME who screwed up!

                        Please don't, it's messages like this that allow some of us to think that maybe we are not totally stupid. :-D

                        1 Reply Last reply
                        0
                        • D DaveAuld

                          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

                          Graeme_GrantG Offline
                          Graeme_GrantG Offline
                          Graeme_Grant
                          wrote on last edited by
                          #14

                          Good 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

                          “I fear not the man who has practised 10,000 kicks once, but I fear the man who has practised one kick 10,000 times.” - Bruce Lee.

                          1 Reply Last reply
                          0
                          • D DaveAuld

                            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

                            A Offline
                            A Offline
                            Amarnath S
                            wrote on last edited by
                            #15

                            It 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.

                            1 Reply Last reply
                            0
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                            • Login

                            • Don't have an account? Register

                            • Login or register to search.
                            • First post
                              Last post
                            0
                            • Categories
                            • Recent
                            • Tags
                            • Popular
                            • World
                            • Users
                            • Groups