hubFS: THE place for F#

. . . are you on The Hub?
Welcome to hubFS: THE place for F# Sign in | Join | Help
in Search

Minor annoyances with VS project build behavior

Last post 05-17-2008, 5:13 by dsyme. 1 replies.
Sort Posts: Previous Next
  •  05-15-2008, 17:23 5913

    Minor annoyances with VS project build behavior

    I'm trying to build an F# project with XNA support on vs2008.  The XNA DLLs are not installed into the GAC and instead are installed in the program files directory, and I had to include the search path using the -I flag.  Problem is that I'm working on this project from multiple machines, one being 32bit and the other being 64bit so the program files path is different on each.

    I tried using the environment variable "%XNAGSv3%" to specify the location of the DLLs but F# projects don't do environment variable expansion when executing the compiler.  Fine, no big deal, I said to myself and wrote a batch script to handle the include paths and set it as the custom compiler value in the project options.  Now my problem is that the custom compiler value can't handle relative paths, environment variables or macros and if my SVN checkout path is different on each system I'm screwed.

    Oh FYI:  There is a minor UI bug; the "..." path select button for the custom compiler option is active only when the custom compiler option is deselected.
  •  05-17-2008, 5:13 5944 in reply to 5913

    Re: Minor annoyances with VS project build behavior

    Thanks for the bug reports. Enabling environment variable expansions is certainly a good idea and something I believe our IDE team intends to enable.

    Kind regards

    Don

View as RSS news feed in XML
Powered by Community Server, by Telligent Systems