Skip to main content

LINQ Errors: “The Type arguements for method cannot be inferred from the usage. Try specifying the type arguments explicitly ” & for the data context object “There is no implicit reference conversion from XXX RepositoryContainer(ReportContext) to System.Data.Objects.ObjectContext”.

Day before yesterday, we faced minor problem in compiling our wcf service which is using LINQ for DML operations.  It’s continuously yielding in giving the errors like “The Type arguments for method cannot be inferred from the usage. Try specifying the type arguments explicitly ” & for the data context object “There is no implicit reference conversion from XXX RepositoryContainer(ReportContext) to System.Data.Objects.ObjectContext  ”.

We are actually using Entity framework and LINQ to entity.
After a couple of hours, I actually dig into the problem and I found that the project in which the entity is being queried is missing the assembly reference >> System.LINQ. Adding reference to this fixed the problem.

Popular posts from this blog

Remote debugging Windows azure cloud service - Worker Role

Remote debugging Windows azure cloud service - Worker Role Very recently I was working on design and development of a worker role component of cloud service. Locally debugging worker role is pretty easy. You just need to know that you need to set Cloud project as a start-up project and ready to go. Problem is when you deploy worker role to azure and trying to troubleshoot an unknown issue.  Thankfully we have remote debugging enable for cloud services – both web and worker roles. This is really handy tool to remotely debug without having to putting a lot of tracing and digging into it. However, remote debugging in worker role/web role requires few steps to be followed: Make sure you are debugging from same machine where you published Make sure to turn on Remote debugger on while you publish (This should be turned off for Production publish profiles) Make sure to Select Debug mode With all the above settings after you publish, you should be able to Atta...

Debugging code running on Remote machine

Before performing below steps, you need to make sure you have pdb files matching dll version on the remote machine.  Open below folder in your remote machine C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Remote Debugger\x64  Open that folder and launch as admin  msvsmon.exe  Select all options to allow firewall From Tools > Options  - Keep the settings to default (as shown below) and click ok.  At this point your remote debugger is all set. You need to connect from Visual Studio by entering Machine IP: Port (4022) 

Differences between Object Serialization and Deserialization?

Serialization = putting the relevant state of the object into a streamable representation. That can mean converting it to a byte stream. This does not necessarily include copying every member variable into the stream. Deserialization = restoring an object from a serial representation and ensuring the invariants of the object. Deserialization can be thought of a separate constructor for the object.