troubleshooting Question

Null assignment check still passes - why?

Avatar of steve-west
steve-west asked on
6 Comments1 Solution234 ViewsLast Modified:
Please consider this code

                       public System.Windows.Forms.Form PRIAMForm
                        FForm = value;

                        if (FForm != null)
                              FForm.Width = Width;
                              FForm.Left = 0;
                              FForm.Top = 0;
                              FForm.Height = Height;

// -----------------------------------

This is property accessor method for a component which has a Form as a property.

The following assignment AForm.PRIAMForm = null causes a Null exception - attempts are made to set the  FForm.Width property. Why, when the "  if (FForm != null)  " should prevent this?




Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 6 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 6 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros