Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,888 questions
Using legacy toolset in VS2019
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 62%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
ManufacturingDeveloper
1
Reputation point
Question: How can I use the toolset from VS2005 in VS2019 ?
As I've seen from stuck-on-an-older-toolset-? it is possible to use older toolsets but the post only shows how to achieve this back to VS2008. It seems there is no "real" toolset for 2005.
Only a community based toolset called Daffodil is availaible. Unfortunately I do not know how this works exactly and I have no idea how to get this in the dropdown menu of VS2019.
Background: I ran in the situation to compile an native dynamic library X.dll (previously compiled with VS2005) which has to link with B.lib and C.lib. These static libs have dependencies on the CRT of VS 2005 and cannot be changed. X.dll itself is consumed by an application A.exe, which is surprisingly compiled with VS2012. We do not have the source for this application either.
As i do not want to get trapped by incompatibility regarding ABI etc, I assume it might be the safest to use th old toolchain ( = VS2005).
Is this correct or is there another approch ?
One I can think of is to wrapp B.lib and C.lib in a D.dll to get rid of VS2005.
X.dll exposes a plain old C-API
Visual Studio
C++
C++
A high-level, general-purpose programming language, created as an extension of the C programming language, that has object-oriented, generic, and functional features in addition to facilities for low-level memory manipulation.
3,636 questions
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Tianyu Sun-MSFT 29,446 Reputation points Microsoft Vendor2022-04-12T09:05:02.063+00:00 Hi @ManufacturingDeveloper , welcome to Microsoft Q&A forum. As far as I know, it is not possible to use the toolset from VS 2005 in VS 2019. As you know VS 2005 is a very old version of VS, the related toolset is not available in VS 2019.
I have checked the toolset
Daffodilwhich you mentioned, and looks like it works only in earlier version of Visual Studio not in VS 2019. You can try to contact the author to confirm this.There aren't many methods to choose, perhaps you can have a try to use new toolset to compile it, but of course, errors should be inevitably. (doc: Upgrade C++ projects from earlier versions of Visual Studio)
-
RLWA32 43,306 Reputation points2022-04-12T10:42:48.13+00:00 Wrapping the static libs in a dll won't help if the static libs hand out CRT objects (e.g., memory allocations, FILEs ) for which the caller is responsible. Those CRT objects need to be de-allocated/closed etc. by the VS2005 CRT that is not used by the caller.
Sign in to comment