1

I have a folder c:\TestSolution that contains a VS2010 solution TestSolution.sln.

If I'm on the command line (with appropriate vcvars.bat file already run), and I type C:\TestSolution>devenv TestSolution.sln I get the following popup:

enter image description here

However, if I supply the full path it loads correctly. E.g. C:\TestSolution>devenv c:\TestSolution\TestSolution.sln works.

In previous work environments, I didn't have to supply the full path, so I'm not sure what's up.

Any ideas?

oz10
  • 153,307
  • 27
  • 93
  • 128
  • That is strange. It works just fine for me. – rory.ap Sep 23 '13 at 21:11
  • Yeah, I'm sure there is a setting somewhere in the registry that controls the behavior I just don't know what it would be, nor do I have access to SysInternal to monitor registry accesses as I load devenv... hoping someone can clue me in to the cause of this. It is hugely annoying. – oz10 Sep 23 '13 at 21:17
  • I was going to suggest SysInternals actually. How come you can't use that? – rory.ap Sep 23 '13 at 21:20
  • Not approved software ;( At the moment, I'm in one of those draconian "secure" environments where all software needs to be approved for use. – oz10 Sep 23 '13 at 21:21
  • meh, forgoing `devenv` and just opening the solution c:\TestSolution>TestSolution.sln passes to the VSLauncher app and opens the solution with version the solution is for... so that is a good work around... but it is still annoying that my old habit of typing 'devenv solution.sln' doesn't work ;( – oz10 Sep 23 '13 at 21:59

0 Answers0