Click here to Skip to main content
15,887,746 members

Comments by Baxter P (Top 9 by date)

Baxter P 22-Sep-14 4:39am View    
Tried the null entry check in the linq query, exception is still thrown. I have also tried updating the DBContext, but again exception persists.
Baxter P 20-Sep-14 3:42am View    
I saw that too, but I suspected the problem was unrelated to mine.

OK, so I have to test for NULLs like so:

var UserDataLocal = (from data in lookUpContext.JMUsers.ToList()
where data != null
select new UserData(data.ID, data.UserName)).ToList();

to be honest I thought the problem was a WPF one.

I try it on Monday. Cheers.
Baxter P 19-Sep-14 5:33am View    
Hello all,
I have imporved the question, and included more details.
Baxter P 21-Mar-14 13:10pm View    
Thanks
Baxter P 19-Feb-14 20:10pm View    
Sounds like the DLL which contains the DateWiseIP class in it is missing from the deployment machine, or it can't be found once deployed.

If you are using click once, you can specify the DLL which contains the DateWiseIP class in it as one of the required assemblies. It will then be sent along with the other assemblies, and be copied into the same folder.