I'm having an issue creating the first project, I'm running Visual Studio 2017 Enterprise on Windows 10 64 bit and have it mapped in the RackAFX preferences.
When I create the projects it opens visual studio 2017 and opens the .vcxproj file but when I right click the first control in RackAFX it says "Compiler not alive/available yet"
If I then go and manually open the Visual Studio project file that was created it says it's unsupported and needs to be upgraded, when I click this option I;m then able to right click the controls in RackAFX and get the corresponding menu from the book but nothing opens up in Visual Studio and when I try to open the new version of the .sln it still says it's unsupported and it needs to be migrated.
Any ideas what could be causing the issue or is there another IDE I could use instead that would be easier to set up?
You do need to upgrade the VS2017 stuff. Did you see the big blurb on the RackAFX download page about this?
Microsoft have confirmed a bug in Visual Studio 2017 that I reported which involves using VS2017 on a computer that does not have VS2015 installed on it (or had VS2015 installed and then removed). When opening an older VS project, you get a message that states that the Target OS and ToolSet will be upgraded; after the upgrade, the Target OS will still be incorrectly set to Win8.1 – without the VS1015 installation files, this project will not compile. The same is true of book projects and new RackAFX projects which have no Target OS setting; instead of setting the new Target OS to Win10.0, it defaults back to Win8.1 and creates the same problem. Microsoft asks that we remain patient while they fix this… but in the meantime, you can work around the bug by manually retargeting old and new projects alike; in the Solution Explorer, right-click on the Solution and choose Retarget SDK Version, then choose 10.0.xxxx.y (there may be multiple versions – if so, choose the latest version).
BTW - Microsoft never fixed this issue.
Just started working on the synth book and I had the same issue, even when creating a new project, not just opening an old project. I had to go in and manually target the Windows 10 SDK, because it was putting in Windows 8.1 as the default. Not sure if this matters all that much, but just wanted to point out it did happen to me on a fresh VS2017 install initializing a new project, not just trying to open an old one.
As this is my first post on the forum, I also want to say a big thanks for having this great resource out there. I purchased both books and am enjoying working through them immensely.
Yes, this is *still* a bug, but it looks like Microsoft are moving to VS2019 (oh joy).
I think you are getting this with a "fresh" VS2017 because at some point, you had VS2015 installed (which installs the 8.1 SDK) or because you installed one of the Redistributables with RackAFX (which is compiled with VS2015).
RackAFX7 is around the corner now.
Most Users Ever Online: 55
Currently Browsing this Page:
Guest Posters: 1
Newest Members:Simple, Chris_1, manyu, AdamR, Stuart, Al Calabrese, frankthetank, dhodgson, Wanderer, mister1234
Moderators: W Pirkle: 352
Administrators: Tom: 71, JD Young: 80, Will Pirkle: 0, W Pirkle: 352