|
Hello,
You can use the Location property of the control.
YourButton.Location = new System.Drawing.Point(x, y);
All the best,
Martin
|
|
|
|
|
I just opened all the forms in my C# project to make sure that they'd all been given the right title and all of the controls had disappeared from one (FormEquiv). The form had gone back to the 300x300 blank default form. I checked the code in FormEquiv.cs and FormEquiv.Designer.cs and everything seemed intact, except for the bits regarding the form object in the Designer file, which had gone back to default. All of the lines with "this.Controls.Add(this.btnAdd);" etc were gone too. I ran the program and it just popped up the blank dialog.
Is there an easy way to fix this, or should I just redo the form settings and manually add the contrls back in?
Any ideas what might have caused this? I checked a build that I did about an hour ago and the form was working fine.
Jack
|
|
|
|
|
What has the designer done now!?
Don't you just love it when a morning's work disappears before your very eyes?
If you are a regular user of the V1.x VS.NET design-time environment (in C# at least, I don't do much by way of VB, so I can't comment) then you will no doubt be well aware of the effects of the amazing self-destructive design-time environment. If you are one of the lucky few who hasn't, I'll explain the symptoms.
You have been happily working in the designer, laying out controls, binding in bits of logic, switching between the code view and the designer view, building, debugging. Then, all of a sudden, half your controls disappear, and/or some move to the top left, and/or all your embedded resources (images in particular) vanish without trace... Control-Z doesn't seem to work quite right... The black gloom of despair fogs the monitor, and you're forced to go and get a really strong cup of coffee. Before you start again.
In the office, we call it "the woe", and it has happened to us...a lot.. Working out why it happens is rather tricky. Finding a reliable repro is nearly impossible; but we have found some of the contributing factors, reliable ways to avoid the problem - and how to mitigate it when it does occur.
The first thing to understand is that the problem is a defect in the round-tripping of the code that the designer generates in the InitializeComponent() method. Basically, when things go awry, it sometimes panics and just leaves some of it out. It doesn't affect the members inserted at the top of the file (the fields that hold the references to the child controls stay put), only the initialization code. That's why, when the problem occurs, you can't just add controls with the same names as the ones that vanished. They conflict with these disembodied fields. This leads me to tip number 1, for people who have already suffered the woe. (See Tip 5 for how to mitigate the woe as it occurs).
Tip 1 - If you have a saved, corrupted file and are trying to recover from the woe, clean up the orphaned fields so that you can reuse the names
But ideally we would avoid the woe completely! What we want is a procedure for working with WinForms projects in the IDE that won't break. How might we go about this?
Well, the problem usually occurs because you don't have a clean, working build of the solution including all the dependencies of your designable control. Now - most of the time, this isn't an issue. After all, you can use the designer right out of the box, without having built the solution at all. But if you have a control from another assembly (or even this assembly!) on your design surface, and it is not built 100% successfully and copied somewhere it can be referenced by the design time environment (the project directories will do), then you invite the possibility of the woe. Therefore, you should follow tip 2.
Tip 2 - Always do a complete solution build before attempting to open any designers
Unfortunately, by default, the VS.NET IDE will reopen the views you had open when you last closed the solution; which is not that great if the solution is not cleanly built when you open it again. Therefore, you should also apply tip 3:
Tip 3 - Always close all of the designer windows before closing the solution
OK, so now we do a build. If it doesn't build cleanly, refer to Tip 2, and then use the code editors only to clean up until it builds successfully.
When it does build cleanly, we can open a designer, do our layout, add code etc. All should be well. When we are ready to try a build and test, apply Tip 4.
Tip 4 - Close all designer windows before doing a build
I can't say this often enough. Never, never build the solution without closing all designers. In fact, it is probably a good idea to write a macro to do this for you, and replace the build/run/debug shortcuts, buttons and menus with calls to this instead. Or be very disciplined. You will get away with it 9 times out of 10, and the tenth time...kaboom.
Ok, we've closed the designer windows and kicked off the build. If the build fails - refer to Tip 2. Don't forget - you have to clean everything up so that it builds using only the code editors. Don't accidentally open a designer... When it builds clean, you can rinse and repeat.
If you follow those guidelines, you'll avoid 99% of all the cases of the woe. But there are a couple more categories of misfortune that can befall us...
The first occurs when we reference controls from an external assembly that is pre-built (i.e. we reference the assembly itself, rather than a project in the solution). You open up the designer, and either the controls have vanished from the surface, or you get a design-time exception (the block of misery-inducing text that indicates the designer has had a panic with your control). Firstly, apply Tip 5. Tip 5 is very useful!
Tip 5 - In Case of Woe, Don't Panic. Don't press save. Don't press undo. Just close the designer window (and any applicable code windows) and say "no - I don't want to save the changes".
If you do this, then the messed-up code won't be saved. It will revert to the version prior to the designer being opened. Tip 5 is also useful if you accidentally break any of the guidelines in Tips 2-4.
So - what causes this particular issue? It seems to be something to do with the design time environment failing to find references that it had no issue with a moment ago. The files haven't moved, no-one has recompiled them. The designer has just taken against them. You can close the IDE and reload it, and it still doesn't work. So, apply Tip 6.
Tip 6 - Remove the references to the assemblies that contain the controls that vanished, and add them back again
You can then reopen the designer and all should be well...
Finally, there's the nastiest of the problems. You can build a control that has an implementation bug that causes an exception at design time. Everything will build fine, but when you reopen the designer you'll see the exception text. As usual, the designer can recover from this 9 times out of ten, but the tenth time induces the Woe.
Recovery is simple - you should first apply Tip 5 and then fix the problem using the code editor only. Fixing it can be tricky. If inspection doesn't work, a handy tip is to open a second IDE, and attach to the original instance of VS.NET. You can then set some breakpoints in your control and watch what happens as you open the designer.
Some of these tips are a bit tedious, and require some discipline, but if you follow the guidelines, you should avoid the woe almost completely, and easily be able to recover if it does occur.
Good luck!
Smile: A curve that can set a lot of things straight!
(\ /)
(O.o)
(><)
|
|
|
|
|
Hello Muammar,
I'm really looking forward for a "The WOE" article of you!
I'm well experienced at this problem, but I get really tired at explaning it every time new in my office!
So now I have this post to forward it in my office and maybe you find time to write an article.
All the best and thanks for this summary!
Martin
|
|
|
|
|
Thanks Martin I think it does worth an article.
Smile: A curve that can set a lot of things straight!
(\ /)
(O.o)
(><)
|
|
|
|
|
Suppose i have a control (say a button) that is created at run time. How can i change the size of the button at run time?
thanks in advance.
Keshav Kamat
India
|
|
|
|
|
|
thanks.
Keshav Kamat
India
|
|
|
|
|
Welcome
Regards,
Satips. ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
|
|
|
|
|
I am working in C#.Net.I am using the context menu. That context menu have 'copy' menu. how to write the coding in copy menu click? (i want to copy the folder.)
suja
|
|
|
|
|
Article By Ralph Arvesen Context Menu[^].
Hope this will Help you.
Regards,
Satips.
|
|
|
|
|
Hi,
Can any body tell me whether Ribbon Control is available from Microsoft or not? If not, then which company's Ribbon control is most stable and reliable? Since i have downloaded some which generate exceptions are they are not fully functional.
Thanks in Advance....
Wasif Ehsan,
Pakistan.
|
|
|
|
|
|
I am talking about whether it is available for us the developers or not. I know it is used in Office 2007 but i need to use it myself.
|
|
|
|
|
Yes if you want you can pay and get it from Microsoft.
Regards,
Satips.
|
|
|
|
|
Where?
How Much?
Kindly give me your hotmail address so that i could add you in MSN Messenger
Regards,
Wasif Ehsan.
|
|
|
|
|
|
|
Hi,
I am beginer in C#. I have an array and ComboBox that are define in Form1.Now I want to use this objects in a Usercontrol that open by preesing a bottun in form1.People say I should use property,but I don't know how I should write and use propert.
I wouls appreciate if somebody give me an example of define and useing of Propetie.
regards
|
|
|
|
|
|
I read some article,but I couldnot find any sample.
please give me some samples.
thanks
|
|
|
|
|
i doubt it, i clicked the first result and it had heaps of examples.
|
|
|
|
|
That's right,but I could not get y answer.
Look. I have a main form that there is 3 buttons and 1 combobox.
in this main form i declare an array that keeps the name of my menu after pressing the related key.
string[] Name_Menues = new string[10];
When I press the first button, a usercontrol apprear and I write the below code to fill the combobox.
Name_Menues[0] = "Input_Passengers";
Cmb_Box.Items.Add(Name_Menues[0]);
Cmb_Box.SelectedItem = Name_Menues[0];
Uc_Check_In uc = new Uc_Check_In();
pnl_Main.Controls.Add(uc);
uc.BringToFront();
uc.Dock = DockStyle.Fill;
The usercontrol appers,after pressing the button .Now I want to clear the contest in combobox in main form when press another key in usercontrol.
|
|
|
|
|
Hello,
My suggestions are:
Use the dynamic "System.Collection.Specialized.StringCollection" instead of fix string[].
For filling the ComboBox with values of you field, you should use a loop.
Hold the instance of your UserControl as a field member of the form and only hide it (Visible = faalse) if you don't need it.
Alireza3839 wrote: The usercontrol appers,after pressing the button .Now I want to clear the contest in combobox in main form when press another key in usercontrol.
Your usercontrol should implement an event (delegate) which is called after you button was clicked.
Your form connects to this event and clears the combobox in the event handled code.
Hope it helps!
All the best,
Martin
|
|
|
|
|
Our client needs C# with SQL Server consultants immly.
Total postions 5 and rate is $50-$55/Hr DOE.
Desired exp is 5+ Yrs and it is a long term.
Location is Orange County,CA.
Intrested candidated email your resumes to navconsultantsinc@gmail.com
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
