well, I don't have a lot of experience with VS+MPI, but these are the
steps taht I followed to make my projects run:
1. Select your project from the Solution explorer, right-click and select
2. From the list on the left, select "Debugging"
3. Set "Debugger to launch" to "MPI Cluster Debugger"
4. Set "MPIRun Command" to the full path of your "mpiexec" (use quotes at
to enclose the path)
5. Use "MPIRun Arguments" to set the number of processes to start, like
6. Set "MPIRUN Working Directory" if you need.
7. "Application Command" normaly is "$(TargetPath)"
8. "Application Arguments" if you need them.
9. "MPIShim Location", this is a triky one, for some reason some times VS
needs the full path for this VS tool. It is located at: "C:\Program
Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote
Debugger\x64\mpishim.exe" or "C:\Program Files\Microsoft Visual Studio
9.0\Common7\IDE\Remote Debugger\x86\mpishim.exe" (use quotes at to enclose
I haven't played with the other options.
10. Close the dialog box.
11. Set some breakpoints in your program.
12. Ready to run.
These instructions only work to debug MPI processes on the localhost, and
I only have tested VS+MPI using MPICH2 for Windows.
To debug on several nodes you should install the Microsoft HPC SDK (I
haven't used it).
PS. I use Visual Studio 2008 professional. Also, I know that MPI debugging
is not available in VS Express editions.
> Does anyone on this list have experience using MS Visual Studio for MPI
> development? I'm supporting a Windows user who has been doing Fortran
> programming on Windows using an ANCIENT version of Digital Visual
> Fortran (I know, I know - using "ancient" and "Digital" in the same
> sentence is redundant.)
> Well, we are upgrading his equally ancient laptopa new one with Windows
> 7, so we installed Intel Visual Fortran (direct descendent of DVF) and
> Visual Studio 2010, and to be honest, I feel like a fish out of water
> using VS 2010. It took me a longer than I care to admit to figure out
> how to specify the include and linker paths.
> Right now, I'm working with the Intel MPI libraries, but plan on
> installing OpenMPI, too, once I figure out VS 2010.
> Can anyone tell me how to configure visual studio so that when you click
> on the little "play" icon to build/run the code, it will call mpiexec
> automatically? Right now, it compiles fine, but throws errors when the
> program executes because it doesn't have the right environment setup
> because it's not being executed by mpiexec. It runs fine when I execute
> it with mpiexec or wmpiexec.