This would slow down the build process in larger sites and also, perhaps, lead to caching issues
Additional details
If this was unticked then the nuget package would not get automatically generated when Visual Studio builds:
You should only look to test the nuget package once you've finished testing via the test site, and want to test that the nuget install itself works. So probably makes sense to use a dotnet pack command for that at the appropriate time instead.
So when you are ready to generate the nuget package for local testing use the command line with something like
Feature summary
This would slow down the build process in larger sites and also, perhaps, lead to caching issues
Additional details
If this was unticked then the nuget package would not get automatically generated when Visual Studio builds:
You should only look to test the nuget package once you've finished testing via the test site, and want to test that the nuget install itself works. So probably makes sense to use a
dotnet packcommand for that at the appropriate time instead.So when you are ready to generate the nuget package for local testing use the command line with something like
dotnet pack --configuration Release /p:Version=1.0.0-rc001 --no-build --output