Paul Riley wrote: Why bother with all that? There shouldn't be any need for DesignMode or overloading OnLoad. Just handle the Load event. I guess thats to do with your own programming style. To me, its easier to override the function calling the event. You mite rather want to utilize the event, but in that case u need to keep track of it.

Hi Leppie, Thanks for your Reply. But, thats not the problem. I will explain it in Detail. I have created a simple UserControl. There are some limitations(or you can say Bugs) in this control. One such limitation is that the CopyLocal property of the Reference to this Control should always be FALSE. When this control is added to the References of any project, by default the IDE makes the CopyLocal property of the reference to TRUE. Now, this Control is used by some other developers also. and, I cannot ask or expect those guys to manually change the CopyLocal property from True to FALSE everytime they add my control to their Projects. So, I need a WAY by which the CopyLocal property should be FALSE automatically whenever my Control is added to any Project. Actually, I feel(or wish) there is some simple way to do this. Like some Assembly Arributes which will expose the Value for CopyLocal property and the IDE will read it from the Assembly when it is added to the Reference and set the CopyLocal property accordingly. But, I could not find any such Attribute... Thanks, Firoz

Firoz -- I've been meaning to upload an article on this... __typeof() doesn't work on types that haven't been fully parsed by the compiler; this will be fixed in a future release. As a workaround, place a dummy class ahead of your MyControl class and specify it instead: namespace NickHod { namespace Multimedia { private __gc class ThisAssembly { }; \[ToolboxBitmapAttribute(\_\_typeof(ThisAssembly), S"CdDrive.bmp") \] public \_\_gc class CdDrive : public System::ComponentModel::Component { The next trick is to name your bitmap using the fully qualifed namespace where the dummy-class lives. In my example above, the bitmap filename is "NickHod.Multimedia.CdDrive.bmp" In the Linker/Input settings for your project, specify this bitmap under "Embed Managed Resource File" (the linker switch is /ASSEMBLYRESOURCE). The other thing you'll need to do is use sn.exe to genereate a strong-name for your assembly (specified in AssemblyKeyFileAttribute() in AssemblyInfo.cpp), then register it in the GAC with gacutil.exe. Good luck! -Nick This posting is provided “AS IS” with no warranties, and confers no rights. You assume all risk for your use. © 2001 Microsoft Corporation. All rights reserved.

Your assembly needs to be registered in the GAC. To do this it first needs a "strong name", sort of like a GUID. Use SN.exe to generate a strong-name key file. In your AssemblyInfo.cpp file, specify the key file as a parameter to the AssemblyKeyFileAttribute() attribute. Rebuild your assembly. Now use Gacutil.exe to register the assembly in the GAC. This step can be done in a custom-build-step if desired. This posting is provided “AS IS” with no warranties, and confers no rights. You assume all risk for your use. © 2001 Microsoft Corporation. All rights reserved.

MSDN has a BuildRules visual studio addin. It lets you add pre and post build commands to solutions and projects. can't find the link right now... but i know it's on there somewhere

Firoz wrote: Is it possible to create a UserControl in Managed C++? Yes, it is possible! Firoz wrote: Can someone please tell me the Steps. Take a look at The MFC unclickable button ported to Managed C++ by Chris M and Nish (moi) :-) Regards, Nish Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]

When oh when oh when will it come out? I also am waiting on DX9 to begin my game development. -Domenic Denicola- [CPUA 0x1337] MadHamster Creations "I was born human. But this was an accident of fate - a condition merely of time and place. I believe it's something we have the power to change..."

Try using the following API functions... ScrollWindow() ScrollWindowEx() I haven't tested it on an MDI form yet, but logically it should work. Also, don't forget to call UpdateWindow() afterwards, so the the client area is redrawn. Jeremy L. Falcon "The One Who Said, 'The One Who Said...'"

Firoz wrote: the number of Network RoundTrips is going to be the same... How do you figure? As I see it, DCOM needs to setup for each call. If you only call once, this setup (marshalling and whatnot) is only done once. If you do many calls, this setup needs to be done each time. Sure the amount of data (from your point of view) being sent is the same (1 x 10 events or 10 x 1 events), but I think you need to take into consideration the setup and teardown of the connection. Please correct me if I'm wrong. :) J

I am not sure whether you can see the HResult. But if the HRESULT is not equal to S_OK, I think Vb raises an exception with err.number equal to the hresult.!!

Usually Events in COM are a kind of painful. these were designed for in- process DLLs. Each event takes 5 round trips from source to sink to complete its duty. Just imagine, how much load on the network due to these round trips.. If you have 8- 10 events.........think.. 40-50 round trips( calls) I will come up with more info.wait.. Cheers, Anand.

Thanks Firoz

Hi, Use Form_QueryUnload instead of Form_Unload, this might help, becuase Form_QueryUnload called before the client exists, but Form_Unload is called when the application is already being unloaded. By the way, you can stop existing the client using Form_QueryUnload event using Cancel argument. ShadiK. Shadi Al-Kahwaji