Hey guys, i got some tips for you if you want to try debugging.
Now, if you want to debug the DLL while you're testing it in Civ4, you must be able to build a debug release instead of a final release. You can always try with the final release, but i'm not sure this will work since i'm always working in debug release (don't worry, it doesn't corrupt anything).
1- get your DLL compiling and be able to run it in Civ4. If you can't run Civ4 with the modified DLL, don't go farther. Get back into VS and make that DLL work.
2- Start Civ4 with the modified DLL.
3- Once Civ4 has finished loading, meaning waiting for you to make an action in the start-up menu, get back into VS.
4- In the menu bar, click on - Debug - then - Attach to process -
5- A window appears listing all processes (application) currently running on your computer.
6- Find the process Civilization4.exe (Vanilla) or Civilization4Warlords.exe (Warlords). For BtS, i have no idea, but it should look like Civilization4"Something".exe where something could be BtS or Beyond or anything else related to BtS. This name is decided by Firaxis btw.
7- Click - Ok - (or it may be - Attach -, i don't have VS installed at home for now)
8- You're now ready to use the debugger in VS 2005!
The two things that i see that could possibly make this procedure not work is:
1- Might not work with a final release. You'll have to test it, because i'm not sure.
2- You don't know how to use the debugger in VS. There should be some tutorial around the web.
I have not tried any of it since my computer got formated and I don't have the time to download all that is required, but it's the standard procedure if you want to debug any DLL that a program is using. I had to do that for my 2007 year project at school (no, not on Civ4).
I'll get the tools as soon as i can and test that myself, but until then you can always ask question here and i'll try to answer.