[CONNECT Update 6] SDK is Available

As part of our SDK QA release process we run binary and source code compatibility checks against the prior SDK with the current version to ensure any breaking issues (signature or data type changes, c runtime version requirements, etc.) can be corrected or documented where necessary.  This SDK does not have any source or binary compatibility issues to report.  However, if you prefer (like us) to always err on the side of caution, we do try to provide prompt and synchronized (matching) product and SDK download release versions that "work best together".

HTH,
Bob

Are we going to have any major issues if we develop with the Update 6 SDK and install on an Update 5 Microstation?  Or the other way, Update 5 SDK on an Update 6 MicroStation?

With all of these updates, our users are running all sorts of different versions.

Unknown said:

When I noticed your reference to 8 days I had to take a double-take and wonder how 3 days turned into 8 days

I was not attempting irony  , but as an outsider I can only report what the Fulfillment Center tells me.  I think it's great that you can issue the SDK so promptly after the platform release.

I'm happy to report, by the way, that I was able to build all the Update 6 SDK examples with no problem.

Hi Jon,

Just a quick update (prior to SDK announcements) and a bit of information related to product build and release dates.

1. I will be posting SDK Update 5 and 6 announcement placeholders (today) and updating with general high-level SDK changes/difference update details vs. what the SDKHELP (MicroStationAPI.chm) "Whats new in the SDK" home page help topic (and Deprecated functions topic) that provide new and deprecated API function difference details.
2. I know time flies for all of us when we are busy, but when I noticed your reference to 8 days I had to take a double-take and wonder how 3 days turned into 8 days.  This can easily be explained.  The Fulfillment Center Product Download date (currently) is the date when an installer package is posted for Internal Review (and QA testing).  The actual Product Release date (and time) is only known by internal event notifications when changing the Fulfillment Center Visibility State between Internal Review and Public Availability and is not the date reflected as the Product Download date.  I can suggest the Public Availability date be used as the Product Download date seen, or if that would be too disruptive to existing metrics used elsewhere. 
3. On a similar (discrepancy) note. SDK Update 6 had a minor regression fixed in the .38 build. The installer version was promoted to .40 to keep the SDK and Product release versions synchronized without further delay of release testing and posting.  The SDK download version is .40 and SDK headers (used by the developer shell dynamic/smart title) reflect the SDK version as .38.  Due to improved product (quarterly) release cycle times this cosmetic discrepancy should already almost be in the past. :)

HTH,
Bob