topic Re: Visual Studio 2010 - Start External Program in ArcObjects SDK Questions

Visual Studio 2010 - Start External Program

ChanceYohman1 — Thu, 01 Sep 2011 20:54:28 GMT

ArcGIS Desktop Project, Visual Studio 2010, Multiple Developers, 32-bit and 64-bit machines

I try to Start External Program : %AGSDESKTOPJAVA%\bin\ArcMap.exe (or enclosed in ")

VS says it can't find the application, but I can launch the app from the command line using the above. Has anyone solved this? I want to do this to deal with varying paths on different developers' machine (i.e. Program Files (x86) vs Program Files).

Thanks for your time.

Re: Visual Studio 2010 - Start External Program

NeilClemmons — Fri, 02 Sep 2011 12:25:18 GMT

The path is stored as a user-specific setting. Visual Studio stores this setting in the *.suo file that sits alongside the solution (*.sln) file in your solution directory. If you're using source control, then this file shouldn't be included when you add the solution to your source control provider. If you're simply copying the solution down from a server or something, you shouldn't copy this file. Each developer should have their own *.suo file on their development machine.

Re: Visual Studio 2010 - Start External Program

AlexanderGray — Fri, 02 Sep 2011 14:58:10 GMT

I have never got relative paths to work in the start external program in VS2003, 2005 or 2008. You need absolute path. But Neil is right, we keep the .suo as an external file to our source control and everything is ok. Plus the suo contains other things you usually don't want to share (compile type for example is usually debug on developer machines but could be changed to release.)

Re: Visual Studio 2010 - Start External Program

RichardWatson — Fri, 02 Sep 2011 18:38:10 GMT

We have a related problem in that we have developers with 32 bit operating system and developers with 64 bit operating systems. This creates a problem when referencing files because the file paths are different. What we do is to use the SysInternals junction command to create the "Program Files (x86)" path on 32 bit machines. This works for us because we always install to the C drive.

I think that junction, or mklink, are very powerful commands that can be used to solve these types of problems.

If do want to insist on the C drive then another trick we use is to create a logical drive, say X, using the DOS subst command. This allows the developer to install to any location.

Re: Visual Studio 2010 - Start External Program

ChanceYohman1 — Wed, 07 Sep 2011 14:35:26 GMT

Except keeping the .suo in the repo is a requirement.