Yang Zhang
2016-06-01 03:44:28 UTC
Hi,
I am working on edit existing string/icon resource in assembly. I use
mono.cecil to parse, edit the resource and save. Almost all the localized
resource files work fine, but only the English original resource file does
not work. The English project contains core logic code and references other
dlls (OtherDLL.dll), this may cause exceptions when using mono.cecil, the
test code and exception is below.
AssemblyDefinition assemblyDefinition = AssemblyDefinition.ReadAssembly(resourceFileName);// Some code
assemblyDefinition.Write(newFileName); // This will cause exception: "Failed to resolve assembly: 'OtherDLL, Version=10.1.1.1, Culture=neutral, PublicKeyToken=null'
The English dll is TestDll.dll under deployment directory, and other
localized resource dlls are TestDll.resources.dll under localized
directory, like /de/TestDll.resources.dll and /zh-CN/TestDll.resources.dll.
(other localized resource files could be well parse and save, but English
resource file failed.)
So how could I fix the issues? If it is the limitation or bug, could we use
another walk around method to achieve the goal?
Thanks in advance,
Yang
I am working on edit existing string/icon resource in assembly. I use
mono.cecil to parse, edit the resource and save. Almost all the localized
resource files work fine, but only the English original resource file does
not work. The English project contains core logic code and references other
dlls (OtherDLL.dll), this may cause exceptions when using mono.cecil, the
test code and exception is below.
AssemblyDefinition assemblyDefinition = AssemblyDefinition.ReadAssembly(resourceFileName);// Some code
assemblyDefinition.Write(newFileName); // This will cause exception: "Failed to resolve assembly: 'OtherDLL, Version=10.1.1.1, Culture=neutral, PublicKeyToken=null'
The English dll is TestDll.dll under deployment directory, and other
localized resource dlls are TestDll.resources.dll under localized
directory, like /de/TestDll.resources.dll and /zh-CN/TestDll.resources.dll.
(other localized resource files could be well parse and save, but English
resource file failed.)
So how could I fix the issues? If it is the limitation or bug, could we use
another walk around method to achieve the goal?
Thanks in advance,
Yang
--
--
--
mono-cecil
---
You received this message because you are subscribed to the Google Groups "mono-cecil" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mono-cecil+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
--
mono-cecil
---
You received this message because you are subscribed to the Google Groups "mono-cecil" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mono-cecil+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.