<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Building HISE plugins on Windows with non-Community version of Visual Studio]]></title><description><![CDATA[<p dir="auto">Is it possible to dynamically set the location of MsBuild when exporting a HISE plugin?</p>
<p dir="auto">I think the below path is hardcoded - so if you have Enterprise or Professional versions installed then the plugin build will fail.  (GitHub Action runners for example come with Enterprise Edition pre-installed).</p>
<pre><code>C:\Program Files\Microsoft Visual Studio\18\Community\MSBuild\Current\Bin\MsBuild.exe
</code></pre>
<p dir="auto">I also see some conflicting docs about always using Visual Studio 2017 or 2022 but it looks like VS Community 2026 is working.</p>
]]></description><link>https://forum.hise.audio/topic/14999/building-hise-plugins-on-windows-with-non-community-version-of-visual-studio</link><generator>RSS for Node</generator><lastBuildDate>Fri, 14 Aug 2026 07:04:03 GMT</lastBuildDate><atom:link href="https://forum.hise.audio/topic/14999.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 14 Aug 2026 03:42:05 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Building HISE plugins on Windows with non-Community version of Visual Studio on Fri, 14 Aug 2026 06:21:55 GMT]]></title><description><![CDATA[<p dir="auto">For anyone curious - it looks like you can get around this by linking the expected path to wherever you have Visual Studio installed</p>
<pre><code>mklink /D "C:\Program Files\Microsoft Visual Studio\18\Community" "C:\Program Files\Microsoft Visual Studio\18\Enterprise"
</code></pre>
]]></description><link>https://forum.hise.audio/post/122512</link><guid isPermaLink="true">https://forum.hise.audio/post/122512</guid><dc:creator><![CDATA[eschirle]]></dc:creator><pubDate>Fri, 14 Aug 2026 06:21:55 GMT</pubDate></item></channel></rss>