If one hosting startup class fails to execute, subsequent hosting startup classes defined in the assembly won't be executed.

This should probably have a low priority, because I don't know of any real assemblies that define multiple hosting startup classes.

However, the order of attributes returned by Assembly.GetCustomAttributes<HostingStartupAttribute>() can affect whether or not a hosting startup class gets executed or not. It should also be trivial to fix.