You can debug Visual Studio by attaching to it manually from another
instance of Visual Studio or by configuring a project properties to run
devenv.exe on the debugging tab.
If the code in question is included in a method that that has the
DebuggerNonUserCode attribute, remove it before you try this or place a
breakpoint inside the method. Otherwise, the debugger will step over
the method entirely.
--
Bryan Phillips
MCT, MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com
Web Site: http://www.composablesystems.net
> When I try to open my .net2 windows form code file in the vs2005 designer, I
> get the error message "Duplicate component name
[quoted text clipped - 9 lines]
> Is there a way to get more details about the exception created while the
> designer is running? (Hook into the designer?)
Hi Rip,
When a form is opened in the designer, an instance of the base form, if
any, is created first(thus, the base form's default constructor is called).
Next the base form's Load event handler is called, if any. At last the
inherited form's InitializeComponent method is called.
> I get the error message "Duplicate component name
> 'iDDataGridViewTextBoxColumn'. Component names must be unique and
> case-insensitive."
The 'iDDataGridViewTextBoxColumn' seems to be the name of a
DataGridViewColumn. It seems that you're trying to add two
DataGridViewColumns with the same name into the DataGridView.
I suggest that you check the above 3 paragraphes of code, i.e. base form's
constructor and Load event handler and the inherited form's
InitializeComponent method to find out the lines of code that cause the
problem.
To check a paragraph of code, you may comment out all the lines of
statements first and build the project if the code is in the base form.
Open the form in the designer to see if it can be opened properly. If yes,
uncomment some of the lines of statements and build the project, if
necessary, and then reopen the form to see if it can be opened correctly.
Repeat the above steps, until you find the lines of code that cause the
problem. Then you could correct the lines of code to solve the problem.
Alternatively, you could debug code at design time. There's a walkthrough
in MSDN for this topic. You may visit the following link for the detail
information.
"Walkthrough: Debugging Custom Windows Forms Controls at Design Time"
http://msdn2.microsoft.com/en-us/library/5ytx0z24(vs.80).aspx
Hope this helps.
If you have anything unclear, please feel free to let me know.
Sincerely,
Linda Liu
Microsoft Online Community Support
==================================================
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.
Linda Liu [MSFT] - 16 May 2007 09:50 GMT
Hi Rip,
How about the problem now?
If the problem is still not solved and you need our further assistance,
please feel free to let me know.
Thank you for using our MSDN Managed Newsgroup Support Service!
Sincerely,
Linda Liu
Microsoft Online Community Support
RipT - 18 May 2007 21:52 GMT
Linda,
Thank you for the information. The class in question inherits
System.Windows.Form directly and the .Designer.cs file which contains the
InitializeComponent method of this class does not contain the string
'iDDataGridViewTextBoxColumn'. Also, I looked through every Name property
assignment in the method and couldn't find any duplicate names.
When parsing the InitializeComponent method of the my class does the
Designer automagically set the Name properties of IComponent inheritors if
they have not been assigned?
> Hi Rip,
>
[quoted text clipped - 59 lines]
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
Linda Liu [MSFT] - 21 May 2007 12:39 GMT
Hi Rip,
Thank you for your feedback.
> When parsing the InitializeComponent method of the my class does the
Designer automagically set the Name properties of IComponent inheritors if
they have not been assigned?
VS designer host indeed has a capacity to name a component with a default
name if the component has not been named.
What control do you place on the form? It seems that the problem is related
to the control placed on the form.
I think it's better for me to have a sample project to research. If
possible, could you please send me a sample project that could just
reproduce the problem? To get my actual email address, remove 'online' from
my displayed email address.
Sincerely,
Linda Liu
Microsoft Online Community Support
RipT - 21 May 2007 16:41 GMT
The control in question seems to be a DataGridView. I'm not sure that I can
reproduce the problem using a sample project because I don't know how the
designer file got "corrupted". (This project is a rapid prototype and not yet
in source control.)
I've now fixed this occurance of the problem by removing all of the
DataGridViews and adding them back.
In the future if I encounter the problem again, I suppose I will attempt to
attach to VS2005 using another instance as a debugger. If this happens and I
am able to discover the cause of any bug, I'll let you know.
Thanks again,
-rip
> Hi Rip,
>
[quoted text clipped - 18 lines]
> Linda Liu
> Microsoft Online Community Support
Marie-Fleur - 06 Aug 2007 10:18 GMT
Linda,
I'm having exactly the same problem - the Designer shows the "duplicate
name" error although the name doesn't appear anywhere in the solution. Do you
want me to send you the project or is there any solution to the problem by
now?
Regards,
Marie-Fleur
> The control in question seems to be a DataGridView. I'm not sure that I can
> reproduce the problem using a sample project because I don't know how the
[quoted text clipped - 33 lines]
> > Linda Liu
> > Microsoft Online Community Support