Solved

visual net 2005 warning about referenced assembly & Error regarding "Unable to write manifest"

Posted on 2009-04-07
7
358 Views
Last Modified: 2013-11-26
Greetings
A sudden warning and error appeared today.  The warning is: warning 15 Referenced assembly 'C:\Programming\ETPRoNet\ETProBankManager\bin\ETBankManager.dll' targets a different processor than the application.      

The error is: Error 14  Unable to write manifest 'obj\Release\ETPro.exe.manifest'. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. The file exists.

The real kicker is that if I load the project from my thumb drive I do NOT get any errors.  I copy the files to the machine and the warning and error appear.

Thanks
0
Comment
Question by:vaughnwhitehead
  • 4
  • 3
7 Comments
 
LVL 39

Expert Comment

by:abel
ID: 24088856
and I assume you tested for enough room on your harddrive and you emptied your %temp% dir already? The file itself (the path you refer to) is editable, ie. not in use by another process?
0
 

Author Comment

by:vaughnwhitehead
ID: 24088942
The only above item I hand not checked/performed was emptying the %temp% dir.  After doing this, the error is gone but the waring  "Referenced assembly 'C:\Programming\ETPRoNet\ETProBankManager\bin\ETBankManager.dll' targets a different processor than the application" is still present. I removed the reference and then added it again, but still get the message.

0
 
LVL 39

Expert Comment

by:abel
ID: 24088994
Glad the first bit went away. Sounds that you have a mixed 64 bit / 32 bit situation. Either the dll is 64 bit and your assembly is 32 bit, or the other way around. Can you check whether you (perhaps inadvertently) mixed versions?
0
Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

 
LVL 39

Accepted Solution

by:
abel earned 500 total points
ID: 24089286
Is the dll a non-.NET dll? I.e., non-managed? From this thread, I got it that that might be a reason for your trouble: http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/d7843bc7-3034-430d-9e46-60acd14c53a6/
0
 

Author Comment

by:vaughnwhitehead
ID: 24091460
Sorry, but I could not find where the 64 vs 32 bit settings are established.

0
 

Author Closing Comment

by:vaughnwhitehead
ID: 31567587
That was it.  The target CPU for the dll was (set to any CUUP.  I changed it to x86 and the problem went away.

Thanks again - I really appreciate the help.
0
 
LVL 39

Expert Comment

by:abel
ID: 24095298
> That was it.  The target CPU for the dll was set to any CUUP.
> I changed it to x86 and the problem went away.

Glad you found it. These errors can be tricky to solve sometimes if you don't know where to look.

> Sorry, but I could not find where the 64 vs 32 bit settings are established.
It wasn't that, as you have found out now, it was the dll.

Glad to have been of some help,

-- Abel --
0

Featured Post

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

A long time ago (May 2011), I have written an article showing you how to create a DLL using Visual Studio 2005 to be hosted in SQL Server 2005. That was valid at that time and it is still valid if you are still using these versions. You can still re…
Since upgrading to Office 2013 or higher installing the Smart Indenter addin will fail. This article will explain how to install it so it will work regardless of the Office version installed.
Show developers how to use a criteria form to limit the data that appears on an Access report. It is a common requirement that users can specify the criteria for a report at runtime. The easiest way to accomplish this is using a criteria form that a…
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now