Visual Studio 2003 Crystal Reports Merge Modules
I'm having lots of trouble with images.
I wonder if this could be the problem. The error said maybe merge
modules were missing and listed the 'old ones', so I added copies
of 'the old ones' from my vs2002 machine... if the new ones are
'there' I hope it's picking the right ones!
Quote:
> Thanks, I hope someone from Microsoft will read this and post the correct
> information in MSDN...the old Visual Studio.Net 2000 information is still
in
> there and that's likely to be confusing to people.
> Chuck
> > In addition to the changes that you noted (which I believe are all
> correct),
> > it appears that VC_CRT.msm and VC_STL.msm were replaced by
> > VC_User_CRT71_RTL_X86_---.msm and VC_User_STL71_RTL_X86_---.msm
> > respectively.
> > Wayne
> > > I've recently upgraded to Visual Studio.Net 2003 and it looks like the
> > > Crystal Reports Merge Modules required for deployment have changed
> > although
> > > I can't find the new requirements documented anywhere.
> > > My guess is this:
> > > - regwiz.msm has been replaced by crystal_reqwiz2003.msm (you still
> have
> > > to enter the license code into it the same as the old regwiz.msm)
> > > - VC_CRT.msm appears to be no longer needed...it disappeared from my
> > merge
> > > modules after I uninstalled VStudio 2000 and replaced with VStudio
2003
> > > - Ditto for VC_STL.msm
> > > - The following new merge modules have been added and I assume these
> > > replace the older versions in VStudio 2000:
> > > - Crystal_DatabaseAccess2003.msm
> > > - Crystal_DatabaseAccess_enu.msm
> > > - Crystal_Managed2003.msm
> > > - Crystal_regwiz2003.msm
> > > I haven't been able to find this documented anywhere, but I assume it
is
> > > correct...can anyone verify or confirm this?
> > > Chuck
