# AAX plugin category

**URL:** <https://forum.juce.com/t/aax-plugin-category/25013>\
**Category:** General JUCE discussion\
**Created:** [November 6, 2017, 8:28pm UTC](https://forum.juce.com/t/aax-plugin-category/25013 "2017-11-06T20:28:39Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [November 16, 2017, 2:54pm UTC](https://forum.juce.com/t/aax-plugin-category/25013/6 "2017-11-16T14:54:34Z")

</div>

You also need to compile the AAX library - there’s a Visual Studio 2013 project in the SDK that you can use to do this.

See this thread:

> [@Compile AAX Library on Visual Studio 2017](https://forum.juce.com/t/compile-aax-library-on-visual-studio-2017/22171):
>
> I know this is a known issue but I can’t find any good comprehensive forum posts (even on the Avid Pro Audio forum) regarding this. It looks like Avid only supplies VS files up to the 2013 version. I’m going to try loading the solution in VS 2017 & change some of the settings around to get the C runtime libs and such matching. Anybody have any advice or resources to tested VS 2015/2017 solutions? In the meantime I’ll report back here.

---

_[View the full topic](https://forum.juce.com/t/aax-plugin-category/25013)._