hmm now it seems to be working after restarting VS.NET after changing references.
its spuratic so will update after a few natural restarts to see if it goes away. On Tue, Oct 26, 2010 at 4:58 PM, Greg Young <[email protected]> wrote: > OK I rebuilt all of cecil with NET_3_5 and setting target of 3.5 > > Still getting issues using Mono.Cecil.dll from bin > > > On Tue, Oct 26, 2010 at 2:17 PM, Greg Young <[email protected]>wrote: > >> This works for me until I edit the project in monodevelop then re-open in >> Visual Studio :( Then I have to do it again. Also with VS.NET you cannot >> explicitly reference System.Core (its automatically added). >> >> Cheers, >> >> Greg >> >> >> On Tue, Oct 26, 2010 at 11:52 AM, Jb Evain <[email protected]> wrote: >> >>> On Tue, Oct 26, 2010 at 4:27 PM, Greg Young <[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. >>> >>> The real fix is to adjust the csproj file depending on the profile you >>> target. If you're targeting at least .net 3.5, you just have to >>> reference System.Core and to define NET_3_5 when building Cecil. And >>> bang, no more issue with the ExtensionAttribute. >>> >>> (Works by defining NET_4_0 if you target .net 4.0 too). >>> >>> -- >>> -- >>> mono-cecil >> >> >> >> >> -- >> 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 > -- Les erreurs de grammaire et de syntaxe ont été incluses pour m'assurer de votre attention -- -- mono-cecil
