Outer Level Blog » .NET http://outerlevel.com/blog Building a MicroISV Tue, 22 Jun 2010 14:25:35 +0000 http://wordpress.org/?v=2.9.2 en hourly 1 Reflector for .NET http://outerlevel.com/blog/2006/05/15/reflector-for-net/ http://outerlevel.com/blog/2006/05/15/reflector-for-net/#comments Mon, 15 May 2006 20:36:51 +0000 Jon Trainer http://www.outerlevel.com/blog/2006/05/15/reflector-for-net/ Recently, a coworker introduced me to this cool little utility for browsing and decompiling Microsoft’s .NET class framework called Reflector for .NET.

The best feature is that it doesn’t just reveal the underling IL code but it translates it into either C# or VB.NET. It also has the ability to decompile other “compiled” .NET libraries as well. A good case for obfuscation?

]]> http://outerlevel.com/blog/2006/05/15/reflector-for-net/feed/ 0 Catastrophic Failure http://outerlevel.com/blog/2006/01/28/catastrophic-failure/ http://outerlevel.com/blog/2006/01/28/catastrophic-failure/#comments Sat, 28 Jan 2006 15:33:15 +0000 Jon Trainer http://www.outerlevel.com/blog/2006/01/28/catastrophic-failure/ A teammate working on the same .NET project at my consulting gig recently experienced the following error while working in Visual Studio 2003.

Not only was the error dialog filled with helpful information, but nothing happened when the developer clicked the “OK” button. No crash, no loss of data, nothing. He just kept working.

]]> http://outerlevel.com/blog/2006/01/28/catastrophic-failure/feed/ 0 Visual Studio: Could not write to output file http://outerlevel.com/blog/2006/01/09/visual-studio-could-not-write-to-output-file/ http://outerlevel.com/blog/2006/01/09/visual-studio-could-not-write-to-output-file/#comments Mon, 09 Jan 2006 17:00:37 +0000 Jon Trainer http://www.outerlevel.com/blog/2006/01/09/visual-studio-could-not-write-to-output-file/ One of my all-time favorite Visual Studio 2003 bugs occurs when trying to build a solution with multiple projects that all reference a base library.

If any code changes in the base library, the very next build will always fail with the following error:

Could not write to output file '[path-to-project]\obj\Debug\[file-name].dll' -- 'The process cannot access the file because it is being used by another process. '

What’s really pathetic is that the “other process” is Visual Studio itself. Something about the way the build works causes the process to step on itself everytime the base library needs to be compiled.

The only way I’ve found to get around the issue is to close Visual Studio, manually delete the library’s /obj and /bin directories. Then reopen Visual Studio and rebuild.

Really, friggin annoying. I can’t believe this hasn’t been found and fixed already.

]]> http://outerlevel.com/blog/2006/01/09/visual-studio-could-not-write-to-output-file/feed/ 2