Visual Studio Vs. Eclipse.
Here is how this starts, two strong coffee’s and two nerds/geeks that have opposing technology backgrounds: .Net and Java.
 
.Net Guy: I programmed Java a while ago, but Eclipse (shakes head while talking to Java Guy).
 
Java Guy: What about Eclipse, it’s had refactoring practically from day 1. How long did it take Visual Studio? [This is a loaded/poking question because it took a hot minute for Visual Studio to get refactoring]
 
.Net Guy: Refactoring, heh and do you need to use that quite a bit? [Ohhh burn is what the .Net guy is thinking in his head, the rest of the world however is thinking: dear god, really, am I listening to this?]. I’m going to say one word “intellisence.” Let that sink in for a bit.
 
Java Guy: How much was Visual Studio Professional again [dramatic pause]? Eclipse “Professional” is free. Oh did I mention Eclipse “Premium Edition” is faaa-reeeee. One more thing Eclipse “Ultimate” is…. [Java guy makes a circle with his index finger and thumb and says wazang as he raises his hand] free as in if yo’ Daddy was Visual Studio yo’ Mama could download Eclipse and have an affair for free.
 
.Net Guy: [Laughs] WTF are you talking about? [Laughs some more] This is why we get along so much, because we can joke about this with each other. We probably should get back.

On the way back to the desk:
.Net Guy: Eclipse really is pretty darn nice these days, and I can’t believe that it’s free.
 
Java Guy: I would like to have an affair with LINQ.
 
[Both Laugh]
 
Here is what I came up with world. This is an astronomically dumb conversation because there really is no winner. It’s an apples to oranges kind of conversation. Further, if you think about it on any level, nobody is ever going to do Java programming in Visual Studio and on the other side nobody is ever going to do .Net programming in Eclipse, therefore it’s a trivial argument, but with the right buddies it sure can be a funny one.

Problem:
Done executing task "AspNetCompiler" -- FAILED.
Done executing task "CallTarget" -- FAILED.
(default target) (1) -> (Website target) -> ASPNETCOMPILER : error ASPRUNTIME: Request failed.

Solution:

What was going on and not being said was the computer I was on didn't trust the assemblies I was using on another computer....We all could have got that from the error right? Anyways, there is a fun little tool called, .NET Framework 2.0 Software Development Kit. Once this kit was installed and downloaded I ran an application called, .NET Framework 2.0 Configuration. In this tool I selected

• Runtime Security Policy <-- Once selected in the right pane I selected
  • "Adjust Zone Security"
    • Once this is selected I choose
    • "Make changes to this computer." Click Next
      • On the next screen click "Local Intranet" and move the trust arrow up to "Full Trust" I did it for Trusted Sites also.

Explanation:
Remember .Net doesn't let you run assemblies from any which location. Why would they‽ That could be a nightmare of security issues, so developers when working on assemblies across the network and things go south always think perms, down to an assembly level.

Error Readout:
None, it's not an error silly.

The Problem:
When I debug, and look at a string that contains my file path I see 2 backslashs (escape characters) in my string when I only wanted 1.

The Solution:
It's nothing, don't worry about it, that's just the way Visual Studio "debug" shows your path when you catch it while debugging.  When the path is used in the code for the file system there will only be 1 backslash and it will work correctly.

This is such a stupid little thing, but for some reason every once in a blue moon, I forget and freak out on why it's doing this, thus wasting a solid five minutes of my life. I put this post up in hopes I will never forget again and that if someone happens to Google this, my post will pop up and help them move on quickly....maybe only wasting 1 to 2 minutes. :)