Is anybody else using the VC++ merge modules that come with VS .NET 2003?
(e.g. VC_USER_CRT71_RTL_X86_---.MSM and his buddies)
I'm having trouble getting them to install the DLLs in the correct place. I whacked them into a Wise 4.2 project (along with the older VS .NET modules) and they install, but to the root of the drive not System32.
Took a look at them in Orca, they don't seem different to say VC_CRT.msm (for VC++ 7.0) but the older modules go straight into System32 while the newer ones aren't interested in anyhting but the root.
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
VC++ Merge Modules For .NET 2003
Started by
PARUK
, May 20 2003 10:51
5 replies to this topic
Posted 27 May 2003 - 08:30
I have the same problem with
VC_User_CRT71_RTL_X86_---.msm
VC_User_STL71_RTL_X86_---.msm
VC_User_CRT71_RTL_X86_---.msm
VC_User_STL71_RTL_X86_---.msm
Asaf Vishna[br]SmarTeam Corporation Ltd.[br]Email: AsafV@SmarTeam.com
Posted 27 May 2003 - 09:09
QUOTE |
I have the same problem with VC_User_CRT71_RTL_X86_---.msm VC_User_STL71_RTL_X86_---.msm |
Well at least it's not just me then. I guess Microsoft will get round to shipping better-behaved merge modules eventually, or tell us how to get round the problem. Major pain in the rear end until then
Posted 28 May 2003 - 08:47
I have found a message in the microsoft.public.platformsdk.msi Newsgroup
"Adam Semel" <asemel@online.microsoft.com> wrote in message news:<E0XCmi5HDHA.1636@cpmsftngxa06.phx.gbl>...
> Ok guys.. just went through the merge module again. There are two
> things
> wrong with them. The first is that you can't retarget the merge module like
> you could with the 2002 merge modules. The second (which is also the cause
> of the first) is that the merge modules have the wrong schema. We are using
> a 100 schema, which means we can't even manually fix the merge modules.
>
> I have filed a bug on all of these merge modules, and we should
> hopefully
> have some new ones out soon.
>
>
> Adam Semel
> Windows Installer Team
> Microsoft Developer Support
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
So this is indeed a BUG, I hope it will be fixed soon.
"Adam Semel" <asemel@online.microsoft.com> wrote in message news:<E0XCmi5HDHA.1636@cpmsftngxa06.phx.gbl>...
> Ok guys.. just went through the merge module again. There are two
> things
> wrong with them. The first is that you can't retarget the merge module like
> you could with the 2002 merge modules. The second (which is also the cause
> of the first) is that the merge modules have the wrong schema. We are using
> a 100 schema, which means we can't even manually fix the merge modules.
>
> I have filed a bug on all of these merge modules, and we should
> hopefully
> have some new ones out soon.
>
>
> Adam Semel
> Windows Installer Team
> Microsoft Developer Support
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
So this is indeed a BUG, I hope it will be fixed soon.
Asaf Vishna[br]SmarTeam Corporation Ltd.[br]Email: AsafV@SmarTeam.com
Posted 28 October 2003 - 08:45
Hi!
I fixed this problem by modifying merge modules.
If you wish, you may download them from
http://www.rsdn.ru/F...rge Modules.zip
Best regards!
I fixed this problem by modifying merge modules.
If you wish, you may download them from
http://www.rsdn.ru/F...rge Modules.zip
Best regards!