Just a fast feedback on my experience with Azure Functions using net core 3.0
I was feeling quite lazy about installing another preview of visual studio 2019, so i kept using my current version (16.3.8).
My main prerequisite was to install the latest version of the azure function preview tools (i did it on powershell).
How i got using my azure function .net core 3.0 (with net standard library 2.1 ?).
1/ Creating azure function with vs 2019 (non preview)
2/ change in csproj AzureFunctionsVersion from v2 to v3
3/ update Microsoft.NET.Sdk.Functions to 1.0.30-beta2 (the 3.xxx does not work for me).
Each time i tried to debug with vs, i got a crash.
4/ Then, tried to start my project with command lines ( func start --build )
5/ Every thing goes well locally and when deployed to azure
On Azure portal, I only had to activate the runtime preview (v3). nothing else.
As you can not debug with my solution, you will have to use efficiently logging (everyone is supposed to do it right ;p).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey,
Just a fast feedback on my experience with Azure Functions using net core 3.0
I was feeling quite lazy about installing another preview of visual studio 2019, so i kept using my current version (16.3.8).
My main prerequisite was to install the latest version of the azure function preview tools (i did it on powershell).
How i got using my azure function .net core 3.0 (with net standard library 2.1 ?).
1/ Creating azure function with vs 2019 (non preview)
2/ change in csproj AzureFunctionsVersion from v2 to v3
3/ update Microsoft.NET.Sdk.Functions to 1.0.30-beta2 (the 3.xxx does not work for me).
Each time i tried to debug with vs, i got a crash.
4/ Then, tried to start my project with command lines ( func start --build )
5/ Every thing goes well locally and when deployed to azure
On Azure portal, I only had to activate the runtime preview (v3). nothing else.
As you can not debug with my solution, you will have to use efficiently logging (everyone is supposed to do it right ;p).