Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. How to fix 'File or assembly "System. WindowsRuntime" not found' Ask Question. Asked 2 years, 9 months ago. Active 2 years, 9 months ago.
Viewed 2k times. After a reinstallation of Windows 10 I get the error The file or assembly 'System. IsMouseVisible; Content. The project shouldn't have changed as well as I had it backed up on an external drive. Edit: This happens when having the project on any other drive than C:. Improve this question. MrMinemeet MrMinemeet 4 4 silver badges 17 17 bronze badges.
WindowsRuntime is included in your references. Maybe there is a yellow triangle that the filepath is not found — Mario Mitterbauer. NetFramework are you running? NET Standard currently netstandard 2. I didn't find an official statement on this if targeting. NET Core directly and not. NET Standard is also ok - or if this will be supported in the future. Having said that, I think there is a workaround for your problem. But I am not sure, if this is officially supported or if that will work in the future.
Currently, when you start a build from Visual Studio, Microsoft. This explains why System. Runtime cannot be loaded. But there is an option to call the. NET Core based generator from the build task. I didn't find any official reference on this - I just know this from the source code - so please be cautious when using this. This property was specifically added for the purpose of selecting which generator to use. I was not sure if this setting is officially supported.
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.
Generic; using System. Linq; using System. Text; using System. Tasks; using System. Windows; using System. Controls; using System. Data; using System. Documents; using System. Input; using System. Media; using System. Imaging; using System. Navigation; using System. Shapes; using Windows.
0コメント