| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Whenever you search in PBworks, Dokkio Sidebar (from the makers of PBworks) will run the same search in your Drive, Dropbox, OneDrive, Gmail, and Slack. Now you can find what you're looking for wherever it lives. Try Dokkio Sidebar for free.

View
 

HowToUse

Page history last edited by ferventcoder 12 years, 1 month ago

How To Use UppercuT

 

Take the files/folders from the app folder (or from the zip file) and put them in the folder under the trunk (or a branch). It's very important for build.bat to be at the top level (for CI servers like CC.NET).  You can see from the example below that we have put the bat files in the top level folder. We also have our build folder at this level. There is where the brains of UppercuT live.  You can also see some of the output of the uppercut framework. There is a SolutionVersion.cs file (or SolutionVersion.vb if you are using VB). There is a build_output folder, where the build output is dropped. Then there is the code_drop folder where everything is getting packaged to (See WhyCodeDrop).  It is very likely you can take what is in the code_drop folder and deploy it from there.

 

 

 

Once you've brought over the framework, you will need to edit one file - settings\UppercuT.config.

 

 

  1. Drop in and add files to source control as described above.
  2. Understand why build.bat is at the top level.
  3. Edit the UppercuT.config file. This is found in the Settings folder.
  4. Set up custom build tasks in the build.custom folder if needed.
  5. Run build.bat from a command line and watch the output for BUILD SUCCEEDED.
  6. Open Visual Studio and add SolutionVersion.cs as a linked item (choose Add As Link) to every project and fix the errors in each local Assembly.cs file.
    1. Remove everything but the GUID in those Assembly.cs files.
    2. If you've added other things to the Assembly file, you can leave those as well (like the key path).

 

 

 

 

Comments (0)

You don't have permission to comment on this page.