File Menu

Option	Description
	Opens the Start New Project Wizard, which you can use to create a new project. You can also use this wizard to import files from other sources. Click on the arrow to the right to show a list of different wizards that you can use to import a variety of file types into the project. You can also choose to create a new project or import from source control. See Creating a Project and Importing.
	Opens the Add File dialog, which you can use to add a variety of files to your project.
	Opens a dialog, which lets you open any type of file supported by Flare.
	Click the face of the button to save changes to the active file. You can also select an option from the submenu. Save Saves changes to the active file. Save All Saves changes to all of the open files. Save As Opens the Save As dialog, which lets you save the active file under a different name and/or file type and to a particular location. The new file is then displayed in the editor. Save To Opens the Save As dialog, which lets you save the active file under a different name and/or file type and to a particular location. The new file is not automatically displayed in the editor. Save As Template Opens the Save as Template dialog, which lets you save a copy of the active file as a template. When you create a new file of the same type in the future, you can select your template file as a starting point for the new file. See Creating Templates. Save As Contribution Template Opens the Save as Contribution Template Wizard, which you can use to create templates for others to use. See Creating and Sending Contribution Templates.
	Click the face of the button to open the Print dialog and send a file to a printer. You can also select an option from the submenu. Print Opens the Print dialog, which lets you send a file to a printer. Make sure that the item that you want to print is selected. For example, if you want to print a topic from the online Help, first click somewhere inside the topic so that it is the active element in the interface. Print Preview Opens the Print Preview dialog, which lets you see how a document looks before you send it to a printer. Make sure that the item that you want to preview is selected. For example, if you want to preview a topic from the online Help, first click somewhere inside the topic so that it is the active element in the interface.
	Click the face of the button to create a temporary copy of the active file. You can also select an option from the submenu. Send to Backups Creates a temporary copy of the file that is open and active in the interface (not files that you select in the Content Explorer, Project Organizer, or File List window pane). The file is placed in the Backups window pane.See Backing Up Files. Clear the "Backups Folder" Removes all temporary backup files from the Backups window pane. See Clearing the Backups Folder. Example You might use this feature, for example, if you want to make some changes to a file but are not certain if you will want to keep them when you are finished. Therefore, you can make a backup of the file in question. When you are finished making your changes, you might decide that you prefer the file the way it was. If so, you can quickly roll back to the backup file, which overwrites the changes that you made.
	Opens the Properties dialog for the selected item.
	Click the arrow and choose from the following. The options shown are different, depending on which source control provider your project is bound to. Import Project Opens the Import From Source Control Wizard, which lets you create a new project by importing an existing project that is located in a source control application. You will see this option for all source control providers. See Importing a Project From Source Control. Add Opens the Check In dialog, which lets you add the selected files to the integrated source control application. When working in a project that is connected to source control, there may be occasions when you have files in your local copy of the project that are not yet part of the source control copy. For example, when you add a new topic in your local copy of the project, that file will not be included in the source control copy of the project until you add it. You will see this option for all source control providers See Adding Files to Source Control. Check In Opens the Check In dialog, which lets you check files into source control. When you are finished editing files, you can check them in to source control. Checking in a file overwrites the old copy of the file in the database with the new one from your local machine. Even if others are not working on a file, it is a good idea to periodically check in files for a backup in source control. You will see this option if your project is bound to Microsoft Team Foundation Server. See Checking In, Committing, and Submitting Source Control Files. Commit Opens the Commit dialog, which lets you commit files into source control. When you are finished editing files, you can commit them to source control. If you are working with Git, committing a file adds your changes to the local database. When you are ready to add your local commits to the remote repository, you can push these files to the remote. If you are working with Subversion, committing a file overwrites the old copy of the file in the source control database with the new one from your local machine. You will see this option if your project is bound to Git or Subversion. See Checking In, Committing, and Submitting Source Control Files. Submit Opens the Submit dialog, which lets you submit files into source control. When you are finished editing files, you can submit them to source control. Submitting a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically submit files so that you have a backup in source control. You will see this option if your project is bound to Perforce Helix Core. See Checking In, Committing, and Submitting Source Control Files. Check Out Opens the Check Out dialog, which lets you check out files from source control. When you need to work on any of the Flare project files, you can check them out. Checking out files means to copy the latest source control files to your local Flare project and remove the "Read Only" designation from them so that you can edit the files. A red check mark is displayed next to each file that is checked out. You will see this option if your project is bound to Microsoft Team Foundation Server or Helix Core. See Checking Out Source Control Files. Lock Opens the Lock dialog, where you can select files to lock. If your project is bound to Subversion, you can steal locks from another user's locked files. When you are working, you may want to lock the files you have modified. Locking a file does not prevent other users from modifying the file. However, no one else can commit a file that you have locked until you unlock the file. If your project is bound to Subversion, you can steal a lock from another user if you need to commit a locked file while they are working on it. Likewise, another user can steal a lock on a file you have locked. You will see this option if your project is bound to Helix Core or Subversion. See Locking Files. Unlock Opens the Unlock dialog, where you can select files you want to unlock. If you have locked a file, you should unlock it when you are done modifying it. Other users can modify the file while you have it locked, but they cannot submit a locked file until you unlock it. To help prevent file conflicts and make sure that everyone on your team has the most current version of the file, you should unlock and submit the file when you are finished working on it. You will see this option if your project is bound to Helix Core or Subversion. See Unlocking Files. Get Latest Version Opens the Get Latest Version dialog, which lets you "get" files from source control. After you bind a Flare project to a source control application, you can get the latest version of any of the source control files. When you do this, you are copying the most current files stored in the source control application to your local Flare project without necessarily checking out the files. This means that the "Read Only" designation will remain associated with the files until you check them out. See Updating or Getting the Latest Version of Source Control Files. You will see this option if your project is bound to Microsoft Team Foundation Server or Helix Core. Update Opens the Get Latest Version dialog, which lets you update files from source control. After you bind a Flare project to Subversion, you can update any of the source control files. When you do this, you are copying the most current files stored in Subversion to your local Flare project. You will see this option if your project is bound to Subversion. See Updating or Getting the Latest Version of Source Control Files. Undo Check Out Opens the Undo Check Out dialog, which lets you reverse the check-out of the files. If you have files checked out from source control but do not want them checked out anymore, you can use the "Undo Check Out" option instead of checking in the files. You will see this option if your project is bound to Microsoft Team Foundation Server. See Reverting or Undoing a Checkout of Source Control Files. Revert Opens the Revert dialog, which lets you return files to their last known state. If you have modified files from source control but do not want to keep your modifications, use the "Revert" option instead of committing the files. While committing the file would save changes to source control, reverting a file returns it to its previously committed state and does not commit any of your new changes to source control. When reverting changes made in Git, you only revert changes to the file on the branch you are currently editing. If you have a file that resides on multiple branches, copies of the file on other branches are preserved. You will see this option if your project is bound to Git, Helix Core, or Subversion. See Reverting or Undoing a Checkout of Source Control Files. Show Differences Opens a window pane that lets you view the content and code differences for files. If you select a single file and choose this option, the differences between the local version of the file and the source control version of the file are shown. If you select two files and choose this option, the differences between those two files are shown. You will see this option for all source control providers. See Viewing Differences in Source Control Files. View History Opens the History dialog, which lets you view the history of a particular source control file, including all of the occasions when the file has been checked in. You can then use the dialog to view the differences between older versions of the file or roll back to a particular version. You will see this option for all source control providers. See Viewing the History of Source Control Files and Rolling Back to an Earlier Version of a File. Undelete Undeletes a file, allowing you to add it to source control. See Undeleting Source Control Files. You will see this option if your project is bound to Microsoft Team Foundation Server. Refresh Refreshes the window pane so that the latest information is shown. You will see this option for all source control providers. Network Settings Opens the Network Settings dialog, which lets you view and modify source control network settings from Flare. You will see this option if your project is bound to Git or Subversion. See Modifying Network Settings.
	Click the arrow to open a submenu, which lets you select various SharePoint options for the selected file(s). See SharePoint Integration. Check In Opens the Check In dialog, which lets you check files into SharePoint. When you are finished editing files, you can check them in to SharePoint. See Checking In SharePoint Files. Check Out Opens the Check Out dialog, which lets you check out files from SharePoint. See Checking Out SharePoint Files. Undo Check Out Opens the Undo Check Out dialog, which lets you reverse the check-out of the files. See Undoing a Check-Out of SharePoint Files.
	Click the face of the button to close the active file. You can also select an option from the submenu. Close Closes the active file. Close Project Closes the current project, but the application itself does not close.
	Displays a list of recently opened projects. You can select one from the list to open it. You can also remove projects from the list of recently opened projects, which lets you keep the list shorter and more manageable. When you use this feature, the project is merely removed from the list, but the actual project is not deleted.
	This option is found in the File menu. Displays a list of recently opened files. You can select one from the list to open it. You can also remove files from the list of recently opened files, which lets you keep the list shorter and more manageable. When you use this feature, the file is merely removed from the list, but the actual file is not deleted.
	Opens the Options dialog, which lets you set various global options. For more details, see Options Dialog.
	Closes the application.

Opens the Start New Project Wizard, which you can use to create a new project. You can also use this wizard to import files from other sources. Click on the arrow to the right to show a list of different wizards that you can use to import a variety of file types into the project. You can also choose to create a new project or import from source control. See Creating a Project and Importing.

Opens the Add File dialog, which you can use to add a variety of files to your project.

Opens a dialog, which lets you open any type of file supported by Flare.

Click the face of the button to save changes to the active file. You can also select an option from the submenu.

Save Saves changes to the active file.
Save All Saves changes to all of the open files.
Save As Opens the Save As dialog, which lets you save the active file under a different name and/or file type and to a particular location. The new file is then displayed in the editor.
Save To Opens the Save As dialog, which lets you save the active file under a different name and/or file type and to a particular location. The new file is not automatically displayed in the editor.
Save As Template Opens the Save as Template dialog, which lets you save a copy of the active file as a template. When you create a new file of the same type in the future, you can select your template file as a starting point for the new file. See Creating Templates.
Save As Contribution Template Opens the Save as Contribution Template Wizard, which you can use to create templates for others to use. See Creating and Sending Contribution Templates.

Click the face of the button to open the Print dialog and send a file to a printer. You can also select an option from the submenu.

Print Opens the Print dialog, which lets you send a file to a printer. Make sure that the item that you want to print is selected. For example, if you want to print a topic from the online Help, first click somewhere inside the topic so that it is the active element in the interface.
Print Preview Opens the Print Preview dialog, which lets you see how a document looks before you send it to a printer. Make sure that the item that you want to preview is selected. For example, if you want to preview a topic from the online Help, first click somewhere inside the topic so that it is the active element in the interface.

Click the face of the button to create a temporary copy of the active file. You can also select an option from the submenu.

Send to Backups Creates a temporary copy of the file that is open and active in the interface (not files that you select in the Content Explorer, Project Organizer, or File List window pane). The file is placed in the Backups window pane.See Backing Up Files.
Clear the "Backups Folder" Removes all temporary backup files from the Backups window pane. See Clearing the Backups Folder.

Example You might use this feature, for example, if you want to make some changes to a file but are not certain if you will want to keep them when you are finished. Therefore, you can make a backup of the file in question. When you are finished making your changes, you might decide that you prefer the file the way it was. If so, you can quickly roll back to the backup file, which overwrites the changes that you made.

Opens the Properties dialog for the selected item.

Click the arrow and choose from the following. The options shown are different, depending on which source control provider your project is bound to.

Import Project Opens the Import From Source Control Wizard, which lets you create a new project by importing an existing project that is located in a source control application.

You will see this option for all source control providers.

See Importing a Project From Source Control.
Add Opens the Check In dialog, which lets you add the selected files to the integrated source control application.

When working in a project that is connected to source control, there may be occasions when you have files in your local copy of the project that are not yet part of the source control copy. For example, when you add a new topic in your local copy of the project, that file will not be included in the source control copy of the project until you add it.

You will see this option for all source control providers

See Adding Files to Source Control.
Check In Opens the Check In dialog, which lets you check files into source control.

When you are finished editing files, you can check them in to source control. Checking in a file overwrites the old copy of the file in the database with the new one from your local machine. Even if others are not working on a file, it is a good idea to periodically check in files for a backup in source control.

You will see this option if your project is bound to Microsoft Team Foundation Server.

See Checking In, Committing, and Submitting Source Control Files.
Commit Opens the Commit dialog, which lets you commit files into source control.

When you are finished editing files, you can commit them to source control. If you are working with Git, committing a file adds your changes to the local database. When you are ready to add your local commits to the remote repository, you can push these files to the remote.

If you are working with Subversion, committing a file overwrites the old copy of the file in the source control database with the new one from your local machine.

You will see this option if your project is bound to Git or Subversion.

See Checking In, Committing, and Submitting Source Control Files.
Submit Opens the Submit dialog, which lets you submit files into source control.

When you are finished editing files, you can submit them to source control. Submitting a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically submit files so that you have a backup in source control.

You will see this option if your project is bound to Perforce Helix Core.

See Checking In, Committing, and Submitting Source Control Files.
Check Out Opens the Check Out dialog, which lets you check out files from source control.

When you need to work on any of the Flare project files, you can check them out. Checking out files means to copy the latest source control files to your local Flare project and remove the "Read Only" designation from them so that you can edit the files. A red check mark is displayed next to each file that is checked out.

You will see this option if your project is bound to Microsoft Team Foundation Server or Helix Core.

See Checking Out Source Control Files.
Lock Opens the Lock dialog, where you can select files to lock. If your project is bound to Subversion, you can steal locks from another user's locked files.

When you are working, you may want to lock the files you have modified. Locking a file does not prevent other users from modifying the file. However, no one else can commit a file that you have locked until you unlock the file.

If your project is bound to Subversion, you can steal a lock from another user if you need to commit a locked file while they are working on it. Likewise, another user can steal a lock on a file you have locked.

You will see this option if your project is bound to Helix Core or Subversion.

See Locking Files.
Unlock Opens the Unlock dialog, where you can select files you want to unlock.

If you have locked a file, you should unlock it when you are done modifying it. Other users can modify the file while you have it locked, but they cannot submit a locked file until you unlock it. To help prevent file conflicts and make sure that everyone on your team has the most current version of the file, you should unlock and submit the file when you are finished working on it.

You will see this option if your project is bound to Helix Core or Subversion.

See Unlocking Files.
Get Latest Version Opens the Get Latest Version dialog, which lets you "get" files from source control.

After you bind a Flare project to a source control application, you can get the latest version of any of the source control files. When you do this, you are copying the most current files stored in the source control application to your local Flare project without necessarily checking out the files. This means that the "Read Only" designation will remain associated with the files until you check them out.

See Updating or Getting the Latest Version of Source Control Files.

You will see this option if your project is bound to Microsoft Team Foundation Server or Helix Core.
Update Opens the Get Latest Version dialog, which lets you update files from source control.

After you bind a Flare project to Subversion, you can update any of the source control files. When you do this, you are copying the most current files stored in Subversion to your local Flare project.

You will see this option if your project is bound to Subversion.

See Updating or Getting the Latest Version of Source Control Files.
Undo Check Out Opens the Undo Check Out dialog, which lets you reverse the check-out of the files.

If you have files checked out from source control but do not want them checked out anymore, you can use the "Undo Check Out" option instead of checking in the files.

You will see this option if your project is bound to Microsoft Team Foundation Server.

See Reverting or Undoing a Checkout of Source Control Files.
Revert Opens the Revert dialog, which lets you return files to their last known state.

If you have modified files from source control but do not want to keep your modifications, use the "Revert" option instead of committing the files. While committing the file would save changes to source control, reverting a file returns it to its previously committed state and does not commit any of your new changes to source control. When reverting changes made in Git, you only revert changes to the file on the branch you are currently editing. If you have a file that resides on multiple branches, copies of the file on other branches are preserved.

You will see this option if your project is bound to Git, Helix Core, or Subversion.

See Reverting or Undoing a Checkout of Source Control Files.
Show Differences Opens a window pane that lets you view the content and code differences for files. If you select a single file and choose this option, the differences between the local version of the file and the source control version of the file are shown. If you select two files and choose this option, the differences between those two files are shown.

You will see this option for all source control providers.

See Viewing Differences in Source Control Files.
View History Opens the History dialog, which lets you view the history of a particular source control file, including all of the occasions when the file has been checked in. You can then use the dialog to view the differences between older versions of the file or roll back to a particular version.

You will see this option for all source control providers.

See Viewing the History of Source Control Files and Rolling Back to an Earlier Version of a File.
Undelete Undeletes a file, allowing you to add it to source control. See Undeleting Source Control Files. You will see this option if your project is bound to Microsoft Team Foundation Server.
Refresh Refreshes the window pane so that the latest information is shown. You will see this option for all source control providers.
Network Settings Opens the Network Settings dialog, which lets you view and modify source control network settings from Flare.

You will see this option if your project is bound to Git or Subversion.

See Modifying Network Settings.

Click the arrow to open a submenu, which lets you select various SharePoint options for the selected file(s). See SharePoint Integration.

Check In Opens the Check In dialog, which lets you check files into SharePoint. When you are finished editing files, you can check them in to SharePoint. See Checking In SharePoint Files.
Check Out Opens the Check Out dialog, which lets you check out files from SharePoint. See Checking Out SharePoint Files.
Undo Check Out Opens the Undo Check Out dialog, which lets you reverse the check-out of the files. See Undoing a Check-Out of SharePoint Files.

Click the face of the button to close the active file. You can also select an option from the submenu.

Close Closes the active file.
Close Project Closes the current project, but the application itself does not close.

Displays a list of recently opened projects. You can select one from the list to open it. You can also remove projects from the list of recently opened projects, which lets you keep the list shorter and more manageable. When you use this feature, the project is merely removed from the list, but the actual project is not deleted.

This option is found in the File menu.

Displays a list of recently opened files. You can select one from the list to open it. You can also remove files from the list of recently opened files, which lets you keep the list shorter and more manageable. When you use this feature, the file is merely removed from the list, but the actual file is not deleted.

Opens the Options dialog, which lets you set various global options. For more details, see Options Dialog.

Closes the application.