I use NAnt to build my code. But, a few days ago, my code started throwing System.Resources.MissingManifestResourceException. I found that the code worked fine when I built it from VS.NET.
I was using resources for localization in my project. And it turned out that the generated satellite assembly wasn’t being signed when I was building my code using NAnt. The <csc> task of NAnt wasn’t passing the “keyfile” information to al.exe (Assembly linker) – the tool that generates the satellite assembly. So, the satellite assembly was not being signed.
The workaround for this is to specify the keyfile to be used in the AssemblyKeyFileAttribute in the AssemblyInfo.cs file. I found this in the NAnt developers mailing list. They claim to have fixed this. I haven’t verified it.
3 Comments
July 9, 2007 at 8:04 am
??? just when i was thinking of switching to linux…darn…
July 10, 2007 at 9:49 am
@Lumeno: Hey, I don’t understand. How does my using NAnt stop you from switching to Linux? Go ahead, man. Take the plunge. Trust me, you’ll love it.
August 18, 2007 at 1:05 pm
hey, i finally did switch to linux… i’m using debian etch on my hp dv5127 laptop and everything’s fine except for the sound… the max volume is very low and the sound from the speakers is jarred… i tried using alsaconf and alsamixer but nothing seems to help… any ideas?