MSBuild \ 12.0 \ bin \ Microsoft.Common.CurrentVersion.targets (3243.9): MSB4094 error

Question

After opening my VS Ultimate 2012 C # solution in VS Ultimate 2013 12.0.21005.1REL I get the following warning:

Warning 1 Conflicts were found between different versions of the same dependent assembly. Set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190 . Energyms

I follow the instructions on the Microsoft link. Then I edited the csproj file, adding the following line:

<AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects> 

When I create the solution again, I get the following error:

The error list "app.config; obj \ x86 \ Debug \ EnergyMS.csproj.EnergyMS.exe.config" is an invalid value for the "ConfigFile" task "GenerateApplicationManifest" task. Unable to pass multiple items to a parameter of type "Microsoft.Build.Framework.ITaskItem". Energyms

Output Window:

C: \ Program Files (X86) \ MSBuild \ 12.0 \ Bin \ Microsoft.Common.CurrentVersion.targets (3243.9): error MSB4094: "app.config; obj \ x86 \ Debug \ EnergyMS.csproj.EnergyMS.exe. config "is an invalid value for the" ConfigFile "task" GenerateApplicationManifest "task. Unable to pass multiple items to a parameter of type "Microsoft.Build.Framework.ITaskItem".

I saw similar topics in the forum, but I do not understand the problem.

Can someone help me understand the problem?

Thanks.

Answer 1

I found that if you disable the "Enable ClickOnce security settings" option in the properties of an executable project, the error will disappear. Now I have to find out what needs to be done to enable this option again so that I can click once to deploy my WPF application.

Answer 2

There was a similar message, and after doing a search on the Internet, I found " Conflicts found between different versions of the same dependent assemblies "

Shows how easy it is to identify a vulnerable assembly.

That evening I drew up a project in which I played, and they gave me the following warning.

Conflicts were found between different versions of the same dependent assembly. Set the AutoGenerateBindingRedirects property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190 .

Given that in this project there are about 50 links to projects that are not particularly useful. Instead of catching fish through a solution, trying to identify intruders manually, there is an easy way to get the compiler to send more information.

• In Visual Studio 2013, go to Tools> Options.
• Select Project and Solutions> Build and Run.
• Find the drop-down multi-page version of the MSBuild project build. Here you can configure MSBuild to provide you more information. By default, it will be set to Minimum. Change it to 'Details.
• Restore and view the output window. Copy everything into notepad and find the warning message that should tell you which assemblies you need to see.

I found that I need to update several Prism assemblies in another project:

Found associated file ".... \ bin \ Debug \ Microsoft.Practices.Prism.Mvvm.xml". This link is not "CopyLocal" because it contradicted another link with the same name and lost the conflict. ImageRuntimeVersion for this link is "v4.0.30319".

Answer 3

I had "... is an invalid value for the" ConfigFile "parameter of the" GenerateApplicationManifest "task.

I decided to edit the .csproj file from my project and included the below <PropertyGroup> :

 <AutoGenerateBindingRedirects>false</AutoGenerateBindingRedirects> 

And now everything is working fine.

Answer 4

I tried to add this as a comment, but I didn’t have a reputation. The solution known so far is to disable the ClickOnce security feature for the project in VS. I want to add something to this as the reason for this setting. What happened in my project was that the solution was built using MSBuild and the ClickOnce security feature was enabled. At first it was successfully built, but my teammate noticed a certificate that was generated. He thought it once again and deleted it. Since then, the assembly of the project began with the abandonment of MSBuild. Therefore, I assume that if you save the certificate as is and create a project with ClickOnce enabled, you should not see the problem.

Answer 5

Oddly enough, the ClickOnce security setting is disabled for me. But I asked myself - what can be done if this parameter should be left "on" or in the "checked" state? Guess what helped in my case ... removing unused links! Just click RMB on the project in the solution explorer, select the project properties, and in the "Links" section you will see unused links and voila!

Hope this helps someone, it worked for me.

Answer 6

to all Xamarin users:
I also had an error message:

The error list "app.config; obj \ x86 \ Debug \ EnergyMS.csproj.EnergyMS.exe.config" is an invalid value for the "ConfigFile" task "GenerateApplicationManifest" task. Unable to pass multiple items to a parameter of type "Microsoft.Build.Framework.ITaskItem". Energyms

and I work with VS and Xamarin.Forms . I tried to prepare my iOS application for shipping to the store and suddenly ran into a problem (only with iOS project, Android WP was still working). I never changed the settings on the security tab (I think the settings were changed "in the background" according to my steps in order to prepare the application for sending). However, unchecking the "Activat ClickOnce Security Settings" checkbox on the security tab in my iOS project also solved my problem. Then I searched the Internet for any world (word) error message and found this message. Since this publication does not have a Xamarin -tag, I also post here ...

Answer 7

The best way to get all your builds and version number is through this app I found on Github.

Asmpy