Software Deployment

Hi Eric,
you could use the VC 2k5 RT MSM's and include them in the package.
Extract them from the VC 2k5 SP1 download.
Regards, Nick

VC 2k5 RT MSM's ?

You can't work it out?!?!? Nick is referring to the Visual C 2005 runtime merge modules.

VBScab: Why cant you stop being such an ass so to speak!?!?!?
Did you had a bad childhood ore something??? And has to take it out on people now?
Then I cant do more than feel sorry for you....

I know that I dont have much experians of MSI packaging. But please if you just want to pick on someone please do it like a man and front them IRL. Dont be like a dam kid and do it on a forum!!

Hi Eric,
don't like to see such language here at all !!!
Ian is maybe kind of direct sometimes, but he has helped a lot of people with their problems (and given you the right answer too, BTW).

A minute of googling would probably have given you the answer also.

And hey: Your initial question with the reference to a self built CA didn't tell me that you don't have that much "MSI experience".

But without in deep knowledge of MSI, you won't be able to integrate the VC redistributes into the MSI.

However, the newest VC8 MSM's are in the SP1 download, which is big enough (430MB).
It contains a patchfile (MSP). One can use the msix utility to extract the files. One of them is the CAB file which has all the MSM's inside.

Regards, Nick

Hi nheim,

Yes I know that he is really good and that he has helpt out many people here. But that dont make it right of him to continue with this style against me............................OR?
It seems that he has something against me and I will NOT take it! I think it is really childish of him.

Anyway lets leav that. Thanks for your help.

Please keep the response in a friendly manner, both of you!

ORIGINAL: aXz
I think it is really childish of him. My friend, what's childish is that you want others to do your work for you. To know that you do not even attempt to find answers to your question by conducting even the most basic research is what irritates. If you knew anything about the Windows OS, you'd know that the MS VC runtimes are contained within files called something like 'MSVCRT[number].DLL'. It's then a no-brainer to work out that 'VC' would be shorthand for 'Visual C' and 'RT' short for 'RunTime'. If you had learned anything about packaging, you'd know that merge modules are saved with the extension 'MSM'. See? Easy. Even a child could do it.

ORIGINAL: aXz
please do it like a man and front them IRL. Are you threatening me? In public? Great move.

For our DWG 2k9 deployment using Altiris we run through the component installs, DX9, VCRT, .NET, MSXML, then DWG. Each install task does a quick check to see if the component is already present and skips out if it's found. works great, no fuss. That meathod may be easier if you're not familiar with the other methods described here.

ORIGINAL: klug

For our DWG 2k9 deployment using Altiris we run through the component installs, DX9, VCRT, .NET, MSXML, then DWG. Each install task does a quick check to see if the component is already present and skips out if it's found. works great, no fuss. That meathod may be easier if you're not familiar with the other methods described here.


Was just going to leave a similar comment as well. I downloaded the updated DirectX, MSXML and VC++ redist and installed them seperately then at the end DWG. This all done through Altiris as well.