Is it necessary to change the assemblyIdentity's version attribute in a manifest file?

Mar*_*ter 15 assemblies version manifest

In the following manifest, is it necessary to change the version attribute of the assemblyIdentity element if the assembly version is specified in the project (or, in my case, set as part of a MSBuild task)?

According to this Microsoft Connect page, it looks like the project's version number overrides the manifest's version number. Please correct me if I'm wrong...

<?xml version="1.0" encoding="utf-8"?>
<asmv1:assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1" 
                xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" 
                xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" 
                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <assemblyIdentity version="1.0.0.0" processorArchitecture="X86" name="MyApp.exe" type="win32"/>
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
    <security>
      <requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
        <requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
      </requestedPrivileges>
    </security>
  </trustInfo>
</asmv1:assembly>
Run Code Online (Sandbox Code Playgroud)

Help me Jon Skeet, you're my only hope... :)

Rob*_*ean 6

程序集信息的要点是唯一地标识您的应用程序到Windows及其组件.这类似于.NET使用filename + version + ID生成的+目标处理器arch来唯一地标识程序集.

如果您选择不更改它,那么Windows组件可能看不到您的应用程序的新版本与旧版本的唯一不同.

有关Application Manifests MSDN页面的更多信息.