R1/R2 Merge Modules And RDC-to-.NET Questions
Hello. I am in the process of updating our VB6-based product from using and distributing CR XI R1 merge modules to R2 merge modules so that it will run on computers running Windows Vista. I have 2 questions:
1. Does anyone know of any side-by-side installation issues with R1 and R2? It is likely that some users will have the CR XI R1 designer installed on the same machine that we will install our product -- using InstallShield to push out the R2 merge modules. We hope that installing our product with R2 merge modules will not affect the R1 design-time environment -- is this correct?
2. We anticipate updating our product to work with CR 2008, but realize this means wrapping a .NET CR assembly using COM Interop so that it will continue to work with our existing VB6-based product. We don't know if the CR 2008 .NET-based object model will expose interfaces with the same methods as in the VB6 RDC (craxdrt.dll) components. We have very simple use of RDC, for example instantiating "Report" objects and setting some formulas from within our code. Is there developer documentation available to explain migrating RDC-based applications to the .NET-based 2008 edition?
Thanks for any assistance.