[4.0] Unable to deploy function app from standalone project
Grimeh opened this issue · 8 comments
Hi there!
UPDATE: this only happens when opening a standalone .csproj, creating a wrapper .sln allows you to successfully deploy a function app. This issue is specifically about the inability to deploy from a standalone .csproj.
After installing the 4.0 preview I cannot deploy our function app.
When creating a deploy configuration, the app settings are correctly pulled down, but I see Error: Choose a project platform at the bottom of the panel:
I have tried both:
Tools/Azure/Deploy to Azure Functions...right click -> Deployon a function app in the Azure Explorer
I was able to deploy to this target with 3.50.0 (though I ran into #861), and can deploy with VS Code's Azure extension.
Let me know if you'd like logs and I can provide them (I just didn't have the time today to comb through and redact confidential info sorry).
Hello! You should be able to see the values in that field, is there anything in it?:
Ah apologies, I should have specified that in the original post. The Configuration field has no values.
Perhaps you don't have any build configuration? What do you see in the configuration manager?
You can also check other Publish configurations if they have values in the Configuration combo box.
I'm not sure if it's because I'm not on the EAP (which your screenshots seem to be from), but I don't seem to have a dedicated configuration manager. I can see Debug & Release configurations in the project properties though, but they seem to be a different type of configuration.
As suggested, I checked another publish configuration and "Publish to folder" has the same problem.
So I noticed that our setup doesn't actually have a .sln, just a standalone .csproj.
Without a solution I suppose there aren't any solution configurations 😅
I will attempt to create a wrapper solution to see if that resolves the issue.
Is this an intentional restriction? Pre-4.0 doesn't require a solution, neither does VSC's plugin.
Creating a wrapper solution did indeed fix the issue (I can also see & edit solution configurations now).
I'll update the title & OP to reflect the info that it only happens when opening a standalone .csproj.
Thank you, fixed that
Legend, thanks!