SP2?

  • Thread starter Thread starter Coderer
  • Start date Start date
C

Coderer

So, we've got a project that's almost ready to field, but it was built
on SP1. We installed, oh, 20-30 hot fixes (QFEs) since then, and we've
documented each one. I figure that since they're all older than SP2,
they should all be included, but we'd have to double-check and again
document. My primary concern is, what are the chances of an SP2
upgrade "breaking" our current system? What are the benefits? If I
had to tell my manager to update or not, how should I "sell" that?
Moreover, is it worth the hassle? If we do it and it hoses everything,
can I roll back to SP1-plus-tons-of-QFEs, or do I have to uninstall
everything and start from scratch? I know it's a lot of questions, but
any guidance at all would be greatly appreciated.
 
Hi Coderer. The main thing about installing the SP2 database over your
existing SP1 database is that it does not overwrite your SP1 DBs or
repositories. You will still be able to build existing SP1+QFE runtimes, so
if you want to preserve those runtimes, you can simply keep the old SLX
files intact. In this way, you can revert to your older runtimes no
problem. The SP2 database can also be uninstalled and reverted to your
previous development environment at any time.

The main advantage to upgrading your runtimes to SP2 is that they will then
be in line with the currently available security features and fixes that
were introduced in SP2. However, this can result in significant changes to
your configuration, including footprint changes, and in some limited cases
it can break existing functionality that depends on deprecated components or
drivers. You may need to invest a significant amount of time to determine
if an SP2 upgraded configuration would be beneficial to your business.

To see if upgrading to SP2 would help you, try installing the SP2 database,
then take an existing SLX file, upgrade it in Target Designer, re-run your
dependency checks, and verify all of your component settings. Then try
building and deploying your runtime and see if your device functions
correctly and your footprint is acceptable. If so, you're set. =)

--
Matt Kellner ([email protected])
STE, Windows Embedded Group

This posting is provided "AS IS" with no warranties, and confers no rights.
===============================
 
Back
Top