Hi all,
I was wondering where I could find descriptions of the current best practices regarding forward compatibility in VB applications. Another way to put this question could be "How can I ensure when building and packaging my applications that a new service pack is not going to come along and break my app?"
It does not seem reasonable to have to maintain separate distributions for each Service Pack, but if one of the dependencies is updated and it breaks the app, then what is one to do? I would have expected that whatever is updated in the SPs would certainly be backward-compatible, but this does not seem to be the case. Is there anything I could have possibly done in my VB app which would cause it to be compatible with only some particular version of some particular system DLL, etc? What is MS's policy on SPs and forward compaitibility? Is there some source of this type of info that I need to get acquainted with?
I was wondering where I could find descriptions of the current best practices regarding forward compatibility in VB applications. Another way to put this question could be "How can I ensure when building and packaging my applications that a new service pack is not going to come along and break my app?"
It does not seem reasonable to have to maintain separate distributions for each Service Pack, but if one of the dependencies is updated and it breaks the app, then what is one to do? I would have expected that whatever is updated in the SPs would certainly be backward-compatible, but this does not seem to be the case. Is there anything I could have possibly done in my VB app which would cause it to be compatible with only some particular version of some particular system DLL, etc? What is MS's policy on SPs and forward compaitibility? Is there some source of this type of info that I need to get acquainted with?
