I stumbled onto this error and thanks to Scott Hanselman’s blog I was able to find a solution to it.

The only problem? My project had a TON of files marked as Content (such as multiple versions of angular) and I didn’t want to spend all morning going through the countless folders to figure out which files were missing in order to resolve the conflict. If only Visual Studio has some way to verify this and let you know which files were missing…

Oh wait, it does! Its just buried and very difficult to find.

You can get visual studio to display all these “yellow icon” missing files by using the Publish Solution option. For those of you unfamiliar with the publish wizard, here is what I did:

  • Right Click your website project and click publish.
  • On the publish wizard that pops up, select Custom and type in any name for the profile.
  • For publish method, I selected File System and chose a directory to publish to.
  • Click the Publish button and it will error and show you exactly which files were missing. You may have to do this multiple times until you get all the missing files resolved.

I recently bought a brand new Cordoba classical guitar. I am extremely happy with my purchase and would recommend this guitar a thousand times over. My only problem with it is the Savarez Cristal Corum High Tension 500CJ strings that came stock on the guitar.


The good
On the plus side, these strings seem to settle in and stay in tune much faster than other ones I have tried. Perhaps this was done on purpose by Cordoba to ensure that floor models of their guitar would always sound great when picked up and played by a shopper.

The bad
These strings seem to wear down very quickly. They can be hard to press down since they are so stiff. The trebles are very dull and it only becomes more noticeable the more you play on them. Also, the price for these things can be steep compared to popular D’Addario ones.

The ugly
After owning the guitar for a month or so and playing for a few hours each night, the strings seemed to rapidly degrade. They barely respond when I am playing now, especially hammer-ons and pull-offs which are now much harder to get proper timbre from. All in all, I would not recommend these strings.


This is the same as the 3D wireframe example which was done in OpenGL, only ported to the new technology known as WebGL. WebGL is still a new technology that uses GPU acceleration to render 3D graphics in a web browser and it has shown vast potential to modernize the web.

Many browsers do not even fully support WebGL at the moment. As such, to view this example you will need an updated, modern browser such as Firefox, Chome, or Opera. Internet Explorer does not support WebGL rendering at the moment unless you install a plugin.

This demo relies upon the GLGE and GLGE_math libaries in order to render.

http://akamaicovers.oreilly.com/images/9780596517748/cat.gifJavaScript, which was originally thrown together over a span of 10 days, has its share of bad parts. Of course, many of these have been remedied over the years thanks to ECMA standards process and the creation of high performance JS engines such as Google’s V8. Enter the highly divisive and opinionated book from the original JS guru, Douglas Crockford.

I thoroughly enjoyed this book and felt that I learned so much from it even though it is a shorter book. Though it is necessary to state that this book is not for JS beginners. The main thing that I did not enjoy are the reliance upon the railroad diagrams, which are not very intuitive to anyone who has previously not implemented some sort of context-free grammar (which I would wager is a majority of JS programmers).

Beyond this singular drawback, this book is filled to the brim with nuggets of wisdom. The sections on functions, patterns, and closures was a huge eye opener to the mystery of JavaScript’s inner workings. Chapters 3 and 4 alone were so insightful to me that I feel as if they should be required reading for all serious JS programmers.

I love the opinionated style of the writing displayed in this book. The author is very knowledgeable and passionate so he is able to get away with it. The appendix, appropriately titled “Awful Parts” and “Bad Parts” is far more entertaining than you would expect and provides examples and evidence backing up the author’s assertions.

All in all, this book is highly recommended and is a must read for all serious javascript developers.

If you are writing code to show a large amount of records in an ASP.NET GridView control, you should do your best to make them easily readable since it can be overwhelming. I’ve ran across a few different hacks using JQuery to enhance the presentation of GridView records, but this seems to lag the user’s browser when a large number of rows is encountered. I have wrote a small function that performs this action server-side and rids the user of the content-rendering JQuery lag spike.

Continue reading

In my database course at Marshall University, I helped my professor with a side project involving Cancer research data that has been collected since 1973 by the National Cancer Institute. My first job was to take the SEER data and load it into a postgreSQL database.

The job was simple enough. The only problem? The data files were in SAS format. Basically the format was CRLF delimited entries composed of fixed-length fields. Here is a list of the fields and lengths that I used for the script.

Continue reading

So I was using a 3rd party iPod management program to copy songs from my iPod back to my hard drive and the program somehow made a folder with a name that was absurdly long. So long that even windows refused to delete it no matter what. The exact error says: “The filename or extension is too long”. The official MS documentation gives 5 suggestions and none of them seemed to work for me. Here is what I did to fix the problem.

Continue reading


This is a Mandala I created in Adobe Photoshop from scratch for the RST department at Marshall University.

Click the thumbnail to see the full size image.