Managed C++/CLI

plz tell how to initialized MFC? i need complete syntex . if you could tell the link related code i will be very thank to u. and one thing more if that initialized code is in dll or not in dll. how to deal with it ? r00d0034@yahoo.com

Thanks Nick, I tried it in the end and it worked fine, I was only creating a simple wrapper to the DnsQuery API Function, and in the end its all worked quite well. Thanks again, Paul -- Paul "I need the secure packaging of Jockeys. My boys need a house!" - Kramer, in "The Chinese Woman" episode of Seinfeld MS Messenger: paul@oobaloo.co.uk Sonork: 100.22446

Wouldn't solving conflicting names with simple rules a real interesting stuff to come up with ? If I remember well, the Eiffel language has this feature, when deriving classes. And I swallow a small raisin.

Thanks ;) With Best Regards :rose: My month article: Game programming by DirectX by Lan Mader. Please visit in: www.geocities.com/hadi_rezaie/index.html Hadi Rezaie

I guess there is no definite answer. I am assuming you would write the web service in Managed C++, so at least some of the code could port over with ease. You would basically just want to rewrite the application from scratch, referencing your existing app. for logical aspects. If your existing code is complex and convoluted then your web service very well could be too. Using Visual Studio.NET will definitely help you in the web service arena. Soliant | email   "the result is that VC7 is the only compiler to generate optimized MSIL" - Stanley Lippman

first of let me tell u what i am tring to do . i am trying to convert a vc++ app into dot net.that program is related to mouse and keyboard hooks. it return HINSTANCE.i know what i do mostly. i did not initialize MFC from an MC++ app.plzz tell how to do it? yes it crash at exacetly that point.plzz help. may i use MFC DLL in managed code if yes then how? can u provide example related to that?

Thanks, Anders pal! I will accept your advice. I cross-posted because my boss is asked me to hand in the project immediately, but I am in trouble as you see. Cheers, George

Thanks, Nisk pal! I think I have fully understood the meaning of size_t under your directions and other pals in ATL/WTL forum. :-) :-) :-) Have a nice weekend, George

Sure you can. In fact unless it's a very simple test class I am trying out, I usually put the declarations in the header and the implementations in the cpp file. Regards, Nish Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]

Hi squeaky Read my article below :- http://www.codeproject.com/system/newbiespawn.asp That'll show you how to use CreateProcess which gives you both the process handle and the thread handle for the main thread. Now use EnumWindows to enumerate all top level windows. Call GetWindowThreadProcessId on each HWND and compare with the thread ID you had saved earlier. If they match, post a WM_CLOSE message to this HWND. Hope this helps, Nish Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]

http://www.codeproject.com/managedcpp/ntrack.asp Nish Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]

No; MFC classes are not garbage collected. Depending on the usage, MFC has built in behavior to manage the lifetime of some classes, e.g. views, using standard C++ technique (new/delete). 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.

First of all, your variable naming implies that you are expecting tmpProcess->Handle to be a window handle. It is not; it is a process handle. Also, in C++, since Process is a reference type, it must be declared as a pointer: System::Diagnostics::Process* tmpProcess; The op_Explicit() operator you are calling exists for implicit casting purposes in C# -- convert the value held by the IntPtr to an __int64, int, or void*. (Recall that the native size of the value of an IntPtr is determined by the platform; on 32bit hardware it is 32 bits, would be 64bits on 64bit hardware). I'll ask around, but I think in C++ it is impossible to disambiguate this function-call because in C++ it is illegal to overload a function based soely on its return type, which is what is happening here. You can get the same functionality by calling one of the conversion members: IntPtr::ToInt32(), IntPtr::ToInt64(), or IntPtr::ToPointer(): long l = hWnd->ToInt32(); 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.