Timeline for Why doesn't "object reference not set to an instance of an object" tell us which object?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 5, 2016 at 6:42 | comment | added | LiverpoolsNumber9 | blogs.msdn.microsoft.com/dotnet/2016/08/02/… FINALLY!!! | |
| Mar 19, 2013 at 20:37 | comment | added | sinelaw | Actually, in the case of null dereferencing this looks like a limitation in the way the CLR dereferences (thanks to Shahrooz Jefri's comment on the OP's question) | |
| Mar 19, 2013 at 20:33 | comment | added | sinelaw |
Agreed, and I'd say the same for KeyNotFoundException and many other annoyances...
|
|
| Feb 11, 2013 at 16:55 | comment | added | LiverpoolsNumber9 | The runtime has more information than it provides. Whatever useful info it has, it should provide. That's all I'm saying. In response to your question, why doesn't it know? If you know the answer to that you might be able to provide a better comment than you have. | |
| Feb 1, 2013 at 16:27 | comment | added | Will | How is the runtime supposed to know what is null though? | |
| Oct 26, 2012 at 7:32 | review | First posts | |||
| Oct 26, 2012 at 12:08 | |||||
| Oct 26, 2012 at 7:17 | history | answered | LiverpoolsNumber9 | CC BY-SA 3.0 |