Maybe it is just me, but from my point of view a metadata reader/writer should be able to reconstruct the original format. If size isn't available in the original format that means that in this scenario this size isn't required in the target format either. So, even though in the intermediate in-memory format, it may be awkward to have an unresolved type, in principle, this shouldn't prevent reconstruction of the original as long as no information from the original has been lost.
Anyway, it appears that this is not possible with Cecil, so I will have to write a resolver. Do you know if anyone has already written a resolver that can take a .config file with codeBase and bindingRedirect elements? Or do I have to implement this logic from scratch? Sam On Wednesday, 4 December 2013 12:58:04 UTC, Jb Evain wrote: > > That's a limitation in the assembly format. There's a few things that > you can't know without resolving the type. This is one of them. > > Cecil, or any metadata reader, needs to know the size to read and > write the constant. One could try to guess, but as any guesses, they > could be wrong. > > Jb > > > -- -- -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
