When I add an external folder to my project which is under source control, why are the source control options for that folder and it’s contents unavailable?
The adding of files to source control requires knowledge of every file independently and ‘External Folders’ are retrieved ‘on the fly’, SCC can not be used for External Folders. • I have an xsl processing instruction in an xml file, and this file is contained in a Spy project (.spp). XMLSpy® 2010 Enterprise Edition transforms the xml file using a different xsl file than that which is referenced in the processing instruction. Why is this? It is possible to set project settings in a Spy project. These settings will take precedence over those in an individual file. The project settings can be set on a project or folder level by right clicking on the project name or one of the virtual folders and selecting “properties”. If you select “Use this XSL” in the properties window of a project folder then this xsl will be used to transform any xml file contained within that folder regardless of whether or not one of the xml files contained within the project folder contains an xml processing instr
Related Questions
- When I add an external folder to my project which is under source control, why are the source control options for that folder and it’s contents unavailable?
- How does a project area affect the visibility of source control artifacts such as streams, workspaces or components?
- How to switch a project from the source control of SourceSafe to SourceAnywhere for VSS?
