Search:

Not a concern....this is an old legacy program that's being phased out. No chance it will be on Vista or 7. It will only be on the platforms its currently on.





BTW....the above method...

Thanks for the tips/reminders.

I really want to avoid having two separate version of the EXE if possible.

I am now trying a solution like this (hopefully will get time to get on the testers in...

I just tried wrapping with:


#ifdef (WINVER > 0x500)
#pragma inline_depth(0)
#endif

I should know Monday morning if that worked or not.

I have a device handler that was not working with Windows XP. It was fixed by a few #pragma statements ( #pragma inline_depth(0) ) around some areas of code. This fixed it for Windows XP,...

I found a seemingly rare knowledgebase article:
http://support.microsoft.com/kb/322621

That made it appear to be a known problem inside of an MFC DLL. It looks like it should have been fixed by...

Are you saying then, my only main issue to really worry about is dynamically allocated memory that is passed between them? If so, I can probably work around that as I don't think it is done thaaat...

Ok....I guess I need to find out what's possible and what is not.

Just before I started this thread, I started a small 'proof of concept' project (two actually). I created a simple VC++ 8.0 MFC...

I was afraid this might be the answer. What is CRT that you are talking about? Can you point me to any references so I can show others I work with?

OK, it seems my task is changing here at work.

We have old code that is written in Visual Studio 6 (C++ code, lots of MFC). I need to take a part of it out and make it in its own DLL.

Here's...

Not knowing "why" it works is almost as bad as it not working, IMO.

I agree. I don't understand why they would have made a difference where you put them.

== means evaluation like if (a == b)
= means assign like a = c+2

So using double equal there means you are testing logic, not assigning a value. It appears to be that you mean to assign a value...

is this supposed to be:

if ( (GetAsyncKeyState(VK_F8) && x ) > 1)

or

if (GetAsyncKeyState(VK_F8) && (x > 1) )

Compiler probably doesn't know? You have two evaluations there.

Is this in Microsoft Visual Studio? If so, what type of project did you select to start with?

I "believe" it is.......here are CPP and Linker Optimizations (didn't change anything in linker except win98 optimization as it didn't look to do much).
...

BTW, in case you are wondering, optimization is disabled. *FYI*

OK, you asked for it, however, I still don't think its a code problem as this is working code in Visual Studio 6. It's not my code, just mine to maintain/update at the moment....so refrain from "bad...

I have an MFC DLL (old working Visual C++ 6.0 code) that is part of a much larger project (all converted from Visual Studio 6 to .NET 2005). I'm having trouble at one point (at least that I've...

This problem relates to a previous thread, but since I've learned more about the problem it kind of seemed new and warranted a separate thread.

The main problem:
MFC DLL (being called from...

Awesome! That was it. Thank you. :thumb:

How are you writing the file?

CFile? CArchive? Most write type functions have a flush() method that commits outstanding writes.

On a project (old VS 6 project upgraded minimally to work in VS 2005), I changed setting from "no clr support" to "clr support".

I got this warning now (that appears to from another DLL that is...

This to me seems the most likely. I've looked at where its serializing out and it appears to only be CStrings and some normal data types (longs, ints, doubles, etc...).

It appears to be creating the archive from the file, then writing it out as a CSequence to that pSequence pointer. I looked in the old on (through debugger) and the >> operator appears to allocate...

I feel your pain. I've been working for a while upgrading a BIG (50,000 lines of code or something of that order) project from VC++ 6 to VC++ .NET 2005. It's been a long and painful experience (that...