Visual Studio Installation files

[KoldMen]

I've problem creating new dll files for windows using the visual studio installation files. The visual studio files in your repository are very old (version 9 and version 10). The current version is 15. Can you please upgrade ?

[tkralphs]

Last time I checked, the upgrade to the latest version worked without problems, so it didn't seem worthwhile to upgrade all 20+ projects, which takes a non-trivial amount of time. Did the upgrade fail?

Some individual projects do have more recent files (like Cbc), so if you are trying to build a particular project, you might check that project to see if it has more recent files. If you tell me what you're trying to do, I can try to guide you.

[dnjiang]

When I tried to load the solution (.sln) to VS 2012, none of the libxxx projects can be loaded. Should I download individual components, eg., clp, cbc, as well? I also downloaded clp individually and tried to load into VS 2012 and VS 2017, the Clp solution can not be loaded either.

Your instruction says that "after obtaining the source from coinbrew, load the solution into VS". So I downloaded coinbrew, but it is unix/linex script and cannot be run on Windows. I am confused.

[dnjiang]

Found out why: the download from GitHub does not contain all dependency packages. For Clp, I had to download the tarball or zip file from here https://www.coin-or.org/download/source/Clp/ to load the solution into VS.

[tkralphs]

Although coinbrew is a bash script, bash comes with Git for Windows and other git distributions, so you probably already have it on your machine if you have git. Alternatively, you can down the source tarballs with all dependencies included, as you discovered. I will add that to the documentation.

[jhmgoossens]

A bit late, but I will get started with a Visual Studio 2022 solution, at least for projects that contain these v17 project files already (Cbc and dependencies)

Note that current tarballs (see above) no longer contain sources of dependencies, as mentioned in Cbc Discussion 592, making it even harder to not use coinbrew.

[tkralphs]

@jhmgoossens If it is a big issue, it should be pretty easy to modify the Actions workflow to upload a second tarball containing all sources, including dependencies. I would suggest doing this only for releases.