How To duplicate applications
This topic explains how to duplicate Packflow applications, allowing concurrent installation on the same Packflow Site.
Packflow applications are, in first place, defined with a model file. This file contains an xml representation of every modeled object.
All these objects have Guids that must stay unique along a site instance, allowing to associate runtime objects with their modeling counterparts. Hence, duplicating an application can't be done by duplicating the model file or project.
These Guids, as some other properties, have to be made unique. Packflow Designer provides tools to duplicate applications easily while keeping model unicity.
Different duplication options allow to choose gradually between a simple model duplication and a full project copy with custom codes importation. When no option is checked, Designer will copy and make unique the model file only. Code customizations are not kept.
These options are available:
When checked, Designer will prompt to generate a new project from copied model, with all generated codes. File structure from source project is copied beforehand, excepted .csproj, crproj, and .custom.cs files.
|Since .csproj file is not kept, additional files and references not generated by Designer need to be included in project again. They are however present in the new project folder.|
When checked, Designer will also copy all .custom.cs files in the source project to the duplicate project, while doing a namespace replacement to match the new project's namespace.
Only files ending by .custom.cs are handled now. Other files you could have added need their namespaces adjusted. Custom aspx, svc files are not handled yet.
You may automate namespace renaming by ending non-generated C# files names with .custom.cs. This will make Designer process them.