Vs2008 is out when I drag my usercontrol into Form?

Question

4.00/5 (1 vote)

See more:

I have a usercontrol (link: http://www.mediafire.com/?h635lk4fazr9e7z), I don't understand what reason that I can't drag it into my Form, when I do this then VS2008 is out. Please check it to help me, thanks.

Posted 24-Aug-12 17:47pm

Andrewpeter

Updated 24-Aug-12 17:48pm

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 25-Aug-12 1:10am

I tried it and confirm it for VS 2008. If I insert your component in the form explicitly, without stupid Designer, it is shown normally, but I cannot not say it behaves nicely: no correct behavior on docking (behaves like a fixed-size thing), looks ugly. At least nothing crashes. Of course, Studio should not crash even if you have some bugs, so this is a Studio bug.

First, do you really need your control to work with Designer? If I don't supply my components for the external users, I don't care about it -- Designer is pretty much a trash part of the Studio to work with it seriously.

If you need to supply your control to some external users, you need to investigate it. First of all, refactor your code to make it less dirty. Remove all hard-coded constants. The ugliest thing you have is "catch {}" -- you block propagation of exceptions -- never do it. Also you have "else {}". You explicitly call dispose of something local, but need to use "using" statement of dispose in "finally". You have "Graphics g = control.CreateGraphics();" which is not used anywhere. I'm almost sure you have more problems. I would not even try to test the control if the code is so dirty...

To investigate, you need to run the whole Studio under debugger. Or you will need to simplify the control down until problem disappears, and restore functionality step by step until you have this problem, to pin-point it. It will take a lot of time...

Sorry, I don't see immediate reason for the crash, it's just needs more time than I can invest; besides, I don't see much sense in it -- I would rather started re-writing it.

However, I have just on good advice on the instrument you can use...

--SA

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)

Sergey Alexandrovich Kryukov · Accepted Answer · 2012-08-24T19:23:00

Please see my comment to the question.

I promised one advice…

Use the following tool to investigate the Studio crash: put almost all of your code of your control in this block:

C#

if (!DesignMode) {
   //rendering, setters, and a lot more...
}

Please see:
http://msdn.microsoft.com/en-us/library/system.componentmodel.component.designmode.aspx[^].

This way, most of the code will work as it works not (I tested it, it does work somehow), but not under design mode, which should prevent Studio crash. Add some functionality feature you really need in design mode one by one until you have the crash again. This way, you will be able to locate the problem. Again, there is a Studio bug, so you just need a workaround. Your final result should still use this (!DesignMode) condition — many things really should never appear in design mode.

But first of all, I would re-write the code.

I found another big problem: your rendering is based on PictureBox. There is no single reason to use this control for the purpose you do. It does not help you at all, only adds up hassles, eats up your development time and resources. This control does not help at all. You should use System.Windows.Forms.Control instead and render everything in the overridden method OnPaint. This is a very usual mistake to abuse PictureBox.

For further detail, please see my past answers:
How do I clear a panel from old drawing[^],
draw a rectangle in C#[^],
Append a picture within picturebox[^],
Drawing Lines between mdi child forms[^],
capture the drawing on a panel[^],
What kind of playful method is Paint? (DataGridViewImageCell.Paint(...))[^].

—SA