Compile New Viewer: Difference between revisions

Latest revision as of 05:06, 15 October 2015

How to compile new viewer

1. Check out Catglobe source code.

2. Open command line change working directory to CatGlobeWeb\jmvc

3. Run command "js.bat catglobe\questionnaire_viewer\scripts\build.js". This command will compile all files in directory to make 2 production files for deploy to server:

+ catglobe/questionnaire_viewer/production.js

+ catglobe/questionnaire_viewer/production.css

4. Build Catglobe Solution.

in Default.aspx.cs debug mode is defined:
    #if DEBUG
     public const bool IsDebugMode = true;
    #else
         public const bool IsDebugMode = false;
   #endif
So in production the build will use the production files as compiled in place, no need to move them anywhere

5. Commit new files to bitbucket

@@ Line 1: / Line 1: @@
 <p style="text-align: center"><span style="font-size:large">'''How to compile new viewer'''</span></p>
-. Check out Catglobe source code.
+<span style="font-size:larger">1. Check out Catglobe source code.</span>
-. Open command line change working directory to CatGlobeWeb\jmvc
+<span style="font-size:larger">2. Open command line change working directory to CatGlobeWeb\jmvc</span>
-. Run command "js.bat catglobe\questionnaire_viewer\scripts\build.js". This command will compile all files in directory to make 2 production files for deploy to server:
+<span style="font-size:larger">3. Run command "js.bat catglobe\questionnaire_viewer\scripts\build.js". This command will compile all files in directory to make 2 production files for deploy to server:</span>
-&nbsp;+ catglobe/questionnaire_viewer/production.js
+<span style="font-size:larger">&nbsp;+ catglobe/questionnaire_viewer/'''production.js'''</span>
-&nbsp;+ catglobe/questionnaire_viewer/production.css
+<span style="font-size:larger">&nbsp;+ catglobe/questionnaire_viewer/'''production.css'''</span>
-. Build Catglobe Solution.
+<span style="font-size:larger">4. Build Catglobe Solution.</span>
-&nbsp;in Default.aspx.cs debug mode is defined:<br/>&nbsp;&nbsp;&nbsp; #if DEBUG<br/>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; public const bool IsDebugMode = true;<br/>&nbsp;&nbsp;&nbsp; #else<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; public const bool IsDebugMode = false;<br/>&nbsp;&nbsp; #endif<br/>&nbsp;So in production the build will use the production files as compiled in place, no need to move them anywhere
+<span style="font-size:larger">&nbsp;in Default.aspx.cs debug mode is defined:<br/>&nbsp;&nbsp;&nbsp; #if DEBUG<br/>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; public const bool IsDebugMode = true;<br/>&nbsp;&nbsp;&nbsp; #else<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; public const bool IsDebugMode = false;<br/>&nbsp;&nbsp; #endif<br/>&nbsp;So in production the build will use the production files as compiled in place, no need to move them anywhere</span>
-. Commit production.js and production.css to Bitbucker
+<span style="font-size:larger">5. Commit new files to bitbucket</span>
+[[Category:Deployment_guidelines]]