# IT:AD:K2:HowTo:Create and Deploy a Project Package #



<callout type="Navigation" class="small">

* [[../|(UP)]]
{{indexmenu>.#2|nsort tsort}}


</callout>


## Scenario ##

Deploying via Visual Studio is nice -- but you won't have rights to deploy to Production from Visual Studio. You'll use a Deployment Package.


>You don't want to leave practising Deployment to Prod -- which varies from [[IT/AD/K2/Deployment/Dev/]] (ie Push) -- to last second.

## Process ##

#### PreRequisites ####


#### Steps ####

* In VS
* Create a Package
* Go to obj folder
* Copy `Package` folder and deliver to target server
* Edit the bat per the target environment, so that it uses the correct Environment variables. 
    * Open the targetXXX.msbuild file
    * scroll down to find  

> $(Environment) == "WDMS Int"

and replace `Test` in the script below

> set deployment_environment="WDMS Int"


* Open a console in that folder, as Admin
* Run the Script.
* Check for Errors.


#### Deployment Script ####

* PreReqs:
    * .NET 64 bit
    * Edit the `deployment_environment` value.
        * Give it value from.... TODO

Script:

    cls
    @echo off
    set version=0.6
    set deployment_environment="Test"
    set serviceBrokerDeployDIR="C:\Program Files (x86)\K2 blackpearl\ServiceBroker"
    set serviceBrokerBackupDIR="C:\"
    set workflowReleaseFolder=".\"

    @echo ========= Start BNZ workflow deployment =========
    @echo.
    @echo.
    @echo Preparing smart object and process deployment...
    choice /d y /t 10 > nul

    for /r "%workflowReleaseFolder%" %%a in (*.msbuild) do "C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\msbuild" "%%a" /p:Environment=%deployment_environment%

    @echo.
    @echo ========== Deployment completed ==========
    @echo.
    pause