Bug 37145 - ninject ArgumentNullException: Cannot be null Parameter name: member after upgrade to forms 2
Summary: ninject ArgumentNullException: Cannot be null Parameter name: member after up...
Status: RESOLVED INVALID
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.0.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-12-18 14:33 UTC by Andy
Modified: 2015-12-18 18:16 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED INVALID

Description Andy 2015-12-18 14:33:08 UTC
We have been using Ninject 3.1 on various projects including our Xamarin forms Android and iOS projects using Forms 1.5.1
however after upgrading to Xamarin 4 (forms 2) it errors with "System.ArgumentNullException: Cannot be null Parameter name: member" when trying to get a named string value, all other exports appear to work OK.

There is an issue raised for this already on Ninject for this issue (see https://github.com/onovotny/ninject/issues/6) however this was working successfully on all previous versions so it must be something xamarin have changed that has broken it.
Comment 1 Paul DiPietro [MSFT] 2015-12-18 18:16:35 UTC
Please refile an issue when a specific cause related to Forms is found, as there does not appear to be any specificity here related to the linked issue.