All user macros reported below for configuration '%s' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros.
All reference arguments passed to externally visible methods should be checked against null (Nothing in VB). If appropriate, ...
All selected projects are under source control. You may need to refresh the solution explorer view to show the correct state ...
All subsequent changes made to files involved in the global operation will be lost if you continue with the undo. Do you ...
All the projects you have selected must be on the same drive. The project %s is on a different drive, and cannot be bound ...
All user macros reported below for configuration '%s' are used before their definition, which can cause undesirable build ...
All users can view this document, digitally sign it, or change permissions. To decide who can access the document and for ...
All {0} servicing step groups have a PerformAfter attribute set, creating a circular dependency. No servicing step group ...
Allow multiple people to work in a workbook at the same time. The workbook should be saved to a network location where multiple ...
Allow users with earlier versions of Microsoft Office to read with browsers supporting Information Rights Management (IRM). ...