Excluding files from build

Excluding files from build

Yesterday I made an unexpected discovery about how Visual Studio handles excluded files.

Perhaps it is obvious (but wasn't to me) that excluding files from a build is specific to the configuration.

As part of my testing, I added a second main program to my project, and excluded the original one.  The trap was that this was that I had different main programs for the Debug and Release versions, and I could not understand why the release version did not do what the code said - it appeared that 90% of the code was being inexplicably bypassed (in reality because that whole file was not being included in the Release build).

Of course, VS does indicate that the file was excluded, but the presence of a very small blue arrow on the icon is easy to miss unless you're looking for it.

Well, I guess I'm a little wiser now.


2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

A couple of great things about using Intel Fortran within the Visual Studio IDE is

  1. Visual Studio is used so widely in the Windows programming world in general and there is so much help out there that I find it takes only a few key strokes in an online search to find the answers I'm looking for and
  2. Intel Fortran's integration with Visual Studio essentially follows Microsoft's base unmanaged offerings such as C/C++.  So if one knows how to do something with these languages, then the same concept (and often the exact same approach) applies to Intel Fortran.


Leave a Comment

Please sign in to add a comment. Not a member? Join today