Migrate Azure Function app from .NET Core v2 to v3

For migrating an Azure Function app from .NET Core v2 to v3 follow the following steps
  1. Unload the Azure function project by right clicking the project and selecting unload.
  2. Change
      <propertygroup>
       <targetframework>netcoreapp2.2</targetframework>
       <azurefunctionsversion>v2</azurefunctionsversion>
      </propertygroup>
             

to
  <propertygroup>
    <targetframework>netcoreapp3.1</targetframework>
    <azurefunctionsversion>v3</azurefunctionsversion>
  </propertygroup>

  1. Reload the Azure function project by right clicking the unloaded project
  2. Update the Microsoft.NET.Sdk.Functions nuget package to version 3.0.2 or higher
  3. Update the Microsoft.Azure.WebJobs.Extensions (when installed) to version 4.0.0 or higher
  4. In the local.settings.json change the FUNCTIONS_EXTENSION_VERSION setting to "~3"
  5. When I for the first time tried to start the converted Azure function project I got the message "no Functions runtime available that matches the version specified in the project.". I fixed this by following these steps
    1. Close existing Visual studio projects / solutions
    2. Updating Visual Studio to the latest update
    3. Create a new Azure Function project
    4. By the template setting check if the .NET Core 3 framework option is there, if not check if you have a spinner below in the screen, wait a while. The spinner did not stop spinning, I cancelled the screen and retried and after that I could create a .NET Core 3 framework project. 
    5. Just create a default timer project.
    6. Close Visual studio and restart your converted Azure function project
Some errors that I found:
System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
File name: 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
Solution: Change in the project file azurefunctionsversion from v2 to v3

Comments

Post a Comment

Popular posts from this blog

System.Net.Http dll version problems

Last few weeks we had problems with referencing the correct System.Net.Http version. This is probably because some components use internally higher versions (.NET Core with System.Net.Http 4.2.0.0) compared to the versions that are available in NuGet. Frequently we got errors like: Could not load file or assembly 'System.Net.Http, Version=4.1.1.2, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) What is the solution.... That is a great questions. But we do not have the satisfying answer yet. What we currently do is the following. - Use in all projects the same System.Net.Http version, currently we use v4.3.3 from nugget - Compile the code and check in the resulting Bin folder what the resulting System.Net.Http version is - Use this version as BindingRedirect in the app.config / web.config like <dependentAssembly>
Read more

SharePoint Survey Back Button

On Internet I could not find a correct solution for implementing a back button in a survey. After some search I found some near implementations but not an implementation that fully worked. One that inspired me was http://sharepointbender.blogspot.nl/2012/04/creating-back-button-on-sharepoint-2010.html but I found the history.back(-2) not satisfying. I wrote my one version in Javascript that uses the FirstField parameter of the survey to implement a correct behaviour. I hope it makes you happy. In the edit form I added a script link to the code below and i added the following statement spbackButton.init("Name of list"); In an javascript file I included the following code. var spbackButton = (function () { var _prevFieldsArray = new Array(); var _currentStep; var _prevPageStep; function setCookie(c_name,value,exdays) { var exdate=new Date(); exdate.setDate(exdate.getDate() + exdays); var c
Read more

How to set up AD FS for a development machine

Image
In this article I will describe how you should set up a development computer to use an existing AD FS. First thing we need to do is to create a trust between the ADFS server and the development machine. You can do this by login in with RDP at the server that is running ADFS and start up the "AD FS 2.0 Management" that is found under the Administrative tools. When the AD FS 2.0 Management studio is started you need to navigate to the "Relying Party Trusts" in the left folder structure. Then you nee to select "Add Relying Party Trust..." in the right menu. This will open the "Add Relying Party Trust Wizard" as shown below. When clicked on "Start" the following screen will open. Here you can specify how the relying party configuration is configured. For a development machine it is most easy to select just the last option "Enter data about the relying party manually" In the next screen you can fill in a name and descr
Read more