Build Acceleration in VS 17.5

[drewnoakes]

Now that VS 17.5 is available, it's a great time to try out Build Acceleration in your solution.

Build Acceleration is an opt-in feature that can significantly improve builds times, especially for large solutions.

For the following solutions we saw improvements of around 80%.

We've even had a report of a 98% reduction!

For more information about the feature, and instructions on how to opt-in, see https://aka.ms/vs-build-acceleration

If you have any questions or issues, feel free to comment here or open an issue on this repo's issue tracker.

⚠️ Take the Build Accleration survey!

[rodrigoporcionato]

I don't see the difference in my case. Maybe I do something wrong. I have more than 30 projects and run 4.8 framework. Do It should be working?

[MaceWindu]

Enabled verbose logging and tested linq2db/linq2db#3989 build with both enabled and disabled option and don't see any difference and any mention of accel substring in build logs

[MaceWindu]

But works with another solution
Visual Studio accelerated 18 project(s), copying 45 file(s)

[drewnoakes]

@MaceWindu I pulled down your linq2db PR to try it locally. You're hitting an issue called out in the docs around ProduceReferenceAssembly. In 17.6, building your PR produces messages like this:

FastUpToDate: This project has enabled build acceleration, but at least one referenced project does not produce reference assemblies. Ensure all referenced projects, both direct and indirect, have the 'ProduceReferenceAssembly' MSBuild property set to 'true'. See https://aka.ms/vs-build-acceleration.

It would be a lot more helpful if we included the name of the offending project(s). I filed #8880 to track this.

Adding this property to your projects gets build acceleration working:

Build started...
1>FastUpToDate: Input Compile item 'C:\dev\linq2db\Source\LinqToDB\DataContext.cs' is newer (2023-02-28 19:38:26.226) than earliest output 'C:\dev\linq2db\Source\LinqToDB\bin\Debug\net46\linq2db.xml' (2023-02-28 19:38:11.253), not up-to-date. (LinqToDB)
1>------ Build started: Project: LinqToDB, Configuration: Debug Any CPU ------
1>LinqToDB -> C:\dev\linq2db\Source\LinqToDB\bin\Debug\net46\linq2db.dll
1>LinqToDB -> C:\dev\linq2db\Source\LinqToDB\bin\Debug\net472\linq2db.dll
1>LinqToDB -> C:\dev\linq2db\Source\LinqToDB\bin\Debug\netstandard2.0\linq2db.dll
1>LinqToDB -> C:\dev\linq2db\Source\LinqToDB\bin\Debug\netcoreapp3.1\linq2db.dll
1>LinqToDB -> C:\dev\linq2db\Source\LinqToDB\bin\Debug\net7.0\linq2db.dll
1>LinqToDB -> C:\dev\linq2db\Source\LinqToDB\bin\Debug\netstandard2.1\linq2db.dll
1>LinqToDB -> C:\dev\linq2db\Source\LinqToDB\bin\Debug\net6.0\linq2db.dll
========== Build: 1 succeeded, 0 failed, 13 up-to-date, 0 skipped ==========
========== Build started at 7:38 PM and took 14.590 seconds ==========
Visual Studio accelerated 13 project(s), copying 213 file(s). See https://aka.ms/vs-build-acceleration.

I'll comment on your PR with the details of what's I had to add.

[MaceWindu]

Thanks! Strange I wasn't able to find this message in build logs, maybe did something wrong

[drewnoakes]

No, you didn't do anything wrong. The message is not in 17.5. It's something we're adding in 17.6 based on feedback such as yours.

[mstv]

How to reset the Build Acceleration cache?

[drewnoakes]

There isn't such a cache for build acceleration. What is the scenario you're trying to address?

[mstv]

I want to trigger a clean full rebuild. Where are the cached build artifacts stored?

[drewnoakes]

I want to trigger a clean full rebuild.

Does rebuild do what you want? If not, can you open an issue with more details so we can investigate?

Where are the cached build artifacts stored?

Everything's in the obj and bin folders.

[mstv]

Thank you for the clarification. I got confused by the "restored" messages on rebuild - like:

Restored D:\Build\gitextensions3_dev\GitCommands\GitCommands.csproj (in 41 ms).

[govert]

The default setting for build acceleration changed in VS 17.9, causing us some trouble, as I explain here: #9106 (comment)