MSB3106: Assembly strong name "{0}" is either a path which could not be found or it is a full assembly name which is badly formed. If it is a full assembly name it may contain characters that need to be escaped with backslash(\). Those characters are Equals(=), Comma(,), Quote("), Apostrophe('), Backslash(\).
MSB3091: Task failed because "{0}" was not found, or the correct Microsoft Windows SDK is not installed. The task is looking ...
MSB3104: The referenced assembly "{0}" was not found. If this assembly is produced by another one of your projects, please ...
MSB3105: The item "{0}" was specified more than once in the "{1}" parameter. Duplicate items are not supported by the "{1}" ...
MSB3106: Assembly strong name "{0}" is badly formed. It may contain characters that need to be escaped with backslash(\). ...
MSB3106: Assembly strong name "{0}" is either a path which could not be found or it is a full assembly name which is badly ...
MSB3116: Application is marked to host in browser but is also marked for online and offline use. Please change your application ...
MSB3121: The file association element in the application manifest is missing one or more of the following required attributes: ...
MSB3126: The application is using file associations but is not marked for installation. File associations cannot be used ...
MSB3127: The default icon {0} could not be found in the current file references or is not part of the required download group. ...