vb2008 pro Warnings

  • Thread starter Thread starter Galen Somerville
  • Start date Start date
G

Galen Somerville

On two of my forms the following code causes a warning"

Me.components = New System.ComponentModel.Container
Dim resources As System.ComponentModel.ComponentResourceManager =
New System.ComponentModel.ComponentResourceManager(GetType(frmSweep))


Warning 1 Failed to parse the following code:

Me.components = New System.ComponentModel.Container


The code within the method 'InitializeComponent' is generated by the
designer and should not be manually modified. Please remove any changes and
try opening the designer again. 0 0


Yet on all other forms the following has no errors

Me.components = New System.ComponentModel.Container
Dim resources As System.ComponentModel.ComponentResourceManager =
New System.ComponentModel.ComponentResourceManager(GetType(frmMain))

The basic difference between the two bad forms and the other forms is, the
two forms have a User Control on them.

Any suggestions?

Galen
 
Hello Galen,

According to your description, you received a warning said "Failed to parse
the code" when compiling the project, correct? If I misunderstood anything
here, please don't hesitate to correct me.

Is this code defined in "InitializeComponent" method gendered by VS IDE in
designer.vb file? Did you make any change in it?

It seems your User Control results the issue. After you drag-drop User
Control on Form Control, the warning shows up, correct?

In order to narrow down the issue, is it possible for you to create a new
Form control, and then drop that User Control into new form. Will the
warning show up in new form? If the issue occurs, you can create a new
Winform project and add refer to your User Control. Then, please add a new
form control in new project and drop User Control on it again. Does the
issue occur again? This could help on identify if the problem is User
Control specific or Project specific.

We haven't heard such issue in VS 2008 pro so far. Thus, we need more
detailed information for further research. We will appreciate if it's
possible for you to provide us detailed steps to reproduce the issue. We
are glad to drill down into the problem.

Hope this helps, please feel free to let us know if you have any more
concern. It's my pleasure to assist you.
Have a great day,
Best regards,
Wen Yuan

Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Will give it a try.

Galen

"Wen Yuan Wang [MSFT]" said:
Hello Galen,

According to your description, you received a warning said "Failed to
parse
the code" when compiling the project, correct? If I misunderstood anything
here, please don't hesitate to correct me.

Is this code defined in "InitializeComponent" method gendered by VS IDE in
designer.vb file? Did you make any change in it?

It seems your User Control results the issue. After you drag-drop User
Control on Form Control, the warning shows up, correct?

In order to narrow down the issue, is it possible for you to create a new
Form control, and then drop that User Control into new form. Will the
warning show up in new form? If the issue occurs, you can create a new
Winform project and add refer to your User Control. Then, please add a new
form control in new project and drop User Control on it again. Does the
issue occur again? This could help on identify if the problem is User
Control specific or Project specific.

We haven't heard such issue in VS 2008 pro so far. Thus, we need more
detailed information for further research. We will appreciate if it's
possible for you to provide us detailed steps to reproduce the issue. We
are glad to drill down into the problem.

Hope this helps, please feel free to let us know if you have any more
concern. It's my pleasure to assist you.
Have a great day,
Best regards,
Wen Yuan

Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
Click to expand...
 
Back
Top