Error 5 Unknown build error, 'Binary format of the specified custom attribute was invalid.' - by Eddy Tick

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 773406 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 12/4/2012 5:23:19 AM
Access Restriction Public


After upgrading my project to visual studio 2012 and retargeting to .Net 4.5 (was 3.5)
The startup project which is an WPF application gives the following error when compiling:

Output window:
3>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.WinFX.targets(268,9): error MC1000: Unknown build error, 'Binary format of the specified custom attribute was invalid.' 

Error	5	Unknown build error, 'Binary format of the specified custom attribute was invalid.' 	Birdseyeview.xd4all.Client

What can i do to solve this, tried converting again but did not help. The errors comes after retargeting the .Net version.

Update 1 is installed for Visual Studio 2012.
Sign in to post a comment.
Posted by Microsoft on 3/18/2013 at 5:10 PM
We have been unable to reproduce this error. Speaking with the msbuild team, the only suggestion for troubleshooting this is to build your project from the VS command line using msbuild.exe and specifying diagnostic verbosity. "/verbosity:diag". This will emit lots of build time logging, but you'll have to do the trial and error process of adding and removing projects to find the issue. The error alone doesn't allow us to determine the cause and we don't have a hisotry of this error to learn from. ------ We appreciate the feedback. However, we were not able to reproduce the issue based on the description. Attaching a simple repro example would help the investigation. Also, if it's easy to very the repro on more than one machine, this would rule out a configuration or environmental problem on the affected machine.    Thank you.
–WPF Team.
Posted by Eddy Tick on 12/18/2012 at 2:25 AM
Still no comment?, please update the status.
Recreated the project and after that again the same error.

Need a solution or a workaround.


Posted by Eddy Tick on 12/10/2012 at 4:23 AM

I hope this will be soon because i must update the solution to the new .Net version.
Even creating a new project and then copying the files from the old project to the new project gives this error.


Posted by Microsoft on 12/7/2012 at 1:36 AM
Hi Eddy,

Thanks for your reply. We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Eddy Tick on 12/6/2012 at 2:02 AM
When i create a simple project there is no problem.
The project that failes is a rather big project with 34 projects in 1 solution.
The only project that has this error is the main WPF application.
This has many third party references so difficult to share this with you.

Can you give any feedback on why this error is given.


Posted by Microsoft on 12/4/2012 at 9:31 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 12/4/2012 at 5:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(