If include the referred assembly's project into your solution and then put a reference to that project instead of directly referring the assembly, you will get configuration dependent references. I admit that this is kind of awkward, but it's the only way that I know of.
According to Microsoft, there is currently in VS2005 one xml proj file that holds the project properties, including a separate item group node for file and project references. The same file is used for both debug and release mode settings. This is definitely a limitation (for the time being). But improvements are under way[^].
Does anyone know why Peek() is blocking when called on the StandardOutput stream?
I've heard that it might block if nothing ever has been written to the stream before Peek() is called. The problem occurs both with VS2003 and VS2005 (.NET 1.1 & .NET 2.0).
System.Diagnostics.Process p = new Process();
p.StartInfo.FileName = @"c:\windows\system32\notepad.exe";
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook
Sorry no. Wrote this in about 10-15 minutes. Tested it with two numbers and it worked. Good enough for me. I didn't want to spend more time coding this, as I think I already took this joke a bit far (though it would've been nice to write some code without using the increment operators )
BTW, refactoring in VS2005 is still one of my favorite features. Sure did the trick on those pesky, descriptive variable names