General information
Category:
Windows API functions
Title:
DLL hell redux - MSVCRT versions
Whats the best way to avoid stepping on a user's MSVCRT.DLL file with a different version? Some activex controls i use (from DBI-Tech) require this DLL. users with different flavors of windows have different versions. I've seen situations where windows complains about not finding the entry point on MSVCRT.DLL but still boots and in other cases windows will not boot at all.
Is it "safest" to ship the latest version? Granted that could break other programs expecting perhaps an older version, but as long as my program works, thats all that matters ;) Or, better, as long as windows boots up.
Are these DLLs available for download from msft?
How do u address this issue in an installation routine?
gracias
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only