Hi Brian,

A new version with the automatic update mechanism is being rolled out in production environment (yay! :-) ). But with production environments special situations can occur :-).

We now had a single client PC that threw us an error "NullReferenceException". Using our own logging we could determine which piece of code went wrong:
- applying the update
- reading the last update result
- special handling depending on the last update result.

The first bit "applying the update" went OK. We know this because we examined the log output of AppLife Update. The update process ended with "SUCCESS" and each step during the update process seemed OK.

The second bit "reading the last update result" is done by (local var) updateController.ReadLastUpdateInformation(); This method gives us a "LastResult" object containing information about the last update. We were wondering, because our code now doens't check this explicitly, if there are situations that this "ReadLastUpdateInformation" method can return a "null" object. Our code further on depends on this object to read e.g. lastUpdate.Result.

We will modify our code to check if the ReadLastUpdateInformation returns a "null" value (best practice). But knowing if the method returns a "null" value will help us understand what can go wrong or in what situation(s).

Thx in advance!

Greetz,

Yves

Hi Adam,

Mmmm... strange.
The version used to build the package is 4.0.2.25. And the update is applied within the same Windows session. We only read the LastUpdate property after we applied an update to check whether it was a successful update or not.

Either way, our code is modified to check explicitly if the object is empty. If i get more information about what circomstances this error occurs and it doesn't apply for the situations described by you Adam I will post it here.

Greetz,

Yves