JSON.NET for .NETCF 2.0 - compact-framework

Anyone having JSON builer/parser for .NETCF (Compact Framework) 2.0 version?

I found this library that works well with Compact Framework 2.0. This is not as mature as json.net but I have added Null attribute handling and JSONProperty for alias to actual field.

Related

Can i use Entity Framework 6.4 in .Net Standard Library (not .Net Framewrok Library)? If yes, How?

I am able to use .Net Framework Library with ASP.Net Core 2.2 and Entity Framework 6.4 but I want to use .Net Standard library with EF 6.4 instead of .Net Framework Library.
Finally i am able to resolve the problem by putting below lines in .net standard's .csproj.
<PropertyGroup>
<TargetFramework>net462</TargetFramework>
<PropertyGroup/>

.Net standard version for .Net core 2.2

Googled a bit but couldn't find the .Net standard version for .Net core 2.2. Only version I got is,
Any hint please?
As you can see in the table you have uploaded, .NET Standard 2.0 is the latest available and it is fully supported by .NET Core v2.0. As you can see in this release doc. section, .NET Standard 2.1 will be supporting .NET Core 3.0 and also .NET Core 2.2. For the whole page check here.
In my opinion, you can go with .NET Standard 2.0 if you do not deal with extreme things (I mean recently added parts of .NET Core). This can yield some errors but still worth the try.

Missing TaskCache class in .NET Core 2

I have created a Custom Model Binder in .NET Core 1.x . It works well as shown in the official tutorial.
Once updated to 2.0, I can't compile it anymore. In the old version it was
return TaskCache.CompletedTask;
Now the TaskCache static class isn't available anymore.
Does any know a workaround?
TaskCache.CompletedTask was removed in .Net Core 2. Instead just use Task.CompletedTask.

Assembly.GetExecutingAssembly() available in .NET Core?

Need to embed a json file as a source for testing in my .NET Core application. The author of this post http://codeopinion.com/asp-net-core-embedded-resource/ provided sample code that included the use of var assembly = Assembly.GetExecutingAssembly();However when I try this I get the error: Cannot resolve symbol ‘GetExecutingAssembly’ and ‘Assembly’ does not contain a definition for ‘GetExecuringAssembly’
If you are targeting .NET Standard 1.5 or above, you may call any of the following:
System.Reflection.Assembly.GetExecutingAssembly();
System.Reflection.Assembly.GetEntryAssembly();
System.Reflection.Assembly.GetCallingAssembly();
If targeting earlier versions of .NET Standard then the typeof(SomeClass).GetTypeInfo().Assembly method is the only way.
There is no "static" Assembly class in .NET Standard prior to version 1.5. Instead you have to do something like:
typeof(<AClassHere>).GetTypeInfo().Assembly
Where <AClassHere> should be replaced by the name of a class/type in the assembly you wish to load.
Nope, it's not available in .NET Core 1.0/1.1.
However, if I remember correctly it will be back in .NET Core 2.0 and the netstandard2.0 which is to be released later this year, which will have a much bigger API surface and increased compatibility with libraries written against .NET >= 4.5 making it easier to port these to .NETStandard 2.0/2.1.
But many of the APIs implementations will be platform dependent. Means, you will be able to call SomeAPI.GetSomething() everywhere, but if run on .NET Core it may throw a PlatformNotSupportedException.
But most APIs about assembly scanning and discovering should be back in .NET Core/Standard 2.0. Stuff around AppDomain will still be missing as there are no AppDomains in .NET Core and processes should be used for isolation.

Ignoring properties in RavenDB 3.5 (.NET Core)

Is there any way to ignore a property in a RavenDB entity class for RavenDB 3.5?
I'm working on upgrading a project to .NET core and this project relies on RavenDB.
Before when saving an object to RavenDB I could just add the attribute JsonIgnore from the Raven.Imports.Newtonsoft.Json namespace in the Raven.Abstraction library to the property I wanted to be ignored but this library doesn't seem to exist for 3.5.
Any ideas on how to solve this?
In the same way, the client is embedding the attribute, and it is available.