# juce\_VST\_wrapper.cpp no longer compiles with VS 2010

**URL:** <https://forum.juce.com/t/juce-vst-wrapper-cpp-no-longer-compiles-with-vs-2010/21586>\
**Category:** Audio Plugins\
**Created:** [March 31, 2017, 8:13am UTC](https://forum.juce.com/t/juce-vst-wrapper-cpp-no-longer-compiles-with-vs-2010/21586 "2017-03-31T08:13:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ans](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ans/32/617_2.png) [@ans](https://forum.juce.com/u/ans)\
**Post date:** [March 31, 2017, 8:13am UTC](https://forum.juce.com/t/juce-vst-wrapper-cpp-no-longer-compiles-with-vs-2010/21586/1 "2017-03-31T08:13:57Z")

</div>

As of Juce 4.3.1, juce\_VST\_wrapper.cpp no longer compiles with VS 2010. Looks like the for loop syntax in findMaxTotalChannels() isn’t supported:

```
    for (auto& config : configs)
    {
        maxTotalIns = jmax (maxTotalIns, config[0]);
        maxTotalOuts = jmax (maxTotalOuts, config[1]);
    }

```

I see how sexy this is, but until VS 2010 support is eventually dropped, this should still use the conventional for loop syntax.

---

<div class="post-metadata">

**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\
**Post date:** [March 31, 2017, 8:18am UTC](https://forum.juce.com/t/juce-vst-wrapper-cpp-no-longer-compiles-with-vs-2010/21586/2 "2017-03-31T08:18:55Z")

</div>

The recent introduction of some more modern C++ features into JUCE means that only VS2013 and later are supported.

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [March 31, 2017, 8:19am UTC](https://forum.juce.com/t/juce-vst-wrapper-cpp-no-longer-compiles-with-vs-2010/21586/3 "2017-03-31T08:19:06Z")

</div>

It’s time to upgrade! We’re in the process of dropping vs2010, and requiring vs2013 or later for all our code.

---

<div class="post-metadata">

**Author:** ![ans](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ans/32/617_2.png) [@ans](https://forum.juce.com/u/ans)\
**Post date:** [March 31, 2017, 8:53am UTC](https://forum.juce.com/t/juce-vst-wrapper-cpp-no-longer-compiles-with-vs-2010/21586/4 "2017-03-31T08:53:55Z")

</div>

Ah ok, I knew this was eventually inevitable.

Upgrading a toolset means days of stressful hassle, endless googling and a cascade of unforseen side effects, broken build scripts and random incompatibilites, so I always postpone it as long as possible. Already tried the move to VS 2015, but failed and gave up on it. No country for old men.