Any word on a fix or a manual fix to get around this? Do I just
download the source and pre-pend a preprocessor flag to the build?
Code Fuzion
On Jun 24, 8:01 am, "Nate Kohari" <
nkoh...@gmail.com> wrote:
> Sorry about this, this is definitely a mistake on my part. I incorrectly
> assumed that the .NET 2.0 build would work for .NET 3.5 as well, but the
> extension method patch will screw things up. I'll be posting a .NET 3.5
> build soon to fix this problem.
>
> -Nate
>
> On Tue, Jun 24, 2008 at 3:25 AM, Michael Hart <
michael.hart...@gmail.com>
> wrote:
>
>
>
> > Hi kentaromiura,
>
> > I had this problem when using Ninject in a .NET 3.5 project - to
> > compile Ninject for .NET 3.5, you'll need to add the NET_35
> > preprocessor flag to build process of the Core project (and possible
> > the Test project too if memory serves).
>
> > There's a submitted issue already to make this a little easier to do (
> >
http://bugs.ninject.org/jira/browse/NINJECT-4
> > ), so track that for any changes.
>
> > Cheers,
>
> > Michael
>