Visual Studio

So this is the post where I consider the outside, long-shot, limit as x goes to infinity possibility that I may have made a mistake in a previous post.

Waffle-y enough for you?

I recently stumbled upon an issue that, provided the correct circumstances could prove to be slightly troubling. Recently, I had to deal with multiple versions of a test project I'd been working on. I had to store a few things to be loaded at run-time, and saved on close. Doing this, I saved a few things to the project settings. However, upon changing the versions (installing an update) the settings were lost, as a new file was generated for the latest version. Perplexed, I turned to the internet. After a shockingly large amount of searching, I finally happened upon some code that helped.

As Mini reported, Microsoft has finished shipping Microsoft Layoff 2009, to middling response. Microsoft laid off roughly 5% of their workforce in an effort to appease Wall Street and improve their stock price.

We're starting to focus on the startup time of our current application. We're sitting at about 5-8 seconds, and that's pretty good for what we're doing; however, every time we throw an exception (obviously, it gets caught), we go on a massive bug hunt.

Some of most egregious examples are System.FileNotFoundExceptions. These were cropping up in the strangest places. I started to track them down to all of our XmlSerialization.

I spent a few minutes yesterday working on adding some code snippets to my personal collection as I refactored a bunch of code. And it got me to thinking about how to be more efficient while using my editor.