Microsoft Azure Functions Nuget Package Prevent NET Library From Packing Into A Nuget

Question

I have a NET Library project that targets net462 that includes a Microsoft.NET.SDK.Functions Nuget package. Problem is that when I pack my project into a Nuget library, it all succeeds (clean,restore,build,pack) except no .nupkg is created. If I comment out relevant code and get rid of the Nuget reference, a nupkg file is produced when I pack it.

I seem to be hitting this issue: IN GITHUB maybe?

The package in question - https://www.nuget.org/packages/Microsoft.NET.Sdk.Functions

My direct question is - Is this a possible feature? Can you prevent your packages from being packed into Nugets? How would I know. Or in any other words, is this situation (the one described in the GitHub issue) even possible? What could be going wrong? Thanks!

Can you please provide your use case? Why would you pack azure function to nuget ? — Vova Bilyachat, Jan 08 '19 at 01:55
Can you detail the step to reproduce, starting from scratch? — Simon Mourier, Jan 08 '19 at 09:11
@VolodymyrBilyachat I am writing a library to generate swagger for Http triggered function apps. So I must include the Functions library. The code needs a bunch of the references to inspect functions to generate Swagger. — jn1kk, Jan 08 '19 at 14:35

score 1 · Answer 1 · answered Sep 14 '21 at 18:56

I just ran into this same problem where dotnet pack was not producing packages for .csproj files that use the Microsoft.Functions.SDK package.

dotnet pack allows you to provide MSBuild parameters that are respected, even if it doesn't occur in their docs, so you can force a nuget package to be generated by doing something like this on the command line:

dotnet pack --configuration Release -property:IsPackable=true

The functions SDK appears to have some code in it I've not spent the time to track down that forces that IsPackable flag to false, regardless of the value in the .csproj.

If you're struggling with these things in the future, you can look at the diagnostics of the dotnet command by appending -v=d (setting Verbosity to Debug) to your command line commands.

I appreciate this is thread necromancy, but y'know, it's where I landed when looking :) — DavidWhitney, Sep 14 '21 at 18:56

Mohamed Elrashid · Answer 2 · 2019-01-09T06:20:45.807

Step 1 :open the project folder

Step 2 : open cmd

Step 5 : you should see a cmd that point to your project not solution directory

Step 6 : copy and past the flowing commands

    PowerShell -Command "Get-ChildItem $dir | Where { $_.Name -match '.csproj'} | Select -Expand Name | out-file -encoding ASCII projectname"

    SET /p projectname=<projectname

    PowerShell -Command "(Get-Content -path ..\packages\Microsoft.NET.Sdk.Functions.1.0.24\build\netstandard1.0\Microsoft.NET.Sdk.Functions.Build.targets -Raw) -replace 'DependsOnTargets="""RunResolvePublishAssemblies"""', '' | Set-Content -Path  ..\packages\Microsoft.NET.Sdk.Functions.1.0.24\build\netstandard1.0\Microsoft.NET.Sdk.Functions.Build.targets"

    SET MSBuild_PATH=C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin

    SET PATH=%MSBuild_PATH%;%PATH%

    MSbuild %projectname% /t:Clean;Rebuild /p:Configuration=Release

    PowerShell -Command "Get-ChildItem -Path .\bin\Release\bin -Recurse | Copy-Item -Destination .\bin\Release "

    PowerShell -Command "if(!(Test-Path -Path 'nuget.exe')){(new-object System.Net.WebClient).DownloadFile('https://dist.nuget.org/win-x86-commandline/latest/nuget.exe','nuget.exe')}"

    NuGet.exe pack %projectname% -Prop Configuration=Release -MSBuildPath "%MSBuild_PATH%"

    start .

Step 7 : you should find your nupkg file

Note : i used vs 2017 with flowing steps

create a new project

install Microsoft.NET.Sdk.Functions

This is not a correct answer. Didn't wanna waste the bounty. — jn1kk, Jan 15 '19 at 19:49