Solved

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

Posted on 2009-04-07
7
363 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
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

How our DevOps Teams Maximize Uptime

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us. Read the use case whitepaper.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background What I'm presenting in this article is the result of 2 conditions in my work area: We have a SQL Server production environment but no development or test environment; andWe have an MS Access front end using tables in SQL Server but we a…
This article describes some techniques which will make your VBA or Visual Basic Classic code easier to understand and maintain, whether by you, your replacement, or another Experts-Exchange expert.
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
Get people started with the process of using Access VBA to control Excel using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Excel. Using automation, an Access application can laun…

751 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