0

I recently got a new computer and a copy of Visual Studios 2015. I opened some older projects (C#, winform, VS2010) and can edit the code just fine. However any changes to the UI in the designer, causes the entire UI to or not show part of the screen or glitch out.

Has any one ever experienced these issues? If so, how do I fix i?

Edit: I discovered the issue has to do with the AutoScaleMode attribute of my project's form.

PhoenixLament
  • 741
  • 1
  • 11
  • 32
  • 1
    I believe that VS 2010 solutions need to be upgraded before they can opened in VS 2013 and later (including 2015). You should not be able to open your form until you upgrade. If, however, you managed to do it somehow, using 3rd party controls may be causing it. – Victor Zakharov Nov 09 '15 at 01:34
  • how do you upgrade them? – PhoenixLament Nov 09 '15 at 01:35
  • 1
    Just open a solution in VS 2015, it will prompt to be upgraded. Choose wisely as you cannot go back to 2010 after the upgrade. – Victor Zakharov Nov 09 '15 at 01:36
  • I did this originally and just now, and it indicated no issues upgrading either time. – PhoenixLament Nov 09 '15 at 01:39
  • 1
    Are you using any custom or 3rd party UI components on the form? – Victor Zakharov Nov 09 '15 at 01:40
  • None, just the items from the toolbox – PhoenixLament Nov 09 '15 at 01:45
  • 1
    Well, then the only way to find out is if you posted your project, I could then open it in my environment and see if it works. Strip out all the private stuff if you want, and make sure it still misbehaves. – Victor Zakharov Nov 09 '15 at 01:48
  • I discovered the issue. On my form there is a property called autoscale which seems to be the issue. If i open my designer in notepad++ and change autoscale to None from Font, it works, but the UI on the designer scrunches together really close but displays right when i run the program. The scrunching is not very desirable though :/ – PhoenixLament Nov 09 '15 at 01:52
  • Please add screenshots to your question, to help explain what you mean. – Victor Zakharov Nov 09 '15 at 01:53
  • @Neolisk _"I believe that VS 2010 solutions need to be upgraded before they can opened in VS 2013"_ - incorrect. One merely needs to have VS2010 SP1 installed. With that installed, VS2010+ share a unified project structure without requiring upgrade (most things anyway). https://msdn.microsoft.com/en-us/library/vstudio/hh266747%28v=vs.110%29.aspx?f=255&MSPPError=-2147217396 –  Nov 09 '15 at 01:54
  • @Micky: Too late, I already upgraded all my solutions to 2013/2015. :) – Victor Zakharov Nov 09 '15 at 01:56
  • @Neolisk check the Original Post for screencaps. – PhoenixLament Nov 09 '15 at 02:01
  • Your `before` version looks fine. Why did you decide to change anything? – Victor Zakharov Nov 09 '15 at 02:12
  • @Neolisk see what happens when I go before altering the UI to altering the UI (added a button). Its in the main post. – PhoenixLament Nov 09 '15 at 02:18
  • My proposal stands, wrap up your project, pack into a zip file and share a link here. Unless it's too private / NDA etc. I will try to do same and see what happens / how to remedy. – Victor Zakharov Nov 09 '15 at 02:21
  • There is an NDA on the sourcecode that I can't violate. I'll see if i can recreate this with another application. – PhoenixLament Nov 09 '15 at 02:22
  • Yes, I was going to suggest exactly that. Try to use as few controls on the form as possible, strip out all business logic. I.e. just leave designer code. See if it still happens, chance is you may be able to figure it out yourself by then, just make sure what's left is as simple as possible. It's calling making a [reduced test case](https://css-tricks.com/reduced-test-cases/) btw. – Victor Zakharov Nov 09 '15 at 02:34
  • @Neolisk I removed all the code in our NDA and left a UI shell for you to look at. The error still occurs when you add onto the UI with the designer. How should I send you this zip? – PhoenixLament Nov 09 '15 at 02:56
  • Public hosting, google drive with link or email me @gmail.com - you decide. – Victor Zakharov Nov 09 '15 at 13:14
  • @Neolisk emailed you it. – PhoenixLament Nov 10 '15 at 17:24
  • If you guys discover anything, please share - I have the same problem in a project that I'm working on. Thanks! – justian17 Nov 16 '15 at 20:37
  • @IliaKoulikov Will do, having same issues. – PhoenixLament Nov 16 '15 at 22:04
  • @IliaKoulikov check my answer. – PhoenixLament Nov 19 '15 at 19:34

1 Answers1

0

I wound up setting the form's autoscalemode to none. Doing that seemed to take care of my issues. I had to reorganize my UI but that was worth having the ability to use the designer again.

PhoenixLament
  • 741
  • 1
  • 11
  • 32