I’ve learned this from the project Busmaster (http://www.etas.com/de/products/applications_open_source.php) , a hidden open source gem dealing with CAN communication. I originally just wanted to fix an internationalization issue (. / , as decimal sign – classic atof problem) , but I’ve learned so much from this project about CAN communication and using #include<vector>, and want to point this out for you.
They also have a really good documentation for their toolchain setup, and there’s something that both amazed and fascinated me: You can definitely use VS Express with ATL and MFC. You just need to figure out how.
(This is an extract / translation from the documents here: https://github.com/rbei-etas/busmaster/tree/master/Documents) – look for BUSMASTER OSS – Development Environment.doc
(As a clarification, I’m using the Professional Edition at work, which is far more sensible – I just need MFC/ATL to play).
I’m using VS2008. I dislike 2010, because it’s impossible to get global properties for libraries, paths,… I understand that decision, and it’s absolutely correct and okay, but personally, it’s annoying.
Okay for solutions with 3 projects, terrible for solutions with 30 projects.
You can’t directly download 2008 any more, but there are enough „deep“ links to get it. Just google, or try this one:
First, install Windows SDK. / Platform SDK. It won’t help, but you’ll need it to compile most things.
VS express doesn’t have ATL.
But Windows Driver Development Kit has. http://www.microsoft.com/en-us/download/details.aspx?id=11800
Download, mount the ISO, install.
(Don’t do this for any public or commercial projects. Read the licences. It’s not allowed!)
This was never meant for you to develop directly with, so you need to patch those versions. For this, they are using git-diffs.
If you don’t have git:
Git for Windows : http://code.google.com/p/msysgit/downloads/list
Git Extensions http://code.google.com/p/gitextensions/
(If you are a Linux User, you probably won’t install Visual Studio. If you do, you don’t need this article.)
There are three files for patching this automatically: The git-patch, and two batch-scripts (for patching, and unpatching).
You need to adapt them for example if you use Win 64 bit:
“C:Program Files (x86)Gitbinpatch” -p1 -d C:/ < WinDDK_7600.16385.1.diff
The patch has to run successfully, else your paths are wrong.
Now open VS and Tools → Options:
(These are the magical global settings not found in VS2010!)
There are limits:
* no Resource-Editing
* release-version (no debugging)
* it’s ATL from VS6.0 (don’t use too modern stuff)