The Build Worker
BimlExpress for Visual Studio Code runs your builds in one build worker that is the same for every platform. What the build worker can do is a property of your computer and never of a setting.
What Runs Where
On Windows, the build worker opens OLE DB providers, applies DPAPI protection levels, and compiles Script Tasks and Script Components.
On macOS and Linux, a build that needs OLE DB providers, DPAPI protection levels or Script Task and Script Component compilation says that it needs the Windows build worker. Use an ADO.NET or ODBC connection in place of OLE DB, or build on a Windows computer.
Bitness
Build Worker: Bitness (bimlexpress.buildWorker.bitness) chooses the x64 or the x86 build worker to match the bitness of your installed OLE DB providers and Integration Services assemblies. The default is x64, which 64-bit-only OLE DB providers need. The other value is x86, which 32-bit-only OLE DB providers need.
On Windows, BimlExpress launches the build worker through the .NET host of the bitness you choose: Program Files\dotnet for x64 and Program Files (x86)\dotnet for x86. The .NET runtime of that bitness must be installed on your computer. If it is not, BimlExpress shows a download link. A change to the setting takes effect at the next build, with no window reload.
The x86 build worker runs on Windows only, since no x86 .NET runtime exists on macOS or Linux. On macOS and Linux, the architecture of your computer picks the build worker.
Select Build Worker Flavor
The Select Build Worker Flavor command in the Command Palette lists the x64 and x86 build workers with their availability on your computer:
- active: the .NET runtime of that bitness is installed.
- install runtime: the .NET runtime of that bitness is missing.
- not viable on this OS: the build worker cannot run on your operating system, which is the case for x86 on macOS and Linux. Choosing it shows a warning and changes nothing.
BimlExpress writes your choice as a User setting, so it stays with your computer. The next build reads it with no window reload.
Dotnet Host Override
Build Worker: Dotnet Host Override (bimlexpress.buildWorker.dotnetHostOverride) is an advanced setting. It takes the absolute path to a specific dotnet host, for when your .NET installation is in a non-standard location and the automatic discovery cannot find it. It is empty by default.
Script Tasks and Script Components
The Windows build worker compiles Script Tasks and Script Components on your computer, in process, against two sets of Microsoft assemblies that it reads in place. BimlExpress installs neither set.
- The .NET Framework reference assemblies for the target framework version of the script project: v4.0 for SQL Server Integration Services (SSIS) 2012 and 2014, v4.5 for SSIS 2016 to 2019, and v4.7.2 for SSIS 2022 and later. The .NET Framework 4.8 runtime satisfies this, as does a .NET Framework targeting pack for that version. A script project that targets a framework version below 4 needs the .NET Framework 3.5 feature of Windows turned on.
- The SSIS assemblies of the SSIS version you target, read from the .NET global assembly cache, the SQL Server SDK folder or the Visual Studio Integration Services folders.
Three Microsoft installs place the SSIS assemblies, each with its own range of SSIS versions. Match the install to the SSIS version you target and to the bitness of the build worker.
| Install | Where to get it | SSIS versions |
|---|---|---|
| SQL Server setup with the Integration Services and Client Tools SDK features selected | SQL Server downloads, with the SQL Server 2025 Standard Developer edition installer and the SQL Server 2025 Enterprise Developer edition installer. The SQL Server 2022 Evaluation installer is on the Evaluation Center. Install Integration Services describes the feature selection. | The SQL Server version installed. Integration Services is not part of the Express edition. |
| SQL Server Data Tools | Download SQL Server Data Tools routes each Visual Studio version. The SSDT for Visual Studio 2017 standalone installer is on the previous releases page. | Visual Studio 2017: SQL Server 2012 to 2019. Visual Studio 2019 and later install the Integration Services projects extension below. |
| SQL Server Integration Services Projects extension for Visual Studio | SQL Server Integration Services Projects 2022+ for Visual Studio 2022 and 2026, and SQL Server Integration Services Projects for Visual Studio 2019. The Download button on each page starts the installer. | 2022+: SQL Server 2017 to 2025, 64-bit only. Visual Studio 2019: SQL Server 2012 to 2022. |
When an assembly is missing, the build reports one Error against the task or component. The Error names the missing assembly and the install that places it, and a line naming the build worker that ran follows it. For a missing SSIS assembly, the Error links the installs. For a missing .NET Framework reference assembly, it names the .NET Framework 4.8 runtime or the targeting pack for the framework version of the script. Install what is missing, then build.
The build worker never downloads, copies or bundles a Microsoft assembly.