Open BerryDomi opened 1 month ago
Hi, this looks like a metadata reading error 🤔
If it is possible, please provide me with a compiled file I can use to reproduce the issue. If you do not want to share it publicly, you can provide it to me via email elektrokilldev@protonmail.com
Thanks in advance!
Hi, this looks like a metadata reading error 🤔
If it is possible, please provide me with a compiled file I can use to reproduce the issue. If you do not want to share it publicly, you can provide it to me via email elektrokilldev@protonmail.com
Thanks in advance!
sorry for the delay,i'll send you the compiled file right now.
Hey,
I took a look at the file you provided and this seems to be an issue with the file itself rather than dnSpy.
Taking a look at the raw metadata found in the file, it is clearly visible that these two fields do not have a signature defined. The offset to the signature data is set to 0 indicating no signature. This is invalid according to .NET metadata specification and suggests that there either was an issue when compiling the file or it was edited in some way which broke this metadata.
There is unfortunately nothing I can do in dnSpy to fix the issue during saveing. dnSpy is just reporting that these fields don't contain any signature defined in the metadata.
dnSpyEx version
6.5.1
Describe the Bug
a .net8.0 dll cannot save the module after using unmanaged type delegation, does the current version(6.5.1) of dnspy add support for this type?
How To Reproduce
using unmanaged type delegations.
Expected Behavior
successfully save modules of those using unmanaged type delegations.
Actual Behavior
failing at saving modules.
Additional Context
No response