Pull the tag "assemblyIdentity" up to level to be directly under "assembly". This fixes the "side by side configuration is incorrect" error when using this example in a project.
It's the first time I'm using a manifest. Therefore I might overlook why the manifest is as it is. But from what I understand there is no need to declare a dependency. Instead we want to declare the parameter like version for the current project.
With this change the manifest can just be copied and used right away.
Coverage remained the same at 66.783% when pulling 5fff253779084e380511ea3edbdd9972c569be8a on ChristianAEDev:master into 0d8781fedde91283df3f137ce4e8a5545fbc4a7f on josephspurrier:master.
Coverage remained the same at 66.783% when pulling 5fff253779084e380511ea3edbdd9972c569be8a on ChristianAEDev:master into 0d8781fedde91283df3f137ce4e8a5545fbc4a7f on josephspurrier:master.
Coverage remained the same at 66.783% when pulling 5fff253779084e380511ea3edbdd9972c569be8a on ChristianAEDev:master into 0d8781fedde91283df3f137ce4e8a5545fbc4a7f on josephspurrier:master.
Coverage remained the same at 66.783% when pulling 5fff253779084e380511ea3edbdd9972c569be8a on ChristianAEDev:master into 0d8781fedde91283df3f137ce4e8a5545fbc4a7f on josephspurrier:master.
Pull the tag "assemblyIdentity" up to level to be directly under "assembly". This fixes the "side by side configuration is incorrect" error when using this example in a project. It's the first time I'm using a manifest. Therefore I might overlook why the manifest is as it is. But from what I understand there is no need to declare a dependency. Instead we want to declare the parameter like version for the current project.
With this change the manifest can just be copied and used right away.