Visual studio 2017 - reading windows forms created in VS2015

Question

0.00/5 (No votes)

See more:

VS2017

I have just upgraded to VS2017 R3 (my VS2015 had died and all attempts to rebuild it failed). I have tried opening old VB and C# windows forms projects created in VS2015 but they will not open. It looks like the problem is with GridView and ToolStripMenuItems - the methods and properties in the .NET are still there and I can create new GridViews on new forms; it is just existing ones the make forms unopenable.

I have a load of on-going projects that have ground to a halt.

Any help that you can give would be very gratefully received. Ideally, I'd like to be able to open the forms in form designer without having to recreate them - especially as many of the forms are very convoluted and are not ones that I have created.

What I have tried:

. Created new projects with GridViews (these seem to be OK)
. Search the web (nothing even close to matching the symptoms)
. Gone on to the Visual Studio Installation Live Chat - been stuck at position 2 in the queue for the last couple of hours

Posted 1-Jun-18 0:51am

jsc42

Updated 1-Jun-18 4:16am

Add a Solution

Comments

[no name] 1-Jun-18 8:58am

What issue/error you are getting when open your project in VS2017?

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)

jsc42 · Answer 1 · 2018-06-01T04:18:00

Fault found between my ears.

I was testing non-production code just as a precaution and the sample application that I had picked was an old VB program (for displaying and managing cookies in MS-Edge) that had been converted to C# using a VB to C# convertor. The issues were associated with failings in the converter. Loading the old VB version worked successfully; so I took a copy of a complicated 'live' program that included examples of the form controls that had caused the test case to not load. That worked with no issues at all.

Thank you @VinodJangle for your response.