“Sometimes the biggest value is in defining the problem, not solving it”.
The quote above is from the Pluralsight course “Practical Networking” by Ben Piper. I watched it recently, and liked something said in relation to troubleshooting in general.
Viewing Linqpad scripts in VS2013
I use LINQPad all the time at, both for experimenting with C#, and for building and testing Linq queries before I import them in our projects.
As an example, I recently wrote a few scripts for fetching some data from a database, and reformatting it into JSON data which we will use as dummy-data for testing. This will not be a part of our finished project, but it’s still nice to have the script visible in Visual Studio, even if I only run it through LINQPad .
The following are a couple of tips I’ve found useful when working with .linq-files in or from within Visual Studio.
Getting into InfoSec
Over the last year or so, I’ve grown more interested in information security, both technical aspects like cryptography and pen testing, and more organizational issues, like governance, risk management and compliance.
This is obviously a huge field with lots of challenges, and one in which come constantly and quickly. I’m adding this category to my site as a place to muse over and share some of the things I read and learn along the way.
Visual Studio: Managing several window layouts
Do you use a varying number of monitors depending on where you are working? If so, you might find this little tip helpful.
Camel Case in Visual Studio using Resharper
I’ve always preferred to use camel case navigation if possible, but this is not the default behavior in Visual Studio. If you’re already using Resharper, this checkbox under Resharper > Options is the easiest way to enable it:
If you don’t know what I mean by Camel Case navigation, consider the following method name as an example: