Click here to Skip to main content
15,886,873 members

Comments by Ahmad_kelany (Top 43 by date)

Ahmad_kelany 19-May-22 5:33am View    
You're welcome
Ahmad_kelany 14-Feb-22 11:59am View    
Thanks for the reply,

Did that, didn't work, I am beginning to think that it is a missing feature in Blend 2022.
Ahmad_kelany 21-Aug-21 8:04am View    
Thanks for replying

I was able to get more info about the exception,

I added exception info to it..

Does this help?
Ahmad_kelany 23-Aug-20 18:14pm View    
Sir,

In the third line of my question I said that I referenced the .dll file produced by the 2.0 standard, and I still got the exception,

Me trying to use Nuegt package was just trying another approach to avoid the exception, not using it "just because" ..

And the .dll file and the Nuget package work fine in other projects, be it WPF or winForms,

So clearly the issue is not in the .dll file or in the Nuget Package,

As I said, there is an issue in the project situation, and I'am trying to figure it out, why does it give me that exception despite the package referencing 2.0 standard not 2.1?

Notice that the exception says that it couldn't find 2.1 standard, but the inner exception says it can't find 2.0 standard..
Verily it seems that I am missing something, but I still don't know what? or how to investigate further.. 😅


Ahmad_kelany 22-Aug-20 17:16pm View    
I tried it with a complete WPF project, and with a new Winforms project, and it worked fine in both cases, as I stated in the question,

As I said, probably the problem is not in the frameworks, but in the project's specific situation,

And I totally agree with your last line, I used 2.1 standard for a certain feature, but as it was incompatible with 4.8 framework, I foregone that feature and went back to 2.0..

My main question is how to investigate that exception and what causes it..