Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with StorageQueue in 4.0.56-beta4 #155

Open
jeckyl2010 opened this issue May 1, 2020 · 2 comments
Open

Problems with StorageQueue in 4.0.56-beta4 #155

jeckyl2010 opened this issue May 1, 2020 · 2 comments

Comments

@jeckyl2010
Copy link

Hi.

I have just updated from 4.0.45-beta4 to 4.0.56-beta4 and are running into some compiler errors afterwards on a project running .NET Core 3.1.1

The compiler error is

C:\Users\vaxh\.nuget\packages\functionmonkey.compiler\4.0.56-beta.4\build\netstandard1.0\FunctionMonkey.Compiler.targets(29,5): error : Error compiling function: HttpAlteryxJobExecutionEventPost.cs(36,144): error CS0234: The type or namespace name 'CloudQueueMessage' does not exist in the namespace 'Microsoft.WindowsAzure.Storage.Queue' (are you missing an assembly reference?) [C:\Temp\Git\AzureFunction\Novo.Azure.Function.Ada\src\Novo.Azure.Function.Ada.Function\Novo.Azure.Function.Ada.Function.csproj] C:\Users\vaxh\.nuget\packages\functionmonkey.compiler\4.0.56-beta.4\build\netstandard1.0\FunctionMonkey.Compiler.targets(29,5): error : Error compiling function: HttpAlteryxJobExecutionEventPost.cs(208,71): error CS0234: The type or namespace name 'CloudQueueMessage' does not exist in the namespace 'Microsoft.WindowsAzure.Storage.Queue' (are you missing an assembly reference?) [C:\Temp\Git\AzureFunction\Novo.Azure.Function.Ada\src\Novo.Azure.Function.Ada.Function\Novo.Azure.Function.Ada.Function.csproj]

The code I'm trying to compile looks a bit like this

Functions(functions => functions.HttpRoute(alteryxJobCompletedRoute, route => route.HttpFunction<AlteryxJobExecutionEventGetCommand>("/{jobname}", HttpMethod.Get). HttpFunction<AlteryxJobExecutionEventPostCommand>(HttpMethod.Post). OutputTo.StorageQueue("alteryxJobStorageQueueName")));

These are some of the nuget packages I have referenced in the project

<PackageReference Include="FunctionMonkey" Version="4.0.56-beta.4" /> <PackageReference Include="FunctionMonkey.Compiler" Version="4.0.56-beta.4" /> <PackageReference Include="FunctionMonkey.FluentValidation" Version="4.0.56-beta.4" /> <PackageReference Include="Microsoft.Azure.Functions.Extensions" Version="1.0.0" /> <PackageReference Include="Microsoft.Azure.ServiceBus" Version="4.1.3" /> <PackageReference Include="Microsoft.Azure.Storage.Common" Version="11.1.4" /> <PackageReference Include="Microsoft.Azure.Storage.Queue" Version="11.1.4" />

I have also tried to update to latest .NET Core version (3.1.3) but with the same result.

I have tried to run dotnet build --force but with same results.

Any idea on what I might be doing wrong.

/Anders

@inuvano-labs
Copy link

@jeckyl2010 did you ever find out what the issue was? I've recently started using this project and first time I introduced OutputTo.StorageQueue I'm getting the same compiler exception as you.

I had a quick look at the compiler source code, and I can see BuildCandidateReferenceList (

protected override IReadOnlyCollection<string> BuildCandidateReferenceList(
) that it doesn't appear to include a reference to the Microsoft.WindowsAzure.Storage assembly in the list - so this could possibly be the problem.

@jeckyl2010
Copy link
Author

@inuvano-labs Unfortunately this excellent package is more or less out-of-maintenance, so I'm no longer using it. I have taken some of the principles and carried over into my own code, but my code is very limited and only suiting me needs.

As things progresses rapidly on .NET Core 3, 5 & 6 - it will not be long before this package is too high a risk to use in corporate code, if not someone take over the gauntlet :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants