-
Notifications
You must be signed in to change notification settings - Fork 186
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
Refactor SDK targets to improve incremental build, publish issues, and nuget feed issues #1946
Conversation
# Conflicts: # DotNetWorker.sln # extensions/Worker.Extensions.Tables/src/TableExtensionStartup.cs # extensions/Worker.Extensions.Tables/src/Worker.Extensions.Tables.csproj # samples/WorkerBindingSamples/WorkerBindingSamples.csproj # test/E2ETests/E2EApps/E2EApp/Table/TableInputBindingFunctions.cs # test/E2ETests/E2ETests/Tables/TablesEndToEndTests.cs # test/SdkE2ETests/Contents/WorkerBindingSamplesOutput/functions.metadata # test/SdkE2ETests/PublishTests.cs
Merge main into feature/ext-proj
Merge main into feature/ext-proj
* Expand on RemoveProperties for inner build. Fix source gen default * Add PublishProfile to remove props * Un-remove some properties from inner build
Hi, we are currently facing the issues fixed by this PR. Is there any information when the fix will be shipped? |
@jviau @kshyju Hey, even though the changes have been approved, there still seem to be checks pending. Do you have a chance to take a look and merge the changes? Unfortunately the fix did not make it into the release from 4 days ago and we are still not able to migrate to .NET 8. When will the next release be? Can you provide a release in the short term to unblock us and many others? |
Merge main into feature/ext-proj
We've been having an issue on our build server where the C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp folder gets filled up with the WorkerExtensions.csproj and buildout artifacts. (about 94 mb each build). Will this change move these files into the standard build directories instead of that temp folder? I'm curious if updating our Microsoft.Azure.Functions.Worker.Sdk package to this version will resolve this issue. |
@WakaToa A preview version of the package is now available. https://github.com/Azure/azure-functions-dotnet-worker/releases/tag/sdk-1.17.0-preview1 |
* Revert "Reverting changes introduced in #1946 (#2313)" (#2346) This reverts commit c34a868. * Directly use ReferencePath for scanning reference assemblies * update release_notes.md * Update log message * Add e2e test to verify SDK assembly scanning * Include nuget.org for test * Pass https source first * Add package with no restore * Refactor Sdk e2e build steps * Remove --no-restore
Issue describing the changes in this PR
resolves #1863, #1834
Pull request checklist
release_notes.md
Additional information
This PR refactors our SDK targets to improve the inner-build stability and quality. The inner build is used to collect functions host extension payload to be deployed with the application. The changes are:
WorkerExtensions.csproj
is now generated and build in the intermediate output directory under a set pathCopyToOutputDirectory
andCopyToPublishDirectory
targets from the base .NET SDK will perform the copies for us.