Visual C++ Runtime installer doesn't clean up after itself | The Coffeehouse

daytrip00

EDIT: This refers to the visual c++ redist.

Here's a screenshot of my C drive:

Pretty obnoxious... Here's a link to the connect topic on the issue:
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=316557

No action on the issue since 12/10...

Anybody got any suggestions?

evildictaitor
if( !succeed( try() ) ) { while(true) try(); }

Is this the VC++ compiler that comes with Visual Studio, and if so which version? If not, which version?

Edit: Ok. You mention it's VS2008 RTM in your feedback.

I don't have this problem Perplexed

- is your temporary files folder got mixed up?

daytrip00

evildictaitor wrote:
Is this the VC++ compiler that comes with Visual Studio, and if so which version? If not, which version?

Edit: Ok. You mention it's VS2008 RTM in your feedback.

I don't have this problem - is your temporary files folder got mixed up?

This is what the visual c++ 2008 REDISTRIBUTABLE does when installing, not visual studio itself. Again, it's not the compiler, it's the redist. It's been reported on connect but received no response.

evildictaitor
if( !succeed( try() ) ) { while(true) try(); }

Is the Visual Studio team responsible for it? (Presumably, since it's the compiler, and they are the superset of the compilers team). If so try using the contact link on the Visual Studio blog.

daytrip00

evildictaitor wrote:
Is the Visual Studio team responsible for it? (Presumably, since it's the compiler, and they are the superset of the compilers team). If so try using the contact link on the Visual Studio blog.

I've been getting the impression that the developers @ microsoft dont actually care what us developers think.

I'm so unbeliveably frustrated with Microsoft right now. It seems like they just can't do anything right these days. Not dumping the installer's intermediate files into the root path seems to be a pretty obvious thing that you SHOULDN'T DO.

YearOfTheLinuxDesktop
Seven of Niner! Resistance is Futile!

a MFC upgrade is planned for march/april so don't expect any bugfixed release for now, they're most likely going to wait to release the newer version

unfortunately I stopped using MFC a while ago just because I hated the redist, maybe now with all the new cool UI office-like controls I'll start using MFC again, it's hard to resist the beautiful gradients Sad

daytrip00

evildictaitor wrote:
Is the Visual Studio team responsible for it? (Presumably, since it's the compiler, and they are the superset of the compilers team). If so try using the contact link on the Visual Studio blog.

Ok... I emailed the VC++ team and posted on their forum... Naturally, no response...

I'm getting very close to banning any new microsoft technology at our company.

evildictaitor
if( !succeed( try() ) ) { while(true) try(); }

daytrip00 wrote:
Ok... I emailed the VC++ team and posted on their forum... Naturally, no response...

Patience is a virtue, as they say.

YearOfTheLinuxDesktop
Seven of Niner! Resistance is Futile!

daytrip00 wrote:

Ok... I emailed the VC++ team and posted on their forum... Naturally, no response...

I'm getting very close to banning any new microsoft technology at our company.

I don't understand. if the problem is the SFX why don't you just extract it and create a working SFX with 7-zip or winrar? both can extract in temp folders/run applications/delete extracted files

Damien Watkins

Hello

This erroneous behaviour will be corrected for SP1, apologies for the inconvenience. George and Ben recently did a Channel 9 video on deployment – I believe that George would normally suggest the way to deploy these files would be via MSMs. See also Ben’s blog entry on how to build a MSI using the MSMs.

Does this address your situation?

Thanks
Damien
--
Channel 9 video: http://channel9.msdn.com/Showpost.aspx?postid=369473
VC Blog by Ben: http://blogs.msdn.com/vcblog/archive/2007/10/12/how-to-redistribute-the-visual-c-libraries-with-your-application.aspx

daytrip00

Damien Watkins wrote:
Hello

This erroneous behaviour will be corrected for SP1, apologies for the inconvenience. George and Ben recently did a Channel 9 video on deployment – I believe that George would normally suggest the way to deploy these files would be via MSMs. See also Ben’s blog entry on how to build a MSI using the MSMs.

Ok... now I feel bad for my flaming above. It's been a frustrating couple months for me with Microsoft technology and i ended up taking it out on the VC++ team. Thanks for your help, Damien!

YearOfTheLinuxDesktop
Seven of Niner! Resistance is Futile!

Damien Watkins wrote:
Hello

This erroneous behaviour will be corrected for SP1, apologies for the inconvenience. George and Ben recently did a Channel 9 video on deployment – I believe that George would normally suggest the way to deploy these files would be via MSMs. See also Ben’s blog entry on how to build a MSI using the MSMs.

Does this address your situation?

Thanks
Damien
--
Channel 9 video: http://channel9.msdn.com/Showpost.aspx?postid=369473
VC Blog by Ben: http://blogs.msdn.com/vcblog/archive/2007/10/12/how-to-redistribute-the-visual-c-libraries-with-your-application.aspx

could you please also get rid of the .CAB file and the other unpacked files in the x64 build and also make sure admin install point works? it would be nice having only a single MSI file for deployment or being able to unpack it (admin install point) and recompress in a better format than CAB