C:\ESAL_REPO\g.gardinier_whisper\torqueProjects\Boeing_Visualization_T3D\My Proj
ects\ESALVis_Copy\buildFiles\VisualStudio 2010\projects>versionNumberHandler.pl
Build Param bad using default: FastDebug
Getting the version number from the file: ESALVis.rc
Found Version number: 69.298.0.3336
Release Build: 69
Debug Build: 298
Debug-Release Build: 0
Changlist: 3336
Getting pending revisions from perforce...
Finding biggest revision number to use...
Found Changelist number: 3338
Found Biggest Changelist number:
3338
Genrating new version number using Old Version #: 69.298.0.3336 Revision (Change
list)#: 3338 and Build: FastDebug
Generated new version number: 69.298.1.3338
Replacing version number 69.298.0.3336 in the file ESALVis.rc with 69.298.1.3338

Changing file version number to: 69.298.1.3338
Over-writing file with new version number...
Building the project with the new version number...
Setting environment for using Microsoft Visual Studio 2010 x86 tools.

Microsoft (R) Visual Studio Version 10.0.40219.1.
Copyright (C) Microsoft Corp. All rights reserved.

Invalid solution configuration

Use:
devenv  [solutionfile | projectfile | anyfile.ext]  [switches]

The first argument for devenv is usually a solution file or project file.
You can also use any other file as the first argument if you want to have the
file open automatically in an editor. When you enter a project file, the IDE
looks for an .sln file with the same base name as the project file in the
parent directory for the project file. If no such .sln file exists, then the
IDE looks for a single .sln file that references the project. If no such single
.sln file exists, then the IDE creates an unsaved solution with a default .sln
file name that has the same base name as the project file.

Command line builds:
devenv solutionfile.sln /build [ solutionconfig ] [ /project projectnameorfile [
 /projectconfig name ] ]
Available command line switches:

/Build          Builds the solution or project with the specified solution
                configuration. For example "Debug". If multiple platforms
                are possible, the configuration name must be enclosed in quotes
                and contain platform name. For example: "Debug|Win32".
/Clean          Deletes build outputs.
/Command        Starts the IDE and executes the command.
/Deploy         Builds and then deploys the specified build configuration.
/Edit           Opens the specified files in a running instance of this
                application. If there are no running instances, it will
                start a new instance with a simplified window layout.
/LCID           Sets the default language in the IDE for the UI.
/Log            Logs IDE activity to the specified file for troubleshooting.
/NoVSIP         Disables the VSIP developer's license key for VSIP testing.
/Out            Appends the build log to a specified file.
/Project        Specifies the project to build, clean, or deploy.
                Must be used with /Build, /Rebuild, /Clean, or /Deploy.
/ProjectConfig  Overrides the project configuration specified in the solution
                configuration. For example "Debug". If multiple platforms are
                possible, the configuration name must be enclosed in quotes
                and contain platform name. For example: "Debug|Win32".
                Must be used with /Project.
/Rebuild        Cleans and then builds the solution or project with the
                specified configuration.
/ResetAddin     Removes commands and command UI associated with the specified Ad
d-in.
/ResetSettings  Restores the IDE's default settings, optionally resets to
                the specified VSSettings file.
/ResetSkipPkgs  Clears all SkipLoading tags added to VSPackages.
/Run            Compiles and runs the specified solution.
/RunExit        Compiles and runs the specified solution then closes the IDE.
/SafeMode       Launches the IDE in safe mode loading minimal windows.
/Upgrade        Upgrades the project or the solution and all projects in it.
                A backup of these files will be created as appropriate.  Please
                see Help on 'Visual Studio Conversion Wizard' for more
                information on the backup process.

Product-specific switches:

/debugexe       Open the specified executable to be debugged. The
        remainder of the command line is passed to this
                executable as its arguments.
/useenv         Use PATH, INCLUDE, LIBPATH, and LIB environment variables
                instead of IDE paths for VC++ builds.

To attach the debugger from the command line, use:
        VsJITDebugger.exe -p <pid>
new version number:
Release Build: 69
Debug Build: 298
Debug-Release Build: 1
Changlist: 3338
Checking out & copying over the new exe and dll we created...


Copying other edited files...

-program debug database -

-resource file-
ESALVis.rc could not be found in revision number 3338
So it must not be checked out, checking it out...
Copied ESALVis.rc to C:/ESAL_REPO/g.gardinier_whisper\torqueProjects\Boeing_Visu
alization_T3D\My Projects\ESALVis\buildFiles\VisualStudio 2010\projects
        1 file(s) copied.

Finished With Script!

C:\ESAL_REPO\g.gardinier_whisper\torqueProjects\Boeing_Visualization_T3D\My Proj
ects\ESALVis_Copy\buildFiles\VisualStudio 2010\projects>versionNumberHandler.pl