You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a large ASP.NET web forms project which we recently added ninject too, after adding ninject to the project references and started to use it within the project, we noticed a lot of unrelated pages began to throw null reference exceptions on Page_Load and narrowed it down to FindControl being called, although the controls where in the markup with the correct ID and runat="server" set.
We have then removed ninject, and the problem goes away.
Does ninject alter the way in which events are fired or the way in which Page_Load is ran? Or does ninject overload FindControl?
The text was updated successfully, but these errors were encountered:
I have also noticed this issue, specifically with the Ninject.Web extension. I can successfully inject services into a Web Forms page but other, previously working and unchanged pages begin receiving null references from FindControl. Removing Ninject.Web fixes the problem.
@bizzehdee I don't have a solution for you but if I come across one I'll share.
We have a large ASP.NET web forms project which we recently added ninject too, after adding ninject to the project references and started to use it within the project, we noticed a lot of unrelated pages began to throw null reference exceptions on Page_Load and narrowed it down to FindControl being called, although the controls where in the markup with the correct ID and runat="server" set.
We have then removed ninject, and the problem goes away.
Does ninject alter the way in which events are fired or the way in which Page_Load is ran? Or does ninject overload FindControl?
The text was updated successfully, but these errors were encountered: