For that to happen as you suggest, there should be a test-build of my product against every Microsoft update, given to QA for verification. Only after that should updates be accepted by sysadmin and...

Dear forum,

About two weeks ago Microsoft released a KB update for developers, updating the runtime assemblies (from 8.0.50727.762 to 8.0.50727.4053).
That caused everything we built in the last...

I'm adding 30 at a time.

The full story is, I once had this problem with DLLs built with MSVC, and fixed it by adding in quants.

Now that I've moved to building with Intel C++ compiler, the...

Hi,

I've been experiencing problems when attempting to add resources to a DLL using UpdateResource. I'm adding many images to the DLL, and as soon as the overall image size reaches ~16MB, the DLL...

Well, it is also sufficient to place the function body in the same file as the *declaration*.
For example in my case, moving the function body from b.cpp to a.cpp without further changes would be...

No, both a.cpp and b.cpp are files that compile into one dll. I did not specify the client to that dll.

Gil.

Oh, of course, forgot to mention the __declspec. Well, it is there.
Try out the scenario I depicted and see that although no link problems, a() is not being exported.

Gil.

Hi,
(using MS VS2005) Recently I've found that in order for a function to be exported, dllexport *must* be placed in the same file of the function body. E.g. see the following case:

File a.cpp
...