-
Notifications
You must be signed in to change notification settings - Fork 89
Error "Could not load file or assembly '/app/*.dll'." in attempt to deploy vb.net function #68
Comments
Hi @lorenzo-ange, I'm sorry to keep mentioning you. Since this is using dotnetcore 3.1 runtime and the error seems to be related to loading assembly which you have experience with (the last pull request of yours), maybe you have some insight and can give direction on where to look to fix this error? |
Hi @har07 , |
Hi @lorenzo-ange , thanks a lot for your suggestion. It get rid of the assembly loading error. Now I got this new error:
If I understand this correctly, |
@har07 I never tested the runtime with VB functions, but I'm really happy that, with your help, we can check why it doesn't work. It seems the runtime cannot load correctly your function code. Can you please try deploy with these explicit env vars: |
@lorenzo-ange I just tried deploying with those env vars. Unfortunately, the error didn't change. I also tried using different module name like 'vbmodule' since 'module' is a keyword in vb, but still got the same error.:
|
Hi @har07 , Imports System
Imports Kubeless.Functions
Public Class [module]
Public Async Function handler(ByVal k8Event As [Event], ByVal k8Context As Context) As Task(Of Object)
Return "Happy coding!"
End Function
End Class |
@har07 any news on this? did you manage to run succesfully the function? |
Hi @lorenzo-ange , I am sorry for the very long wait. The development server that I use for experimenting with kubeless was being migrated to a different data center. Now that I regain access to the server, I tried adding public modifier to the vb class, exactly as you suggested. Then deployed the function with all parameters set: kubeless function deploy dotnet-vb \
--runtime vbdotnetcore3.1 \
--from-file test.vb \
--dependencies test.vbproj \
--env ASSEMBLY_NAME=project \
--env MOD_NAME=module \
--env FUNC_HANDLER=handler \
--handler module.handler Unfortunately, I still get this error:
|
I wrote a function in vb and attempted to deploy it to kubeless. I got it passed the compilation phase, but the function can't be executed and the runtime container has this error log:
Is it the assembly path should be
/app/project.dll
instead of/app/*.dll
? If this is the case where is this/app/*
.dll came from or where to look to fix this wrong path?I am using compilation and runtime image from dotnetcore3.1 runtime to define new runtime that support vb.net. This is what I added to
kubeless-config
configmap (following these steps):This is my function definition:
vbproj:
The text was updated successfully, but these errors were encountered: