MySQL Bugs: #92931: MySQL Windows Form generation wizard breaks with XML parse of template

Bug #92931	MySQL Windows Form generation wizard breaks with XML parse of template
Submitted:	24 Oct 2018 15:10	Modified:	22 May 2020 18:52
Reporter:	Charles Peppler	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Visual Studio Integration	Severity:	S2 (Serious)
Version:	1.2.8	OS:	Windows (10)
Assigned to:		CPU Architecture:	Any
Tags:	entity framework, Form Wizard, MySQL Visual Studio Integration

Description:
I just performed the upgrade to MySQL 8.0.13.  This fixed a problem that allows me to use Entity Framework (thank you).  Now that I can generate an Entity Framework model, the MySQL Windows form generator is throwing an error, and will not generate a form.

How to repeat:
I generated my entity model, and went to use the MySQL form wizard.  The wizard asks for your model, and the type of form you want to create (table or form).
It generates an error:  "Name cannot begin with the '>' character, hexadecimal value 0x3E.  Line 2, Position 2.

To repeat:

Create an ADO entity model.

Then, 

Solution Explorer-> 
(right click project) -> 
Add Item... -> 
(filter by MySQL) ->
Select "MySQL New Windows Form" ->
Select the model created above, and the object/table within that model.  Name the form.  Select either Single column layout or Grid, and click "Add".

Error screen comes up with message above.

Suggested fix:
Recreate the error.

Review the template files that are in the MySQL item template set, see if any are corrupt, or if it might be picking up an old version or something.

Help us understand where the template files are stored for VS MySQL Integration, and which one might be at fault.

Has this be resolved? I am experiencing the exact same issue, same steps. I am running MySQL Connector version 8.0.17 with Visual Studio Community 2017. Are there manual steps that will accomplish the same thing as the template wizard?

Please try version 1.2.9. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".