__VSPPROJECTUPGRADEVIAFACTORYFLAGS Enumeration
Specifies action to take with OnAfterUpgradeProject calls.
This enumeration has a FlagsAttribute attribute that allows a bitwise combination of its member values.
Namespace: Microsoft.VisualStudio.Shell.Interop
Assembly: Microsoft.VisualStudio.Shell.Interop.8.0 (in Microsoft.VisualStudio.Shell.Interop.8.0.dll)
Syntax
'Declaration
<FlagsAttribute> _
Public Enumeration __VSPPROJECTUPGRADEVIAFACTORYFLAGS
[FlagsAttribute]
public enum __VSPPROJECTUPGRADEVIAFACTORYFLAGS
[FlagsAttribute]
public enum class __VSPPROJECTUPGRADEVIAFACTORYFLAGS
[<FlagsAttribute>]
type __VSPPROJECTUPGRADEVIAFACTORYFLAGS
public enum __VSPPROJECTUPGRADEVIAFACTORYFLAGS
Members
| Member name | Description | |
|---|---|---|
| PUVFF_BACKUPSUPPORTED | Backup is supported.
All implementations that return either PUVFF_SXSBACKUP or PUVFF_COPYBACKUP should also return PUVFF_BACKUPSUPPORTED. This enables aggregated project systems to AND together capabilities. Visual Studio takes this to mean 'multiple projects support mutually exclusive backup types,' as differentiated from 'no backup options available.' |
|
| PUVFF_COPYBACKUP | Xcopy style backup supported. | |
| PUVFF_SXSBACKUP | Side-by-side backup supported. | |
| PUVFF_USE_ALT_BACKUP_LOCATION | By default, copy backup occurs in a subfolder of the solution. There are times where this is unwanted. In those cases UpgradeProject_CheckOnly can return PUVFF_USE_ALT_BACKUP_LOCATION. This defaults to using a subfolder under the user's default project location folder. This alternate location should be avoided if it is possible, as it presents more limitations regarding backup file name length. |
Remarks
COM Signature
From vsshell80.idl:
enum __VSPPROJECTUPGRADEVIAFACTORYFLAGS
{
PUVFF_SXSBACKUP = 0x00000020
,PUVFF_COPYBACKUP = 0x00000040
,PUVFF_BACKUPSUPPORTED = 0x00000080
,PUVFF_USE_ALT_BACKUP_LOCATION = 0x00000100
};
typedef DWORD VSPUVF_FLAGS;