Hi,
Jb Evain-2 wrote:
>
>> Actually I'm not sure about workarounds yet, except for checking all
>> custom
>> attributes in assembly...
>
> It's not about working it around. It's not a bug. The custom attribute
> contain a string representation of a type, you'd have to modify them
> yourself..
>
Actually I was talking about workarounds for my bug :) - no offence here.
But still I have some things unclear for me:
First, the original lines of code for the block:
............
.custom instance void
[nunit.framework]NUnit.Framework.ExpectedExceptionAttribute::.ctor(class
[mscorlib]System.Type) = (
01 00 78 4E 69 6E 6A 65 63 74 2E 43 6F 72 65 2E // ..xNinject.Core
...........
were following:
.......
[Test, ExpectedException(typeof(ActivationException))]
public void
MultipleMatchingConditionalBindingsWithNoDefaultBindingThrowsException()
{
.......
And it was natural for me(because I don't know specs probably :)) to think
that this will result in sth like TypeReference but not just string with
full name of the type.. but still that's about me..
So my question is if it is possible to somehow substitute such
"text"("..xNinject.Core.ActivationException, Ninject.Core,
Version=1.1.3498.33389, Cultu.....") occurances in dll binary (I tried to
use plain text search - but no results here)?
It seems a bit wrong, however, when I tried to enumerate methodDefinitions
and their CustomAttributes - the type of attribute parameter was string not
System.Type as I expected...
I am sorry for making such raw questions - it would be great if somebody
will point me out some reference material on the matter either..
--
View this message in context:
http://www.nabble.com/Weakening-strongly-typed-assembly-references-tp24750303p24755202.html
Sent from the Mono - Cecil mailing list archive at Nabble.com.
--~--~---------~--~----~------------~-------~--~----~
--
mono-cecil
-~----------~----~----~----~------~----~------~--~---
