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

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
vaughnwhiteheadAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
abelConnect With a Mentor Commented:
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
 
abelCommented:
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
 
vaughnwhiteheadAuthor Commented:
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
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
abelCommented:
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
 
vaughnwhiteheadAuthor Commented:
Sorry, but I could not find where the 64 vs 32 bit settings are established.

0
 
vaughnwhiteheadAuthor Commented:
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
 
abelCommented:
> 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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.