Aaron Hoffman's Blog

If you want to ensure you get line numbers in your Exception Stack Trace, you need to make sure your project is set up to provide "full" debug info on build. By default, for "Release" configuration, this is set to "pdb-only". Steps to enable: In Visual Studio... 1. Ensure your project is set to "Release" Solution Configuration (or whichever config you use for deployments) 2. Go to Project > Properties > Build 3. Click the Advanced Button in the bottom right. 4. Under Output > "Debug Info", choose "full" from the dropdown. 5. Save all settings and build your project. You will now see line numbers in Exception Stack Traces. Hope this helps, Aaron

We've been working with Azure WebJobs recently (more info: here and here ) and even though the built in logging to Azure Storage is great, it is difficult to query at times. In more recent version of the WebJobs SDK, the team exposed a TraceWriter collection via the JobHost configuration that allows consumers to write logs to a custom repository. The snippet linked below is a naive implementation of using that collection to write the logs to SQL Server. Feel free to adapt it to fit your needs (i.e. performance concerns, async, batching, etc.) Write Azure WebJob Logs to SQL: https://gist.github.com/aaronhoffman/3e319cf519eb8bf76c8f3e4fa6f1b4ae Hope this helps, Aaron

My google-fu wasn't the best when searching for a way to convert WGS84 to Web Mercator EPSG:3857, which is the common Google Maps and Bing Maps projection. If you have arrived here in search of an answer, the links to explain everything are below. Essential Background https://alastaira.wordpress.com/2011/01/23/the-google-maps-bing-maps-spherical-mercator-projection/ Take the EPSG WKT from article 1, and use it in the proj.net library http://blogs.u2u.be/diederik/post/2010/01/01/Converting-Spatial-Coordinates-with-ProjNET.aspx The definitive MSDN article https://msdn.microsoft.com/en-us/library/bb259689.aspx Code from MSDN article that doesn't use the proj.net Library https://gist.github.com/aaronhoffman/f53e1852ca289e4a806c062f97a18f05 Live Demo (in JavaScript): https://jsfiddle.net/aaronhoffman/L1kpdmgz/ And this next section is just to help others search and get here: Convert WGS84 to Web Mercator Convert WGS84 to Google Maps Convert WGS84 to Bing M

Working with some images of maps, I had a need for some pixel grid overlays. I couldn't find any with a quick google search so I made these in paint.net using the Grid Maker  plugin. Images below 8x8 pixel grid on 256 pixel image 8x8 pixel grid on 1024 pixel image 16x16 pixel grid on 256 pixel image 16x16 pixel grid on 1024 pixel image Hope this helps, Aaron

We are using proj.net  to calculate the UTM Easting/Northing values for a given pair of WGS84 Latitude/Longitude coordinates. But I couldn't find an easy way to determine the correct UTM Zone for a WGS84 coordinate pair. The Zone had to be provided for the library to calculate the Easting/Northing values. I wanted the library to decide the best UTM zone based on the lat/lng coordinates. To assist with this, I created the following table containing the "bounding box" lat/lng values for each UTM Zone in North America. Test Code and CSV file: https://gist.github.com/aaronhoffman/699d3659e1f68991e85d05e5637e1c5a The easiest way I found to determine these values was to use the centroid point for each UTM Zone, then add +/- 4 degrees Latitude (North/South) and +/- 3 degrees Longitude (East/West). I have also provided some C# code to convert these into arrays, and then an example using a " point in polygon " function to determine the appropriate UTM Zone.