So, last week one of my colleagues wanted to serialize an object along with custom property attribute to JSON. Interesting… JSON.NET by default will not allow serializing custom property attribute. So, you have to write custom JSON converter to fix this. Let’s take a look at how
- Optimising Image Processing: Reducing memory consumption and time taken by 80%
- It’s Not Your Code Vol. I: Reducing AWS S3 .NET client LOH allocations by 98%
- Strings Are Evil: Reducing memory allocations from 7.5GB to 32KB
you should either use the using statement, or let the DI container handle disposing objects for you. For cases where that's not possible, ASP.NET Core provides two mechanisms you can hook in to: RegisterForDispose and IApplicationLifetime.
Do use the interface IReadOnlyList<T> or IReadOnlyCollection<T> to expose a collection.
Use IReadOnlyList<T> if the item order is important and deterministic.
Use IReadOnlyCollection<T> if the item order is not important.
.NotSupportedException: The method 'Max' is not supported
This topic provides information about the way in which LINQ queries are composed and executed when you are using the WCF Data Services client and limitations of using LINQ to query a data service that implements the Open Data Protocol (OData). For more information about composing and executing queries against an OData-based data service, see Querying the Data Service (WCF Data Services). Composing LINQ Queries LINQ enables you to compose queries against a collection of objects that implements IEnumerable. Both the Add Service Reference dialog box in Visual Studio and the DataSvcUtil.exe tool are used to generate a representation of an OData service as an entity container class that inherits from DataServiceContext, as well as objects that represent the entities returned in feeds. These tools also generate properties on the entity container class for the collections that are exposed as feeds by the service. Each of these properties of the class that encapsulates the data service return a DataServiceQuery. Because the DataServiceQuery class implements the IQueryable interface defined by LINQ, the WCF Data Services you can compose a LINQ query against feeds exposed by the data service, which are translated by the client library into a query request URI that is sent to the data service on execution. Note: The set of queries expressible in the LINQ syntax is broader than those enabled in the URI syntax that is used by OData data services. A NotSupportedException is raised when the query cannot be mapped to a URI in the target data service. For more information, see the Unsupported LINQ Methods in this topic.
Url: C:\Users\Morteza\Downloads\ExplorerPCalV.1.1\Bin\ExplorerPCal.exe -> ExplorerPCal, Version=1.1.0.0, Culture=neutral, PublicKeyToken=a55a2614eb2aee77 Caller: ExplorerPCal.App -> appDispatcherUnhandledException Exception classes: System.NullReferenceException System.Reflection.TargetInvocationException System.Reflection.TargetInvocationException Exception messages: Object reference not set to an instance of an object. Exception has been thrown by the target of an invocation. Exception has been thrown by the target of an invocation. Stack Traces: at ExplorerPCal.Utils.ConfigSetGet.GetConfigData(String key)
