dotnet / dotnet/vblang

VB.NET in Azure Functions

Open
#475 46 comments 3 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
328
Forks
71
PR merge metrics
No merged PRs in 30d

Description

FYI I was able to get a pure-VB.NET Azure Function working. It was pretty simple, really—here's what I did:

1. Created a C# sample using [this guidance](https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-your-first-function-visual-studio)
2. Created a new VB.NET project (in .NET Standard 2.0 instead of .NET Core 2.2—I ran into missing dependency problems while trying it in Core)
3. Converted the C# sample class using Telerik's [Code Converter](http://converter.telerik.com/)
4. Added the converted code to the VB.NET project (being careful to remove the redundant namespace declaration)
5. Per [this advice](https://stackoverflow.com/a/49790793/722393), added the `AzureFunctionsVersion` element to the VB.NET project's XML:


FunctionApp1
netstandard2.0
v2

6. Published and tested as normal

If you're using WebDeploy (uncheck the 'Run from package file' checkbox at first publish), you'll see a warning during deployment:

> Could not evaluate 'Microsoft.CSharp.dll' for extension metadata. Exception message: Could not load file or assembly 'Microsoft.CSharp, Version=4.0.4.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

This warning can be safely ignored. Best guess, the assembly is probably only necessary as an interpreter for C# Script functions.

Due to my limited bandwidth I can only publish via WebDeploy, so I'm not aware of whether the warning occurs during a ZipDeploy (checking the Package checkbox).

And there we have it—an Azure Function in pure VB.NET.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.