Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 1.17.0 breaks solution builds using no-incremental #2284

Closed
skystedt opened this issue Feb 13, 2024 · 11 comments
Closed

Version 1.17.0 breaks solution builds using no-incremental #2284

skystedt opened this issue Feb 13, 2024 · 11 comments
Labels
bug Something isn't working Needs: Attention 👋

Comments

@skystedt
Copy link

Description

Building a solution with flag --no-incremental while having a test project referencing a functions project will result in the build failing with
MSB3030: Could not copy the file "obj\Debug\net8.0\extensions.json" because it was not found.

Using Microsoft.Azure.Functions.Worker.Sdk 1.16.4 => works
Using Microsoft.Azure.Functions.Worker.Sdk 1.17.0 => does not work

Building without any flags => works
Building with --no-incremental => does not work.

Building each individual project => works
Building the solution => does not work

Steps to reproduce

  1. Create a solution with a new functions project
    • Functions worker: .NET 8.0 Isolated
    • Function: Empty
  2. Add a xunit test project
  3. Add a project reference in the test project targeting the functions project
  4. Use Microsoft.Azure.Functions.Worker.Sdk 1.17.0
  5. build with: dotnet build --no-incremental solution.sln
@jeromekol
Copy link

same issue here

@skystedt
Copy link
Author

Still broken in Microsoft.Azure.Functions.Worker.Sdk 1.17.1

@kshyju
Copy link
Member

kshyju commented Mar 1, 2024

Thanks for reporting the issue @skystedt . We released a new version of Microsoft.Azure.Functions.Worker.Sdk package which includes a fix for this issue. Could you please upgrade to that version?

https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Sdk/1.17.2

@skystedt
Copy link
Author

skystedt commented Mar 2, 2024

The new version solves the issue.
Thanks!

@robmaas
Copy link

robmaas commented Sep 25, 2024

@kshyju This was working in 1.17.2 but is broken again in versions 1.17.3 and 1.17.4.

@pregress
Copy link

1.18 also broken. Similar issue as: #2722

Would be nice If they would finally create a test case for this instead of just breaking every possible build.

@robmaas
Copy link

robmaas commented Nov 21, 2024

Still broken in 2.0.0

@pregress
Copy link

Still broken in 2.0.0

Following pull request should fix it: #2763

@jmaczan
Copy link

jmaczan commented Dec 11, 2024

Is there any known workaround for 2.0.0, where it is still broken?

@pregress
Copy link

Is there any known workaround for 2.0.0, where it is still broken?

You can pass -m:1 to your dotnet publish / dotnet build

https://learn.microsoft.com/en-us/visualstudio/msbuild/msbuild-command-line-reference?view=vs-2022#switches

@jmaczan
Copy link

jmaczan commented Jan 10, 2025

@pregress Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Needs: Attention 👋
Projects
None yet
Development

No branches or pull requests

6 participants