SenseNet Project Installer

How it works

This is basically a package of various scripts used by my team creating and managing custom project installations. There are some batch scripts as previously used solution, but lately we replaced them with powershell scripts. It contains the following scripts for now:

• Create, start and stop IIS sites
• Setup host file
• Unzip archives
• Build solutions
• Install Sense/Net site from source package
• Get latest from TFS
• Import/Export content and index populate Sense/Net site
• and some other custom scripts

Prerequisits

Prerequisits are mostly come from the scripts that are made for managing Sense/Net:

1. Microsoft SQL Server a. SQL Server Configuration Manager
2. Visual Studio
3. IIS
4. PowerShell (or obsolate batch scripts uses command line)
5. Environment settings

Powershell script modules:

• StartWebsiteAppPool: starts the site by the given parameter.

StartWebsiteAppPool.ps1 [SiteName]

• StopWebsiteAppPool: stops the site by the given parameter.

StopWebsiteAppPool.ps1 [SiteName]

• BuildSnSolution: builds the solution by the given parameter.

BuildSnSolution.ps1` -slnPath [Solution file path. It is .sln file]

• Create-IISSite: creates the application pool and the site. In the first parameter you need to set the application pool (same site name) and in the second parameter you need to set the site’s physical path on the hard drive.

Create-IISSite.ps1 [SiteName] [site’s physicalPath]

• GetLatestSolution: gets the latest version from the repository.

GetLatestSolution.ps1 -tfexepath [tf.exe physical path] –location [project source folder path]

• Import-Module: imports the project files to the repository.
• Export-Module: exports the project files from the repository.
• Index-Project: runs indexpopulation process.
• Init-Assemblies: copies the SenseNet dlls into /bin and /tools folders and edits the config files.
• init-functions: initialization functions.
• Initialization: initializes the script variables.
• Install-SenseNet: installs the sensenet.
• RemoveDemo: removse the default site from the SenseNet portal.
• SetHostFile: set in the web.config host attribute.
• Unzip: unzips the zip file (example: SenseNet package) to the destination folder.

unzip.ps1 -filename [zip file path] -destname [destination path]

• START: You can run it in different modes: ** fullinstall: runs sensenet install process.

Local install

If everything've set right, you can call the scripts simply with the following parameter:

START.ps1 fullinstall

Build server example steps

The same scripts that are used locally can be used with visual studio's build server.

1. Stop the site
2. Unzip the SenseNet package
3. Build the SenseNet solution
4. Install SenseNet
5. Copy DLLs to /bin and /tools folder
6. Get latest version
7. Build solution
8. Import contents to repository
9. Indexpopulation
10. Start the site

Known issues

There are some steps we've not fully automated yet. So some manual setups may required, such as:

• The plan was to use different json settings for different projects and/or environments, but only local settings work for now
• The script won't automatically map your Visual Studio version and its location which is needed to get latest tfs and solution build steps. You have to set tf.exe path properly in project-local.json's Tools.VisualStudio property
• Unziping archive script uses 7zip, the location for 7za.exe file needs to be set in project-local.json too
• If you use sql alias like MySenseNetContentRepositoryDatasource in default Sense/Net install, you have to set it manually before using the script or you have to set different Datasource in project-local.json
• Project references should be checked if they're matching the proper Sense/Net version.