Please understand that I know with some due diligence I could answer these questions myself, but don't have a SQL 2K8 environment set up for testing yet.
There have been major changes in the way dtexec loads design time and run time settings, as discussed here http://msdn.microsoft.com/en-us/library/bb500430.aspx
I've noticed in your current version of source code that there doesn't seem to be any way to control (or REapply) design time config loading (file or SQL), it just happens during pkg load.
1) is this correct?
You then use package.ImportConfigurationFile(configFile); to apply files and p.SetValue(pkgObj, s); to apply direct property values. No problem.
2) In 2K8, is there now a method for "reloading" the design times, or does this happen during the "execute" method with no control?
The new microsoft changes actually BREAK functionality when "Using the
/ConfigFile option to load run-time configurations for the same property values that are also set by design-time configurations".
Unfortunately, this is MY chosen method of package configuration for many reasons and this breaking change is troubling. I'm trying to figure out if using dtloggedexec is a way to avoid the "second load" FORCED on us by 2K8! I
couldn't believe some of the design decisions in 2K5 and am now pretty mystified that they've significantly CHANGED functionality without providing a switch to force the old behavior.
3) does dtlogged exec behave in the same way as the 2K8 dtexec when running under the 2k8 dts namespace?