|
At a quick glance I noticed that your first "for" loop is incorrect.....
What is the exception you're getting?
|
|
|
|
|
hi,
i found a form can't be destroyed after registered for the Main form's timer event. below are 2 methods used to create the form. one register with timer event, one without. i can see that the destructor of the one without timer event registered will be called after i open and close the form several times. but, the one with timer event registered. destructor will be called only when the main app exit.
so, any method to help?
<br />
private Form2 frmbulk;<br />
private int counter;<br />
private void button1_Click(object sender, System.EventArgs e)<br />
{<br />
Cursor currentCursor = Cursor.Current;<br />
Cursor.Current = Cursors.WaitCursor;<br />
<br />
frmbulk = null;<br />
frmbulk = new Form2("Form2_"+System.Convert.ToString(counter++)); <br />
<br />
this.timer1.Tick += new EventHandler(frmbulk.TimerEventHandler);<br />
frmbulk.Show();<br />
<br />
Cursor.Current = currentCursor;<br />
}<br />
<br />
private void button2_Click(object sender, System.EventArgs e)<br />
{<br />
Cursor currentCursor = Cursor.Current;<br />
Cursor.Current = Cursors.WaitCursor;<br />
frmbulk = null; <br />
frmbulk = new Form2("Form2_"+System.Convert.ToString(counter++)); <br />
<br />
frmbulk.Show();<br />
Cursor.Current = currentCursor;<br />
}
|
|
|
|
|
Hi,
if object A (frmBulk) registers an event of object B (timer) it is like B would have a reference to A. Thus to free A you will have to unregister the event. So if you dont need the form any more:
<br />
this.timer1.Tick -= new EventHandler(frmbulk.TimerEventHandler);<br />
Btw: I dont think its good style to bind an event of object A (timer) to an object B (frmBulk) within a third object (main). I think it would be better if main just registers the event itsself and then just calls a method in frmBulk. To free bulk you would then only need to set the private field to null.
|
|
|
|
|
Well in my project in need of following menu extensions
a) make tooltips appear on mouse over the menu item
b) how can i organize the menu in multi columns - currently in one contex menu have about 100 items, whant to organize them on two panels, link "All Programs" menu in Windows
Regardless
|
|
|
|
|
You'll have to ownerdraw the menu and draw the menus yourself. There are no properties to support columns in the menus.
Tooltips, I don't know about. I don't think they're supported. I also don't remember seeing them in any application, at least, not in any normal application that doesn't ownerdraw everything.
But, something to think about -> If I opened a menu and saw a hundred items in it, I'd click Close, then Add/Remove Programs, Uninstall.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Set the BarBreak property of a MenuItem to true to start a new column in a context menu. For instance:
contextMenu1.MenuItems[2].BarBreak = true;
-----------------
| item1 | item3 |
| item2 | item4 |
-----------------
Charlie
if(!curlies){ return; }
|
|
|
|
|
Hi everyone!
Has anyone ever worked with WMI i.e has anyone done any work which involves exposing data to the WMI repository?
I have created a WMI namespace with a managed class in it but it does not seem to accept the creation of instances, which is what it should happen when I expose an instance of a .NET class by publishing it to the WMI. The only way that I can create instances is if I create a sublass and then create instances of it either manually using the CIM Studio tool or using MOF scripts. Am I missing anything? The example given by MS seems to be fairly simple and strightforward and I followed it to the letter, but id does not want to work for me.
Can anyone offer any help?
Thanks,
Marjan.
|
|
|
|
|
See the documentation[^] for the ManagementClass.CreateInstance method which includes an example of how to create an instance of a class for which you're providing instances.
This posting is provided "AS IS" with no warranties, and confers no rights.
Software Design Engineer
Developer Division Sustained Engineering
Microsoft
[My Articles] [My Blog]
|
|
|
|
|
Thank you very much for the reply Heath. I'm now able to create instances. However, it is interesting how I can only create instances on a subclass of my class, and not on the class itself. In any case, now I can write to WMI which is the main thing. 
What will we do without the net?
Regards,
|
|
|
|
|
how can i handle my project in windows event? for example when something happen in windows my project should do shomthing. suppose that someone makes a copy of a text in notepad or anywhere, when user takes this copy i need the data what user has copied, and want to proccess on this data. what should i do?
thanks
m.rastgar
|
|
|
|
|
You can handle a number of Windows events using the Microsoft.Win32.SystemEvents class, which defines several static events.
For handling events from other arbitrary applications you need to hook native Windows messages. Search this site for "SetWindowsHookEx".
Please note that great care must be taken and you really should understand just what a Windows message is and how to write your managed code efficiently and robustly. When you hook native Windows messages you're responsible for the stability of not just your application but all of Windows. You must not throw exceptions, do long operations (like database look-ups), or anything that could slow down the machine. Remember, you're hooking a Windows message before it's dispatched to the destination window and Windows will wait for your handler to return. You could seriously compromise the stability of Windows, so take such a task very seriously and write good, clean, robust code.
This posting is provided "AS IS" with no warranties, and confers no rights.
Software Design Engineer
Developer Division Sustained Engineering
Microsoft
[My Articles] [My Blog]
|
|
|
|
|
In my .NET solution I have a project which has the controls I have developed for use in the main project. If I add the controls in that project to the toolbox I am adding them from the Debug directory. When I compile the controls for release will the main project still be referencing the debug code?
Rugby League: The Greatest Game Of All.
|
|
|
|
|
Its not important how youve dragged the controls into the toolbox. Its important what reference your main project has. If it has a real project reference to your project with the controls then everything should be fine when building in release mode.
|
|
|
|
|
Thanks, how do I do that? I just tried building in release mode and every control from the control project dissapeared. I added the controls to the toolbox using the add/remove dialog and then "browse"
|
|
|
|
|
Right-click on your project and select Add Reference. Click the Projects tab and select a dependent project in your solution. This makes sure that you're always building against the most up-to-date assembly (because it establishes a build dependency) and that you're using the right build configuration (so a release build uses the release assembly from the dependent project).
Any control extending UserControl appears automatically in the toolbox. Do not add it yourself. In fact, don't use the toolbox for the project you're developing within the solution. You'll be changing them often. If you develop in-house controls for use in a project, control the release cycle similar to how you would for a public project and then you could add them to the toolbox. The toolbox is meant for stable controls, not controls you're developing otherwise you will have the problems you're having.
If you need to add a control you're developing to a container control initially, add it manually. It's not hard. Open the source code for the container control (like the Form you're designing), add a private field like you see for other controls, then instantiate it in the InitializeComponent method like you see for the other controls. When you switch back to the designer you can design it like all the other controls you added from the toolbox. It's a one-time process that only takes a few seconds, compared to the time you'll be spending working around problems with adding controls in development to the toolbox.
This posting is provided "AS IS" with no warranties, and confers no rights.
Software Design Engineer
Developer Division Sustained Engineering
Microsoft
[My Articles] [My Blog]
|
|
|
|
|
Thanks for replying.
That's exactly what I am doing. I have a control which inherits from Control so it doesn't appear in the toolbox so I instantiate it myself - however the IDE just gets rid of it sometimes - I thought we weren't supposed to change any code in IntializeComponent.
I have project references in the main project but as soon as I switch to Release build all the controls from the controls project disappear from the main project.
I have been at this for a while now and can't get it to work at all.
|
|
|
|
|
You might have covered this already, but did you check the AssemblyVersionAttribute tag, in assembly.cs if you have one, to make sure it doesn't have any * in it? Replace the * with a number so the version number stays constant from build to build while your developing your control.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
That appears to have worked. Thanks for your help.
Rugby League: The Greatest Game Of All.
|
|
|
|
|
While it's a good idea to control your versions, this isn't necessary when you use a project reference as opposed to an assembly reference.
This posting is provided "AS IS" with no warranties, and confers no rights.
Software Design Engineer
Developer Division Sustained Engineering
Microsoft
[My Articles] [My Blog]
|
|
|
|
|
Something just didn't sound right about what he was doing. At least with this method, we know for a fact he wasn't using project references. Thanks for spelling it out for him! 
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
If you dragged a component from the toolbox than you've got an assembly reference. Project references are recompiled (if necessary) before your project is recompiled, and the assembly is copied locally to your project's target directory. If your controls are disappearing it's most likely because your project is referencing a specific version of the assembly you added originally (and versions greatly matter for assemblies, unlike native DLLs) that is no longer available.
If Dave's suggestion worked, great, but you will still face a problem when you do have to change your assembly version. Be sure to remove all assembly references to projects in your solution and use project references.
You can modify InitializeComponent, but if you don't do it in a designer-friendly manner the designer will not work. Just use the same pattern of code that the designer expects and you'll be fine. I used to do it all the time in the same exact scenario you describe now.
This posting is provided "AS IS" with no warranties, and confers no rights.
Software Design Engineer
Developer Division Sustained Engineering
Microsoft
[My Articles] [My Blog]
|
|
|
|
|
Thanks for replying. How do I tell if a reference is an assembly reference or a project reference?
|
|
|
|
|
You as the developer don't know what comprises your own project?
If you need to check, right-click on your solution and select Configuration Manager. Look at the dependencies for your project by selecting your project from the drop-down. If there's a disabled checked checkbox, then you're got a project reference. If not, you're referencing an assembly.
You can also open the .sln file (your solution file) in notepad or some other plain-text editor and look at the solution text to see what is listed. It should be quite obvious.
For a 60+ project solution I used to manage while a senior software architect for another company I never once had a problem - nor did any of my developers - because we all used project references.
This posting is provided "AS IS" with no warranties, and confers no rights.
Software Design Engineer
Developer Division Sustained Engineering
Microsoft
[My Articles] [My Blog]
|
|
|
|
|
I have some controls inherited from UserControl in the sub project and they appear in the toolbox on the My Controls tab but I also have some controls which inherit from Control - how do I get those to appear in the toolbox? At the moment I am editing the code generated by the IDE in the "Windows Form Designer Code" in order to use them which, of course, means they can be gotten rid of at any time. I just want to be able to drag them from the toolbox. How do I do that?
|
|
|
|
|
my project uses an access data base (mdb file) and i want to encrypt that file to prevent abusing the database but if i change the file my project cannot use it because adoconnection can not connect to this encrypted file and if i decode the enrypted file in my project,during running of my project the database file can be abused in out of my application area. what should i do with this problem...
thanks
m.rastgar
m.rastgar
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
