This site uses cookies for analytics, personalized content. By continuing to browse this site, you agree to this use. Learn More
Installation and containerization of the Visual Studio family of products
August 29, 2006Aug 29, 200608/29/06In response to a previous post about how large patches can cause problems, reader Zodman asks,
“Would it be fair to say that SP1 is actually ready, and that the only hold up is problems with the install?”
While I can’t comment on any dates or availability,
August 23, 2006Aug 23, 200608/23/06In response to a previous post where I mentioned that work was being done on Visual Studio 2005 SP1, reader ringi commented,
“I would match rather has SP1 as a complete 4GB install, including having to uninstall Visual Studio 2005 then have it delayed just to save a little bit of bandwidth.”
August 18, 2006Aug 18, 200608/18/06Digitally signing files helps protect against changes to a file (or any data, really) by validating that a hash of the current file matches the hash stored in the digital signature. Digital signatures also help verify that a package came from a particular publisher by encrypting the hash with the publisher’s private key.
August 14, 2006Aug 14, 200608/14/06Another reason a custom action may not run is because the custom action function isn’t exported. This may not be common in most patch build systems, but could arise during authoring or if a binary wasn’t updated in the Binary table.
August 14, 2006Aug 14, 200608/14/06I’ve been away for a while, though I’ve barely left the Microsoft campus. As we prepare for Visual Studio 2005 Service Pack 1, I’ve been very busy with issues: especially an issue with the size of the patch.
Visual Studio is probably the biggest product (in terms of the number of files at least;
