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
Restoring C:\git\bug-free-sniffle\apitest\WeatherForecastFunction1.cs:
C:\git\bug-free-sniffle\apitest\WeatherForecastFunction1.cs(1,1): error MSB4025: The project file could not be loaded. Data at the root level is invalid.
Line 1, position 1.
Restore failed.
Post action failed.
It appears that it is the result of the template picking up the primaryOutputspath during Nuget restore according to lines 67-72 in the template.json.
{
"description": "Restore NuGet packages required by this project.",
"manualInstructions": [],
"actionId": "210D431B-A78B-4D2F-B762-4ED3E3EA9025",
"continueOnError": true
},
It should be picking up the project file. A quick scan of the other dotnet isolated templates show the same pattern of code.
The error messages appear to be superfluous when running from Azure Functions Core Tools but does raise concerns for newer users. According to Post Actions Registry, I believe it may be resovable by adding an args configuration.
The text was updated successfully, but these errors were encountered:
oneolddev
changed the title
HttpTrigger-CSharp-Isolated Restore Failed and Post Action Failed
HttpTrigger-CSharp-Isolated displays 'Restore Failed and Post Action Failed' after successful creation
Apr 11, 2023
This issue was uncovered originally in Azure Functions Core Tools when creating an isolated c# function. Please see the following: Azure/azure-functions-core-tools#3217 (comment).
It appears that it is the result of the template picking up the primaryOutputs path during Nuget restore according to lines 67-72 in the template.json.
It should be picking up the project file. A quick scan of the other dotnet isolated templates show the same pattern of code.
The error messages appear to be superfluous when running from Azure Functions Core Tools but does raise concerns for newer users. According to Post Actions Registry, I believe it may be resovable by adding an args configuration.
The text was updated successfully, but these errors were encountered: