You’ve may have noticed that sometimes your project name is too long where other times it is accepted in the New Project Dialog. As explained by Paul on the Visual Studio General Forums…
The OS limit is 260 characters (MAX_PATH). However, the computation is:
Path length + 1 (separator) +
Solution name length + 1 (separator) +
Project name length + 1 (separator) +
Project name length +
80 (Reserved space)
The project name length is added twice: Once for the folder name and once for the file that holds your project itself (.vbproj, .csproj etc.). The 80 additional reserved characters are for the files that you place in the project. Most new project templates create several sub-folders for intermediate files that help with like intellisense and debugging. While we may not use the full 80 characters, it is a sensible limit.
Using Paul’s calculation above, let’s create a Max-Length project / solution named
ThisSolutionIsThirtyFiveCharacters (35 characters long)
C:\Documents and Settings\saraf\My Documents\Visual Studio 2005\Projects (73 characters long)
Doing the math, we get
73 + 1 +
35 + 1 +
35 + 1 +
So, VS will accept creating a solution / project ThisSolutionIsThirtyFiveCharacters at C:\Documents and Settings\saraf\My Documents\Visual Studio 2005\Projects.
Found out over the weekend that we had passed. Everyone going for shodan (1st degree black belt) had passed. Sweet.
Technically, I’m not a black belt until the ceremony in mid-Jan when we have our belts and certificates handed to us. However, last night when I got to practice, several of the guys made it a big deal to bow to me (as it is customary to bow to any black belts in the class when you’re a lower rank). It was pretty cool. Now, I get to look forward to perfecting what I already know and to help the lower ranks (like those guys from last night who are going for black next year) get ready for their Shodan exam. And yes, we’re going to start training them early, very, very early for this exam.
For those of you who used the VSEdit Powertoy for VS 2003, you’ll be happy to know that you can have similar behavior in VS 2005!
Just run “devenv.exe /edit <filename>” from the command line to open any file in an existing instance of Visual Studio 2005.
You may want to create a VSEdit command if you find yourself using this feature a lot. Just create a file called "VSEdit.cmd" (you can use notepad to do this) with the following:
@"%Program Files%\Microsoft Visual Studio 8\Common7\IDE\devenv.exe" /edit %*
Also, place VSEdit.cmd in a directory that’s in your PATH (or add the directory to your PATH).
now you can do