You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should expose and document the func pack command (as suggested here by Ahmed), since it's useful for creating deployment packages manually outside of a deployment process. This is beneficial when creating one-off remote deployment package to enable run from package URI scenarios and during testing.
However, currently func pack won't run on C# in-process projects because of this check that includes ignoreDotNetCheck. The func azure functionapp publish path works correctly because ignoreDotNetCheck is set to true, but not in func pack.
Interestingly, func pack seems to work fine for C# isolated projects, because the C# check is only on WorkerRuntime.dotnet.
We should also unblock func pack for C# in-process apps.
We should expose and document the
func pack
command (as suggested here by Ahmed), since it's useful for creating deployment packages manually outside of a deployment process. This is beneficial when creating one-off remote deployment package to enable run from package URI scenarios and during testing.However, currently
func pack
won't run on C# in-process projects because of this check that includesignoreDotNetCheck
. Thefunc azure functionapp publish
path works correctly becauseignoreDotNetCheck
is set to true, but not infunc pack
.Interestingly,
func pack
seems to work fine for C# isolated projects, because the C# check is only onWorkerRuntime.dotnet
.We should also unblock
func pack
for C# in-process apps.+ @mattchenderson for awareness.
The text was updated successfully, but these errors were encountered: