Just from a design point of view, are you sure you want to be creating and closing a new pipe every second? If you're going to be up and running for a bit, why deal with the overhead of constantly creating and destroying a pipe? Also, in your C# code, you should use a using statement on your pipeClient variable. Its lack may be why you seem to be leaking memory due to incomplete cleanup of your pipe. Be wary of strong drink. It can make you shoot at tax collectors - and miss. Lazarus Long, "Time Enough For Love" by Robert A. Heinlein

If helps. A memory mapped file is an OS supported option. C++ can use and access a memory mapped file. C# can use and access a memory mapped file. So the solution is 1. Study memory mapped files so you specifically understand how they can be shared between applications. I believe sharing requires a specific set up. 2. Study the api for C++ memory mapped files. 3. Study the api for C# memory mapped files. 4. Design how the memory mapped file will be used. Pay attention to failure scenarios. 5. Use 2 and 4 to implement a solution in the C++ app. 6. Use 3 and 4 to implement a solution in the C# app.

Is it possible that the 2 applications that share the memory (File mapping) be developed in C# and C++ respectively. Example: One application in C# to create shared memory Other application 2 in C++ opens and shares the memory file mapping.

David Crow already answered it: [Re: How to convert my MDI Application to open each window as a separate instance of the application - C / C++ / MFC Discussion Boards](https://www.codeproject.com/Messages/5757598/Re-How-to-convert-my-MDI-Application-to-open-each)

I catch what you are saying, it just seemed to me that for the context of the original question the discussion veered. No harm or foul. Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759

There are many good articles about drawing in mfc - which is really pretty much Win32. Rather than have that magical moment where you get it running and it flickers constantly, make sure to look into double buffering with a bitmap. Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759

Nice. :thumbsup:

manoharbalu wrote: The problem is when I click on the view...I have added the below code for selection of tabs. But what does the code look like that responds to the view being clicked? "One man's wage rise is another man's price increase." - Harold Wilson "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons "You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles

I am not a real fan of MFC but I can tell you what windows API is doing. Dialog backgrounds paint by WM_CTLCOLORDLG, WM_CTLCOLORSTATIC it used to be WM_CTLCOLOR and I suspect MFC still uses WM_CTLCOLOR because it has a couple of bugs. Usually what you want to do is return a NULL_BRUSH with GetStockObject(NULL_BRUSH); So this one if you paint the entire dialog then return a NULL_BRUSH WM_CTLCOLORDLG message - Windows applications | Microsoft Docs[^] MFC may use this one and again return a NULL_BRUSH WM_CTLCOLOR message - Windows applications | Microsoft Docs[^] That means it doesn't paint the background before it sends you an WM_PAINT :-) If you want/need to transparent overlay the bitmap you have to use a transparent colour to stop flashing void CDemoDialog::OnPaint() { CPaintDC dc(this); // device context for painting // transfer the bitmap into paint DC using a transparent color dc.TransparentBlt( 10, 10, bmp.bmWidth, bmp.bmHeight, // destination coordinates and sizes &pDCTmp, // source DC .. your DC with bitmap 0, 0, bmp.bmWidth, bmp.bmHeight, // source coordinates and sizes RGB(255, 0, 0)); // transparent color } In vino veritas

The complete background is not changing

manoharbalu wrote: When I call this function inside a thread, the application crashes by triggering a breakpoint. You must not directly access the main GUI thread controls from within a secondary thread! Instead you should PostMessage a user defined message to the main thread window notifying it that it has to do some operation(s). Within the main thread you handle this message and perform the ordered operation(s). See also this great J.Newcomer essay: [Using Worker Threads](http://www.flounder.com/workerthreads.htm)

Sorry for that. As you said I will refer google. Thanks

Thanks for your reply. In the client side: I used OnReceive() and a timer variable which is reset to zero in that function. In a separate thread of 1 second frequency, I increment the timer variable to one. So every one second the timer variable is incremented but it is reset to zero in the OnReceive since the data is received in OnReceive() which is sent by the server every second. When the timer variable exceeds 30 counts, it is elapsed. When the timer is elapsed, I closed the client socket using shutdown and deleted the socket. But When I tested the Server and the client, the server hangs after some 2 hours. Previously my client got hanged or lost connection. Any suggestion, why the server is getting hanged this time?

Yes, but; 1) I highly suggest you install them from oldest to newest. 2) Do NOT open a solution by double-clicking in explorer. Rather, open the visual studio you want to use and then open the solution from there. Also be aware that once you move a solution to a newer version, you typically cannot move back. Also note that starting with either 2013 or 2015, you can use an earlier toolset.

Yes, it's possible, and the same way that you access the functions of any DLL. But your question is not clear, what problem are you having.

Do what Richard says encrypt it when your write and decrypt when you read it. You can go from simple XOR encryption if it isn't that important to the real heavy stuff and there is a pile of libraries and code out there. In vino veritas

Have you made sure you open the file for write in binary mode. FILE * binfile = fopen("somefilename.bin", "wb"); //Open writable bin file You open it with just "w" command and it's in text mode some of the raw struct characters will be translated to tabs, CR, LF etc. In vino veritas

I don't know, you would need to search the CodeProject Articles[^], or use Google for a wider search.

First let me say you are making a mountain out of a molehill ... "test->" is a dead easy string to pick off with a text auto-replace on. Would take me about 30sec to do on code throughout the project. You could also do what a good programmer would do and get rid of the stupid global pointer and pass it into the functions on the local interface. You can keep it as test on the local interface but pass in lets_use_it.test1. You make your code better, safer and it is simply extending a few local interfaces. That is what I would actually do .. globals are evil :-) The question to ask yourself is why are you using the global pointer rather than having a pointer parameter on the functions that use the global? That all said you could keep the pointer "as is" if you want by typecasting but it is frowned on :-( struct test1* test = lets_use_it.test1; /* Is perfectly valid */ In vino veritas

That should work and does on VS2015 and VS2107 so if it doesn't work on VS2008 it's a very old bug. You can however easily hack around it, just make a local variable struct and copy the global struct to the local ... the watch window can't get that wrong and it's one single line of code :-) Other alternative is to try the later compilers, they are free and easy to download and try. In vino veritas