Robert,
>
> 1. What's the ETA on this? (week or month?)
>
I believe I'll have an ETA available next week.
>
> 2. Will it include support for the Crystal Reports Sybase drivers as well?
>
A few words to the new "SB5 Merge Module" compiler technology (Developer
Edition only). We can import (configurable) Windows Installer merge modules
(.msm) and compile native .msi runtime files for SetupBuilder 5 now.
So if the Crystal merge modules support Sybase drivers then you can also add
this to your setup.exe. In this case, support for the Sybase drivers is
included in the reportengine merge module.
>
> 3. How will it work in first getting the latest service pack from
> Crystal - meaning, do you install from CD, then get a service pack, and
> then run the Setup Builder?
>
We are using the original Crystal merge modules (SP1 dated 3/8/2006). You
can download the latest .msm, add the SB5 runtime include script and compile
your SetupBuilder 5 project.
BTW, if SP2 comes out, download the new merge modules and recompile your
project.
> 4. Is the SB build script smart enough to get rid of what you don't
> want/use - ie: the Design Component.
Yes. SB5 will support configurable merge modules. So, if you don't need,
say, BTRIEVE driver support, just disable this. And if you don't need
support for the Designer Control (another 15 MB of overhead), don't include
the designtime merge module.
> 5. Any idea what the footprint size will be when it is done, for just
> regular CR XI Viewer support, with export, with Sybase, no design
> components.
It depends on the merge module. The reportengine and runtime merge modules
are 58 MB, so if you need both merge modules, the overhead will be ~58 MB
(1,000+ files).
Friedrich
--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
+1.954.252.3910
"point. click. ship" - that's SetupBuilder 5