This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
Version 2 NSGFlowLogTuple Schema broke build during Functions Deploy #3
Comments
|
Hi @dxlusby. If you install from the 'refactorOutputs' branch, this problem is fixed. I'll merge the branch into master once there is more testing. Care to contribute? |
|
Version 2 is merged. |
arledesma
pushed a commit
to arledesma/AzureNetworkWatcherNSGFlowLogsConnector
that referenced
this issue
Jun 3, 2020
…sionUpdated MW-366 Library versions are updated
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would appear that the addition of the version parameter in the August changes causes the project build to fail.
Using shared compilation with compiler from directory: D:\Program Files (x86)\MSBuild-15.3.409.57025\MSBuild\15.0\Bin\Roslyn
Stage1BlobTrigger.cs(50,20): warning CS0168: The variable 'msg' is declared but never used [D:\home\site\repository\NwNsgProject\NwNsgProject.csproj]
Stage3QueueTrigger.cs(484,45): error CS7036: There is no argument given that corresponds to the required formal parameter 'version' of 'NSGFlowLogTuple.NSGFlowLogTuple(string, float)' [D:\home\site\repository\NwNsgProject\NwNsgProject.csproj]
Done Building Project "D:\home\site\repository\NwNsgProject\NwNsgProject.csproj" (default targets) -- FAILED.
The text was updated successfully, but these errors were encountered: