Mono could not load file or assembly system runtime remoting

Is the intended way to build Function apps V2 to target. NET Standard or is targeting. NET Core "directly" also ok? I ask because it seems that some people target. NET Core directly mainly because they want to use. Functions apps are supposed to target. NET Standard. If the app targets netstandard either of the generators should be able to generate the functions. But from the build perspective, if the app has. NETCore dependencies, and the build is triggered from full framework msbuild, then right property needs to be set UseNETCoreGenerator to use the core generator instead of full framework generator.

The UseNetCoreGenerator allows a. NET Core 2. I can supply my project I am using to replicate this, but it does feel like an Azure Function Project should target 'netstandard20'. So I'm having this same issue targeting net I also added the UseNetCoreGenerator and my runtime breaks now. The weird thing is that it is only happening on one of my computers. This same code is on another computer and it compiles fine and runs fine.

In fact, I never even got the error that started this thread on my other computer. It only ever occurred on one of my computers. Is there something I should check for on the working computer that is installed that maybe isn't installed on the one that has these errors? Make sure that you run your. Wow this is too bad - Are there plans to support. NET Core directly? Spoke briefly to fabiocav about this the other week as I hit it by referencing my function from an xUnit test project.

Thanks for the pointer and quick assistance jeffhollan! Using a default Functions v2 template we're getting an error on one machine like the one called out here but for System. I haven't added the generator tag or anything, this is the fist time I've ever seen this error in my experience with Functions.

Do we have an official solution here? For my scenario, the VS installation was I updated the problem machine's. Net Core SDK installation was 2. Note the Experienced the same issue whilst running an xUnit Test Which cannot be. AggregateException: One or more errors occurred. ArgumentException: Process with an Id of is not running.

Task 1. InnerInvoke at System. Execute End of stack trace from previous location where exception was thrown at System. MoveNext End of inner exception stack trace at System. Can you elaborate a little more on your scenario?

Are you trying to put function definitions into class libraries and then reference them from multiple function apps? OK, so yes, I can put the functions in a shared class library and the intent here in part is so that they can be distributed via a nuget package , and they'll compile as long as I have these refs:.

But there has to be another step, because the tooling in a functions project referencing the shared library won't generate any of the json files that the runtime needs to "find" the functions.

Running locally, the console will say there are no jobs found. Got it. For this particular scenario, if you try the other approach I mentioned specifying V2 in the csproj , does that work for you? I think fabiocav has some ideas on how we could improve our handling of this scenario, I'll let him comment.

No, it's already set in the functions project. All I did was move the function classes to the shared library and add the above references. This is what we're planning to address. I've updated an existing issue we have tracking this and assigned to the upcoming milestone, so you can track that for updates For those who is still struggling. Explicitly adding System. Runtime NuGet package to the project Azure Function seemed to resolve this issue for me.

I was also having this problem. I created a function using VS for Mac and then pulled the source down to my Windows laptop and it wouldn't compile giving me the System. RunTime Error. Fixed it by adding the v2 in the AzureFunctionsVersion which was blank. If the last two suggestions alone doesn't help you, try updating the Microsoft. Functions package from 1.

That fixed the build issue for me. I'm seeing a related warning message in my output to this which hasn't been referenced yet in this thread InvalidCastException: [A]System.

AppDomain cannot be cast to [B]System. Type A originates from 'System. Type B originates from 'System. Are you missing a private assembly file? Anyone else seeing this in the logs when running? Interestingly enough - I use both Rider and VS I do not get this problem with Rider.

LoadFrom call - then its base directory will not be searched then B won't be searched in A 's base dir. I couldn't entirely make sense of my previous comment so let me clarify for future-me:. Skip to content. Star 9. New issue. Jump to bottom.

Labels area-Runtime: Loader. Copy link. Given a custom msbuild task, mytask. Reflection; using Microsoft. GetName ; Console. Load System. AssemblyName assemblyRef, System. LOG: Assembly download was successful. Member Author. Load assemblyName ;. Load does not respect AssemblyName. CodeBase Assembly. Load from an msbuild task does not load assemblies from the task's directory Jul 13, LOG: Where-ref bind Codebase does not match what is found in default context. Keep the result in LoadFrom context.

LOG: Binding succeeds. Native image will only be probed in default load context, like with Assembly. Unfortunately, I get the same result as before. It could well be my error. The version that is installed is 4. Below is the basic output, and the verbose output is attached. GCHandle:FreeHandle int emitted at 0xdea40 to 0xdeaee code length [nuget.

Context:ReleaseContext System. Context Method wrapper managed-to-native void System. Context emitted at 0xdeb40 to 0xdebee code length [nuget. InternalThread,intptr Method wrapper managed-to-native void System. InternalThread,intptr emitted at 0xdecc0 to 0xded98 code length [nuget. Based on the comment from schiebel who is using Mono 4. Skip to content. Star 1.

New issue. Jump to bottom. Labels Platform:Mono Resolution:External. Milestone 4.