whoward69
DLL Minion
I was going to title this "Adventures in Obtaining Unobtainium" …
So I've got a shiny new Windows 10 64-bit laptop
Steam and Civ V are installed, my mods are installed and I'm playing
... I even have the SDK downloaded and FireTuner working ... so I'm also cheating 
ModBuddy next. Doesn't run by double-clicking the .exe file
OK, I'll try it via Steam and the SDK start menu ... completing install ... looks promising ... needs VS-2010 Isolated Shell ... no longer exists on the Microsoft web site.
Let the hunt for unobtanium begin!
Trawling through my old notes, hard-disks and files I find it - much rejoicing
But wait, at the back of my mind is something about needing to install VS-2008 first if you want to compile the DLL (and that's the whole point of this particular exercise) …
Yep, in my notes "install VS-2008 before VS-2010 or you need to uninstall VS-2010 to fully install VS-2008"
OK, lets find VS-2008 ... several hours (and much swearing later) ... got it!
VS-2008, despite being only the web-installer, installs perfectly (looks like MS left all the VS-2008 .cab and .msi files on their servers and only removed the web pages to the VS-2008 installer download - please, no one tell them!)
Perfectly? Mmmm. Let's see if the un-modded DLL code will compile. OMG, it does (using the 2008 solution file)
Yeah! Feeling cocky, I install VS-2015 and try to compile DLL-VMC. BOOOO!!! All kinds of errors about missing build tools, but I thought those were in VS-2008.
Hmmmm ... back to the notes. Looks like I also need VS-2010 SP1. Now I know where those are ... in the same backup as VS-2008 (perhaps I'm not as stupid as I look!)
VS-2010 refuses to install ... oh yes, some idiot installed VS-2015 first ... right uninstall VS-2015 …
VS-2010 now installs, and SP1 slips over it easily. Let's see if we can compile the unmodded DLL with VS-2010 (using the 2010 solution) ... YES!!!
Feeling brave, I re-install VS-2015 (you've already guessed this is going to be a mistake, haven't you)
DLL-VMC compiles
(Quick burst of the "Hallelujah Chorus" can be heard in the background!)
Let's start ModBuddy. Damn, got carried away and forgot the VS-2010 Isolated Shell (which was how I started this wild goose chase!).
Damn! $#*^!!! Won't install. Ooops ... sheepishly ... I installed VS-2015 didn't I …
Uninstall VS-2015 (why does this take so long?), install VS-2010 Isolated Shell. ModBuddy still won't start, something about different patch versions ... reapply VS-2010 SP1.
Oh yeah! Cooking with gas! ModBuddy starts (can't remember exactly what the directories need to be set to, but I can copy those from my old setup later).
Reinstall VS-2015 (third time lucky?) Hoo b****y ray! DLL-VMC still compiles and ModBuddy still works.
So ... I could just stop here, but where's the fun in that? I want VS-2019!
And anybody who guessed that that was going to be another epic just lost
VS-2019 downloads and installs first time. So I start it up, open the DLL-VMC 2015 solution file (do NOT OK the dialog that prompts to udate the project, just Cancel it), and it compiles without problem. I'm amazed, I was expecting serious pain!
Now all I have to do is find the time to start modding again.
William
In summary, to build a DLL based mod on a new Windows 10 machine
* Install VS-2008
* Install VS-2010
* Install VS-2010 Isolated Shell
* Install VS-2010 SP1
* Download the Civ V SDK and start ModBuddy from the Steam SDK Menu (to complete the installation)
* Install VS-2015 (optional)
* Install VS-2019
* Open the DLL source and compile it, when prompted to update the project, do NOT click OK, just Cancel
* Start ModBuddy by double-clicking the .exe file
* Start modding
So I've got a shiny new Windows 10 64-bit laptop

Steam and Civ V are installed, my mods are installed and I'm playing


ModBuddy next. Doesn't run by double-clicking the .exe file

Let the hunt for unobtanium begin!
Trawling through my old notes, hard-disks and files I find it - much rejoicing

But wait, at the back of my mind is something about needing to install VS-2008 first if you want to compile the DLL (and that's the whole point of this particular exercise) …
Yep, in my notes "install VS-2008 before VS-2010 or you need to uninstall VS-2010 to fully install VS-2008"
OK, lets find VS-2008 ... several hours (and much swearing later) ... got it!
VS-2008, despite being only the web-installer, installs perfectly (looks like MS left all the VS-2008 .cab and .msi files on their servers and only removed the web pages to the VS-2008 installer download - please, no one tell them!)
Perfectly? Mmmm. Let's see if the un-modded DLL code will compile. OMG, it does (using the 2008 solution file)
Yeah! Feeling cocky, I install VS-2015 and try to compile DLL-VMC. BOOOO!!! All kinds of errors about missing build tools, but I thought those were in VS-2008.
Hmmmm ... back to the notes. Looks like I also need VS-2010 SP1. Now I know where those are ... in the same backup as VS-2008 (perhaps I'm not as stupid as I look!)
VS-2010 refuses to install ... oh yes, some idiot installed VS-2015 first ... right uninstall VS-2015 …
VS-2010 now installs, and SP1 slips over it easily. Let's see if we can compile the unmodded DLL with VS-2010 (using the 2010 solution) ... YES!!!
Feeling brave, I re-install VS-2015 (you've already guessed this is going to be a mistake, haven't you)
DLL-VMC compiles

Let's start ModBuddy. Damn, got carried away and forgot the VS-2010 Isolated Shell (which was how I started this wild goose chase!).
Damn! $#*^!!! Won't install. Ooops ... sheepishly ... I installed VS-2015 didn't I …
Uninstall VS-2015 (why does this take so long?), install VS-2010 Isolated Shell. ModBuddy still won't start, something about different patch versions ... reapply VS-2010 SP1.
Oh yeah! Cooking with gas! ModBuddy starts (can't remember exactly what the directories need to be set to, but I can copy those from my old setup later).
Reinstall VS-2015 (third time lucky?) Hoo b****y ray! DLL-VMC still compiles and ModBuddy still works.
So ... I could just stop here, but where's the fun in that? I want VS-2019!
And anybody who guessed that that was going to be another epic just lost

VS-2019 downloads and installs first time. So I start it up, open the DLL-VMC 2015 solution file (do NOT OK the dialog that prompts to udate the project, just Cancel it), and it compiles without problem. I'm amazed, I was expecting serious pain!
Now all I have to do is find the time to start modding again.
William
In summary, to build a DLL based mod on a new Windows 10 machine
* Install VS-2008
* Install VS-2010
* Install VS-2010 Isolated Shell
* Install VS-2010 SP1
* Download the Civ V SDK and start ModBuddy from the Steam SDK Menu (to complete the installation)
* Install VS-2015 (optional)
* Install VS-2019
* Open the DLL source and compile it, when prompted to update the project, do NOT click OK, just Cancel
* Start ModBuddy by double-clicking the .exe file
* Start modding

Last edited: