Big Data and You

I'll flesh this out later but I wanted to put down a link before I forgot:

The Scoreboards Where You Can’t See Your Score -- nytimes.com


Comments

Post a Comment

Popular posts from this blog

List of Visual Studio Keyboard Shortcuts

Here's a link to a great list of keyboard shortcuts for Visual Studio: 149 Shortcuts for Visual Studio 2015 (Windows) While there's no need to memorize the list (that's why someone has created a cheat sheet, after all), it certainly doesn't hurt to look over the list from time to time and try to add one more command to your repertoire.
Read more

Using Reference Aliases

Image
I recently ran across a situation where two different libraries shared identical namespaces and class names. Visual Studio complained anytime I used one of these classes that it was an ambiguous reference. I needed both libraries -- each contained some unique elements -- so I couldn't ditch one or the other. But, as I said, anytime I tried to use a class that was common (again, via the class name and namespace), I received the ambiguous reference error. This was a real problem, so say the least. However, C# provides a way to specify exactly which library (reference) you mean when you use an object that's common to two or more libraries. Simply put, you use an extern alias  statement. The concept is fairly simple: Give the reference an alias (I used the Properties windows for the reference). Add an extern alias statement, putting it before your using statements. Add a using statement, which effectively links a specific object through the extern alias statement to th...
Read more

Most Likely Cause of the C# Error: "Non-static method requires a target"

I've encountered this error twice in the last two days, both times occurring while with a LINQ query and Entity Framework. And, in both cases, the problem stemmed from using a null value within the LINQ. Ultimately, the problem was farther upstream and not with my LINQ query at all (though better use of a try-catch statement would've been smart). The problem was an object with a null value being passed into the method. Once I figured that out, it was fairly easy to step through the debugger and see where my object wasn't being set to a legitimate value. So, if you get the error "Non-static method requires a target,", then verify that every value you're using within your LINQ statement contains a value, not a null. See the following posts on the web for more information and resolution to this error. Non-static method requires a target http://stackoverflow.com/questions/13717355/non-static-method-requires-a-target EF Non-static method requires a targe...
Read more