Visual Studio Build Options
-
Does any one know of an easy way to maintain seperate Visual Studio "include file profiles" and quickly switch between them? (Something like a user defined "Platform"?. I use VS to develop both Win32/MFC apps and MS-DOS 16 bit apps and they have completely different include/lib/prog directory locations. At the moment I have to run a batch file to modify the VS registry entries every time I switch from Win to DOS development? There has to be a better way! gjr
-
Does any one know of an easy way to maintain seperate Visual Studio "include file profiles" and quickly switch between them? (Something like a user defined "Platform"?. I use VS to develop both Win32/MFC apps and MS-DOS 16 bit apps and they have completely different include/lib/prog directory locations. At the moment I have to run a batch file to modify the VS registry entries every time I switch from Win to DOS development? There has to be a better way! gjr
You can make a batch file that sets your INCLUDE and LIB paths, then runs msdev with the /USEENV switch. That makes the IDE use the environment variables instead of the directores set in the Options. --Mike-- http://home.inreach.com/mdunn/ #include "witty_sig.h" :love: your :bob: with :vegemite: and :beer:
-
You can make a batch file that sets your INCLUDE and LIB paths, then runs msdev with the /USEENV switch. That makes the IDE use the environment variables instead of the directores set in the Options. --Mike-- http://home.inreach.com/mdunn/ #include "witty_sig.h" :love: your :bob: with :vegemite: and :beer:
-
You can make a batch file that sets your INCLUDE and LIB paths, then runs msdev with the /USEENV switch. That makes the IDE use the environment variables instead of the directores set in the Options. --Mike-- http://home.inreach.com/mdunn/ #include "witty_sig.h" :love: your :bob: with :vegemite: and :beer:
Michael Many thanks. This is much more flexible than my registry hacks. It works a treat as I use LNKs to run different projects in any case. Just goes to show one should always check out a program's command line options before complaining about lack of flexibility. By the way, does anyone know if VS .NET is going to be more flexible in handling project specific settings?? Perhaps even allowing you to define editor color settings for ASM files?? Define a color for virtual spaces?? (The whole VS IDE and editor seems to be several generations behind such tools as Ed for Windows and Codewright in these areas.) Gary