making the cecil one public will cause clashes in the global alias, and I reckon you don't want to use explicit aliases...
Creating your own in your own assembly can work, I think the guys at DLR project did just that ( or IronRuby) It is also covered on one of their blogs. I am pretty confident in using Cecil, so applying it to itself was the easiest thing for me to do. Am 26.10.2010 um 17:02 schrieb Greg Young <[email protected]>: Gotta love non-determinism. Maybe I should just create one in my assembly? Maybe it would like that? Or make the cecil one public? Greg On Tue, Oct 26, 2010 at 10:57 AM, Johannes Rudolph < [email protected]> wrote: > Hi Greg, > > I can tell you some horror storries related to that... Basically the issue > is that the csc will use the first ExtensionAttribute definition it finds. > This causes a problem with Cecil, as the Attribute is declared internal. > Obviously making it public is not a solution either (clashes). > > So for some people there are no problems using Cecil the way it is, because > Csc will use the definition from System.Core. However, sometimes the cecil > one is picked and this behavior cannot be controlled (neither via msbuild or > csc command line). > > So the solution I ended up using was to use Cecil on itself to remove all > occurances of ExtensionAttribte incl. the definition. Id be happy to share > that small programm if thats ok with my employer. We have plans on OSS this > anyway. > > Regards, > Johannes > > Am 26.10.2010 um 16:37 schrieb Greg Young<[email protected]>: > > From looking around quickly I have a sneaking suspicion this is more > likely caused by something odd in project file (likely do to have started > off in monodevelop). Unless anyone has a better suggestion next step will be > to recreate project from scratch in VS > > On Tue, Oct 26, 2010 at 10:27 AM, Greg Young < <[email protected]> > [email protected]> wrote: > >> When using VS2010 with cecil for some weird reason everytime I open the >> project, I have to switch every project to 3.5 and then back to 4.0 or else >> I get a bunch of build errors after about extension attribute. Not sure if >> this is cecil related but its only happening on my projects referencing >> cecil (also get a warning that cecil defines its own extension attribute)... >> ideas? >> >> -- >> Les erreurs de grammaire et de syntaxe ont été incluses pour m'assurer de >> votre attention >> > > > > -- > Les erreurs de grammaire et de syntaxe ont été incluses pour m'assurer de > votre attention > > -- > -- > mono-cecil > > -- > -- > mono-cecil -- Les erreurs de grammaire et de syntaxe ont été incluses pour m'assurer de votre attention -- -- mono-cecil -- -- mono-cecil
