Changes between Version 5 and Version 6 of FdoEnhancedVersionSupport
- Timestamp:
- Oct 18, 2007, 9:27:51 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FdoEnhancedVersionSupport
v5 v6 109 109 A provider is considered to be binary-compatible with the current FDO if the specified parts of the provider's !FeatureDataObjectsVersion match those of the current version of FDO. For example, if the !FeatureDataObjectsVersion has 2 parts, then these must match the 1st 2 parts of the current FDO's version. The following table provides some concrete examples: 110 110 111 '' 'Provider !FeatureDataObjectsVersion'''111 ''Provider !FeatureDataObjectsVersion'' 112 112 113 113 3 … … 125 125 4.1.0.0[[br]] 126 126 127 '' 'Provider !FeatureDataObjectsVersion'''127 ''Provider !FeatureDataObjectsVersion'' 128 128 129 129 3.0 … … 140 140 3.2.0.0[[br]] 141 141 142 '' 'Provider !FeatureDataObjectsVersion'''142 ''Provider !FeatureDataObjectsVersion'' 143 143 144 144 3.2 … … 155 155 3.3.0.0[[br]] 156 156 157 '' 'Provider !FeatureDataObjectsVersion'''157 ''Provider !FeatureDataObjectsVersion'' 158 158 159 159 3.1.0.1 … … 171 171 The 4th example is for illustration and would not likely happen in the real world. It is unlikely that versions as similar as 3.1.0.1 and 3.1.0.2 would be incompatible. 172 172 173 ==== !FdoProviderNameTokens====173 ===== !FdoProviderNameTokens ===== 174 174 175 175 This class will be modified to support the removing of version parts from a provider name. 176 176 177 '' '!ToString (new)'''177 ''!ToString (new)'' 178 178 179 179 This function converts this tokenize provider name back to a string:
