Home/ Questions/Q 9155315
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-17T12:34:12+00:00

Our app is targeting .net4.0, code is mix of projects in vb.net and c#.

  • 0

Our app is targeting .net4.0, code is mix of projects in vb.net and c#. This particular project is vb.net. My dev machine is windows 7×64 pro with vs 2010 sp1 and a VS2010 + Windows 8×64 VMWare machine.

In windows 7 our tablelayoutpanel shows correctly in design time and the resultant executable winforms application. However running our application in Wondows 8 we saw that the order of columns in TableLayoutPanels are mixed up.

I have attached a screenshot, now at first we just thought its something to do with the way windows 8 works and hopeed that a recompile in windows 8 would fix it. Nope! Opening the same source file in windows 8 shows as per the attached screenshot, mixed up columns. So we fixed the ordering, compiled and in windows 8 it shows up fine, but back in windows 7 we get the mixed up column orders all over again.

So fix it in either windows 7 or 8 and the other shows incorrectly?

Can anyone offer any suggestions? its not like we can email Microsoft for an answer and expect a fix any time soon.

screenshot

Edit: We are really stuck with this, does have any ideas/suggestion?

Edit2: MSDN Community Support told me to raise it with connect.microsoft.com, which i have done but i dont expect it to ever be solved. So i will have to replace this user control with something else and hope i dont find other user controls with similar issues or Windows 8 support will just get shelved permanently.
Going to close this on the basis that its accepted as a bug and wont be fixed any time soon.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    For anyone else with this issue.
    I have a response from connect.microsoft, its fixed in 4.5 8th Jan 2013 patch release.

    Posted by Microsoft on 17/01/2013 at 17:52
    Thank you for your feedback. We are able to reproduce this issue and confirmed that it had been fixed in the recently release update to .Net Framework 4.5 that is available on Windows Updates starting on the 8th of January.

    Many customers have found it useful to discuss issues like this in the forums (http://www.microsoft.com/communities/forums/default.mspx) where Microsoft and other members of the community can suggest workarounds. Please keep the feedback coming.

    Thanks,
    The Windows Forms Team

    • 0