Visual studio 2012 form design surface

Question

0.00/5 (No votes)

See more:

VS2012

Foolishly, I just upgraded my development machine to Windows 10.
I use a third party development framework called StrataFrame

Previous to the upgrade, all I had to do was to drop the control from the toolbox onto the form and it showed up on the form right where I dropped them. Unfortunately, this no longer happens to all controls just to the ones that are not associated, directly, with a business object ... such as a Button control. Instead, they show up at the bottom of the form designer where the controls with a non-visual component appears. The control has a text of "button1" as one might expect.

Now, I'm not asking you to troubleshoot StrataFrame for me as that is impossible for you to do unless you own it. However, I am hoping one of you will know how Visual Studio 2012 determines on which area a control appears when one is dropped onto the form.

Thanks so much,

CT

What I have tried:

Dragged multiple controls onto the form designer (Visual Studio 2012 WinForms Form Designer)
Some appear in the visual design area (at the top) where they should and did, previous to the upgrade to Windows 10.
Some appear (which previously did have a visual component) at the bottom of the visual form designer (where the non-visual controls previously appeared)

Posted 4-Jun-16 14:33pm

Charles T. Blankenship

Updated 5-Jun-16 10:22am

Add a Solution

Comments

BillWoodruff 4-Jun-16 21:10pm

Two questions: 1. if you start a new WinForm App in VS 2012 without StrataFrame, do you observe any of the siting behavior with drag-dropped Controls you describe here ?

2. are you using the latest installer for StrataFrame and have you followed the instructions posted here:

http://forum.strataframe.net/Topic33068.aspx

George Jonsson 4-Jun-16 22:11pm

You got a misplaced reply.

Charles T. Blankenship 4-Jun-16 21:50pm

Wow, thanks for the quick reply:

Answer 1: A brand new WinForms application (not a StrataFrame) application allows all visual controls in the Common Controls toolbox to drop onto the form as expected. The only ones that do not were the ToolTip and the NotifyIcon which I believe is normal behavior. What makes VS 2012 determine when to drop a control onto the top design surface or the bottom non visual design surface?

Answer 2: StrataFrame was already installed when I upgraded to Windows 10. All I had to do was to recompile all of my StrataFrame libraries and my applications "ran" perfectly, but the design surfaces were whack. I wasn't using VS 2015 at the time so I never tried to install SF within that. I was using VS2012 with SF already installed (to beat a dead horse ;-)).

BillWoodruff 4-Jun-16 22:06pm

1. notice the Tabs in the ToolBox called 'Components, and 'Dialogs: their behavior is not the same as Controls; they extend/provide functionality. Confusingly, the NotifyIcon and ToolTip (under Common Controls) whatevers also extend/provide functionality to the Form and all Controls, respectively.

2. I note that the instructions for using the .visx on Strat's site I referred you to also mentions that this .vsix is valid for VS 2012, and VS 2013.

3. Go and look in the Designer.cs file of the Form and observe what the internal setting for 'Location is on some of the controls that are not ending up where ou want them.

Is there some way for you to post a response to that thread on the Strata Forum ?

Charles T. Blankenship 4-Jun-16 23:15pm

Nothing I've tried is working ... sooooo ... I'm going to uninstall and re-install StrataFrame on the newly upgraded Windows 10 machine, execute the VSIX instructions and see where we go from there. If that doesn't work then there is some incompatibility with StrataFrame and Windows 10 so it's back to re-installing Windows 7.1 Pro (worst case). I'm testing the process on a VMWare machine to see if a new installation in the proper order fixes the problem:
1. Install Windows 7.1 Pro and patch it.
2. Install Visual Studio 2012 up to Patch 5 (I believe)
3. Upgrade to Windows 10 (if it is even possible to update from 7.1 ... might only upgrade from 8.1 ... dunno) and patch it.
4. Install StrataFrame and follow VSIX instructions.
5. Open project and see if it builds and behaves properly

Thanks George for notifying me of how to place comments ... I wasn't paying attention.

CT

BillWoodruff 5-Jun-16 5:42am

Good luck !

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Charles T. Blankenship · Answer 1 · 2016-06-05T10:22:00

I thought it was enough simply to recompile the StrataFrame libraries, not so.

Once the upgrade to Window 10 took place I had to uninstall and then reinstall StrataFrame. All, now, is well. At least I think it is as the design surface is working just fine.

Thanks for the attention guys.

CTBlankenship

I still would like to know how VS 2012 determines where to place the object dropped onto the form ... on the form actual or below the form in the non-visual design area.