= Improve Usability of Stationery in Perforce= == Summary == When I create a new Express project and reference stationery in Perforce, the project keeps the read-only settings from Perforce and gives error messages. Express should always create a new project with the appropriate read/write settings for a *new* project. == Detailed Description == We keep standalone stationery in Perforce b/c this is the easiest location for local and remote workers to access. Currently, I need to check out the stationery just to create a new Express project. This makes no sense--I'm not changing the stationery--and it's bad practice. Express should create a new project and set the files that must be changed, such as the stationery.manifest, to write-access. Currently, if I create a new project with stationery that I did NOT check out, I get the following error message: An error occurred while creating the project. The directory is not empty. I navigate to the project directory on my machine and there is a wrp file and other folders and files. I open the wrp file in Express and get the message that the stationery has changed--it has not. When I syncrhonize to the stationery I get the error message: An error occurred synchronizing the project. Access to the path \stationery.manifest is denied. == Use Cases == Use case is anyone using Perforce or other source control systems to keep actively used stand-alone stationery. ---- <>