Source code of user-mode APIs is available to registered customers and they can build any library they need. As the evaluation version is provided namely for evaluation and testing (and not for development of actual software), we don't provide custom libraries on request.

What I meant here is the version number, like we are using VC90.CRT 9.0.30729.1, and we are really concerned about libraries compatibility inside our product. But your reply regarding the source code is partially answering this question.

Yet it is still a large concern if we would need to make changes to your code to be able to build it in compatible mode. I mean wchar_t compatibility too. It is also questionable will it still remain compatible with your kernel mode part after that.

We cannot make proper evaluation of your product without answering the questions mentioned above. Also real performance, stress and compatibility testing does require integration into our product.

IMHO our company can be very large customer of yours, so I'm wondering if we can resolve these questions in a private manner.

Thank you for your answers Eugene. As you can see you've built your library with a different version of CRT and that can be a problem if we pass some objects which size for example has changed between these two versions. But assuming that we will rebuild the user mode part with our CRT version and you pass only simple standard types to/from the driver (and you guarantee that comparability will not be broken with CRT change) that should be OK.
Yet if we build your library with another wchar_t setting and it is passed through your driver interface that can be a serious problem. This is something we need to test before buying your product.

I don't know how much you care about another customer with $20K+ license. But if you do, let's try to find some solution where we can make reasonable evaluation of you library working with our application. I can understand that you do not want to share the source code with non customers, but I will highly appreciate if you support group will prepare a build of cbfs.lib which uses CRT 9.0.30729.1 and /Zc:wchar_t- compiler settings in debug and release modes so we can see your product in a real work and not in a simple test app.

"If you design your DLL so that it passes CRT objects across the boundary or allocates memory and expects it to be freed outside the DLL, you restrict the DLL users to use the same copy of the CRT library as the DLL. The DLL and its users use the same copy of the CRT library only if both are linked with the same version of the CRT DLL."

We use cookies to help provide you with the best possible online experience. By using this site, you agree that we may store and access cookies on your device. You can find out more about and set your own preferences here.