So it seems to me that the condition you suggested on the msbuild extension pack *.tasks file should do the trick, no?
If the package was not downloaded yet, you avoid importing a non existent file (using not yet defined tasks in various targets should not be a problem until you actually build the solution).
Then, when the package is downloaded, all should come into place and work just fine.
I'm guessing that in automatic builds you will use nuget cmdline to invoke package restore?
If the package was not downloaded yet, you avoid importing a non existent file (using not yet defined tasks in various targets should not be a problem until you actually build the solution).
Then, when the package is downloaded, all should come into place and work just fine.
I'm guessing that in automatic builds you will use nuget cmdline to invoke package restore?