Now that Visual Studio 2005 Service Pack 1 is released, some are wondering how to slipstream the patch so they can install Visual Studio 2005 with SP1 already applied. Much of this process is standard practice for Windows Installer packages.
Please note this will require a lot of disk space, as you’re unpacking around 3 GB – and more, if you add the MSDN installation, though that is not patched in this service pack – just for the product installation.
1. Install the Product
You must create an administrative image of Visual Studio 2005 in order to slipstream the service pack in that way. Installing the patch while installing the product – though a supported scenario with Windows Installer – is not supported in our patches currently because of how actions are conditioned, a more general problem I’ll discuss in a future post.
Assume D: is your CD or DVD drive letter, and \servershare is a path with space available all licensed users can access.
msiexec.exe /a D:vs_setup.msi TARGETDIR=\servershare /L*vx install.log
2. Unpack the Patch
The patch you download for service pack 1 is a wrapper around the .msp file, so you must unpack the .msp file using the patch-standard /extract switch. Assuming you made an administrative installation of Team Suite, the main Visual Studio 2005 SP1 is used below:
VS80sp1-KB926601-X86-ENU.exe /extract “%TMP%”
3. Apply the Patch
Now that you have the .msp file extracted, you must apply it to the administrative installation from step 1.
msiexec.exe /a \serversharevs_setup.msi /p “%TMP%VS80sp1-KB926601-X86-ENU.msp” /L*vx patch.log
4. Installing the Patched Product
The official deployment strategy for Visual Studio 2005 network installations can be found in KB907759. Copy the contents of the CD or DVD to the same directory – like \servershare in the example above – but do not replace any files. You really don’t need to copy the CAB files in the root directory, either. All those files have been expanded into source directories. This step is to copy the bootstrap files and other required components to the installation directory. After copying is complete, run setup.exe as normal.
Notes
Because when Windows Installer installs a patch to an administrative image, the identity of the patch is essentially lost (the #transform is not persisted, which contains information about how to apply the patch) the service pack is not uninstallable when you install the slipstreamed installation you just created. The entry in Add/Remove Programs (ARP) was written in lieu of having ARP discover the patch, but without an UninstallString registry value for the patch because the patch doesn’t actually exist and can’t be uninstalled.
This is also an expanded form of the installation, with all files loose in their source directory structure. If someone were to write a tool to repackage this, such a tool would have to – based on the Media table, attributes in the File table, and Word Count summary property as described in File Sequencing and How Files are Located – re-CAB some files and embed some of those CAB files back into the .msi file, then reset the administrative image bit (bit 2) in the Word Count summary property.
Heath Stewart has made a nice how to on his MSDN blog on how to slipstream visual studio 2005 SP1. Its
Că tot a apărut VS 2005 SP1 uitaţi un mini How to .. despre cum să faceţi slipstream la SP1. V.Nice.
After installing SP1, Properties window stopped working in Source view of an ASP.NET page. It used to display properties of a selected item (though slow), now it is just blank window with empty list of elements.
Can I uninstall the Service Pack?
The logs created in these steps are very large (60+ MBs), having not path given to the logs puts them wherever the current directory is. They should, at the least, be sent to the %TMP% folder.
Ex: msiexec.exe /a D:vs_setup.msi TARGETDIR=\servershare /L*vx "%TMP%install.log"
Also there is a mistake in the 3rd step since there is no reference to a target directory, it will attempt to patch the source directory.
Simply changing the installer’s path to the newly created administrative share is sufficient to properly patch the right source.
Ex: msiexec.exe /a \serversharevs_setup.msi /p "%TMP%VS80sp1-KB926601-X86-ENU.msp" /L*vx "%TMP%patch.log"
Visual Studio 2005 Service Pack 1 was released yesterday. Here are the direct download links. · VSTS
Aleksey, I recommend you report the problem using Microsoft Connect, which you can access though http://connect.microsoft.com. If you want to uninstall the service pack, you can do so in Add/Remove Programs from the Control Panel, but please take note your original Visual Studio 2005 installation media may be required, as reported in the "Instruction" sections of the download page at http://www.microsoft.com/downloads/details.aspx?familyid=BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC&displaylang=en#Instructions.
jcarle, thanks for pointing out the mistake. I’ll correct that. As for the log path, it’s certainly up to the user to put the log wherever. I usually just use the current working directory because I can simply type "gvim patch.log". You can also decrease log size by getting rid of "x", but it is highly recommended that you pass "*v" to generate verbose logs, which is about the only way to diagnose problems given the transactional nature of Windows Installer.
Die Installation des Service Packs für Visual Studio 2005 dauert lange, sehr lange, desweiteren wird viel freier Speicher auf der Festplatte gebraucht und zwar schlappe 6,2 GB. Sollte man das Visual Studio mehrmals auf der Platte haben so erhöhrt sich
Finally the long awaited TFS service pack 1 has shipped … see http://www.microsoft.com/downloads/details.aspx?FamilyID=A9AB638C-04D2-4AEE-8AE8-9F00DD454AB8&displaylang=en
Slipstream VS2005 SP1
Oh god, the output of this is big. I’m trying to build a DVD with updated Visual Studio components on it (VS2005 with SP1 slipstreamed, the latest MSDN Library, etc.), but the un-cabbed files take up 3.22GB on their own, which doesn’t leave enough room on a DVD for even the older MSDN Library that was on the RTM DVDs. Is there going to be a way of getting around this or will I just have to go without a convenient up-to-date install DVD?
Answers to my prayers – kind of. Good post on slipstreaming the SP1 patch into a Visual Studio 2005 Fresh…
Answers to my prayers – kind of. Good post on slipstreaming the SP1 patch into a Visual Studio 2005 Fresh…
Joe, you could always keep MSDN on a separate disk. http://support.microsoft.com/kb/907759 documents putting both VS and MSDN in the same location, but you could simply put MSDN on a separate disk or just pop in your original when you need to. Personally, I don’t install this in lieu of the current Platform SDK (now "Windows SDK") since that can integrate into the combined collection, or you can even just select it for use from VS’s options dialog instead of the combined collection. That way it’s up-to-date, along with headers, libs, etc.
Visual Studio 2005 Service Pack 1 available now
To be short.
Service Pack 1 is broken. It’s not possible to install it on a 2003 Server.
The digital signature is not acceptet even if I do an administrative installation of VS2005 and then tries to apply SP1 to the adm installation.
And the same error ("Digital signature incorrect") appears if I try do do a local installation.
Exactly the same setup works on XP SP2.
lmfs, this is a known issue, documented in the SP1 README file along with a pointer to KB925336 at http://support.microsoft.com/kb/925336, which was derived from a couple of my blog posts on the same problem before SP1 beta shipped. Please follow the instructions in the KB article or from this blog (they are the same).
I seem to recall reading somewhere that if yo slipstream Office service packs it becomes impossible to install any future updates (instead, you have to update the administrative image and then repair from that to get the updates). Is this the case if I slipstream VS2005 as well? Or am I just making stuff up?
KB925336 does NOT work for me as I continue to be plagued by the "digital sig" problem while attempting the install on win2k3. i concur w/lmfs , this SP IS broken…
lmfs and cj, this is actually a problem in Windows XP and Server 2003 that manifests as a result of all the files fixed in the service pack. Be sure that you stop the msiserver service or reboot your machine after making the change so that it takes effect. If that continues to be a problem, please also remove the MSP file type from the Designated File Types in the same location where you disabled the SAFER check for local administrators. For this change, reboot the machine.
I’ve just finished my guide about upgrading TFS V1 to WSS 3.0 and Microsoft immediately releases Service
Even if I follow KB925336 I can’t install SP1 on Windows 2003 (domain member). I have also disabled check for msp files.
Error 1718: File C:Windowsinstallerbbae82.msp did not pass the digital signature check.
Installer folder does not exist in c:windows.
Matej, we are investigating why the workarounds don’t work in some cases. As for the %WINDIR%Installer directory, it is a hidden, system folder. In order to see it in Windows Explorer you must have both hidden and system files visible. You can ‘cd’ to it, however, but do not attempt to alter files or permissions because this could corrupt the installer cache which would remove all cached files and cause a lot of problems.
The release of Visual Studio Service Pack 1, seems to have created a lot of interest – rightfully so
Sven, patches can be applied to patched admin installations, at least in DevDiv. I remember talking about Office’s limitations with them quite sometime back but don’t remember all the details. Suffice to say, Windows Installer supports this but one problem is that when admins on your network update the admin image with another patch, that can cause problems (such as "removing" the client-installed patch) when the new patched admin image is reinstalled and cached on your client machine.
Link to Heath Stewart’s Blog : Slipstreaming Visual Studio 2005 Service Pack 1 If you would like to integrate
If you would like to integrate the Visual Studio 2005 Service pack 1 into the standard installation of the Visual Studio Heart explained that on his blog. Great!
Yes, I too have followed KB925336 and confirm that the VS2005sp1 still does not install and appears to be broken for Windows2003sp1.
We are trying to repro this internally where the workaround doesn’t work, but have not been able to. We could repr the original problem even before the beta shipped but the workaround always worked. We’re fairly certain that on such machines memory fragmentation is very high. Be sure to follow the previous instructions then reboot the machine as opposed to just restarting the service. If that doesn’t work (and please let me know if it did), shutdown non-essential (to SP1 installation) services like the various SQL services. Shutdown as many apps as you can and log out all inactive sessions. Try installing SP1 again.
Please keep me informed if any of these solutions work.
Same here, can’t install SP1 on Windows Server 2003. I had Windows Server 2003 SP2 RC installed, even reverted to SP1 (uninstalled SP2 RC) which did not help. This is a domain member fairly recently upgraded from Server 2000. The policies are changed in Local Security Policy, removed MSP from Designated File Types etc. Tried for about a day including numerous restarts, log-on as domain admin and local admin, it still throws "SaferIdentifyLevel reported failure. Assuming untrusted." Maybe the registry is not updated correctly? What is the relevant registry key?
dirk, see http://blogs.msdn.com/heaths/archive/2006/09/22/Enabling-Large-Patches-to-Install.aspx for the registry key.
We are continuing to investigate why the workaround isn’t working on Windows Server 2003. Try shutting down as much as you can before installing the patch. You might also use ‘msconfig.exe’ to disable functionality at system boot.
Slipstreaming? I don’t need mean to vent, but aren’t there more important issues to worry about, such as actually getting the service pack to install on machines that already have VS2005 installed?
Based on what I’ve seen in various forums, I am not the only one who can’t get the darn thing to install. I keep getting that original source media required error.
After all the pain that the Office 2007 install gave me… and the fact that IE 7 still doesn’t appear to work 100% yet (the 32-bit version refuses to view any RSS feed and the 64-bit version won’t subscribe to them) I am beginning to wonder if Microsoft’s installation packages are getting too complicated to be trusted.
Ron, there are many issues regarding SP1 and Windows Installer patches in general described in my blog. For SP1, click on the "VS 2005 SP1" tag at the top of every page.
Prompts for source during installation mean that some file not being patched is missing. If you provide the original source be inserting your media or specifying a network location you can get past this error and continue with installation.
This might be just the worst way for upgrading your Programming IDE.
Even with slipstreaming it takes 100% cpu, but no disk activity. So I wonder, what’s happening?
This workaround does not work on Windows 2003 for me either.
Have you found the right solution?
For additional feedback: The quoted registry key HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsSaferCodeIdentifiers was empty in my case (even though the settings in Local Security Policy were persisted and correct). This was probably because of some "Group Policy processing aborted. " errors (Event ID 1053) I had since the upgrade from Win 2k. I since rejoined the domain and the keys now exist. I haven’t tested intalling the SP because I had already used your slipstreaming technique which worked fine. Thanks.
Sander, slipstreaming is not generally recommended. In most cases, just download the patch executable and double-click it. If you want to know what’s going on behind the scenes, look in the "VS 2005 SP1" tag (near the top of every page) and I have several posts about that very subject.
Serhiy, we are still working on solving the problem, but you should be able to reduce the physical memory fragmentation by disabling as many services as possible and shutting down all apps that are not necessary.
The DVD from MSDN has Visual Studio 2005 in a vs sub-folder. For these instructions to work, you will need to modify the first command to be:
msiexec.exe /a D:vsvs_setup.msi TARGETDIR=\servershare /L*vx install.log
More importantly, when you burn the patched files back to DVD, you must put them BACK into a vs sub-folder or the install will fail because it cannot find files and starts prompting for the DVD (which is already in the drive).
In you were out the second half of December, you might have missed some of the VS 2005 Service Pack 1
In you were out the second half of December, you might have missed some of the VS 2005 Service Pack 1
I also got the "Digital signature incorrect" error on multiple Windows 2003 Server installations.
The only way I got this SP to install on a Windows 2003 Server (domain member), was to take the machine out of the domain while applying the SP and then adding it back to the domain afterwards.
So somehow the digital signature "bug", at least in my case, was related to being a domain member. I doubt it has anything to do with memory fragmentation since I on one machine tried stopping all apps and services not necessary thereby having almost 3GB RAM free. These could of course still be too fragmented, but not likely.
Heath Stewart has written several very useful blog posts about Visual Studio 2005 SP1 that I wanted to
【原文地址】 A few VS 2005 SP1 Links and Information Nuggets 【原文发表日期】 Monday, January 01, 2007 8:24 PM 如果你在12月份的下半个月出去了，你也许错过了我早先写的几篇关于VS
VisualStudio2005的SP1补丁已经发行一阵子了,大家应该都已经打上这个补丁了吧.但是每次在安装visualstudio2005就已经需要很长的时间了,再一打补丁,好家伙,需要的时…
I receive this error when attempting to Slipstream my DVD:
Product: Microsoft Visual Studio 2005 Team Suite – ENU — Error 1335.The cabinet file ‘_15370_RTL_x86_enu_dNS_SDK_Samples.cab’ required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
Any thoughts on this?
Hi,
I trying to slipstrem the vosial studio sp1 and when I get to step 3:
D:>msiexec.exe /a vsvs_setup.msi /p vsVS80sp1-KB926601-X86-ENU.msp /L*vx pa
tch.log
I get an error pop up that says:
This patch package could not be opened Verify that the patch package exists and that you can access it, or contact the application vendor verify that this is a valid windows installer package"
This is on a windows xp sp2 and vs2005 and tha pactch have bee installed without errors.
I’ve verified the paths and they are the right ones
In my consulting roll with VSTS/TFS, one of the things I often work with clients on is how to setup and
Samir, we have seen a few reports during patch installation like this. At this time all I can recommend is trying to re-apply the patch, and possible disable SAFER as directed at http://blogs.msdn.com/heaths/archive/2006/09/22/Enabling-Large-Patches-to-Install.aspx. I will update my blog with more information when available.
PerseP, use fully-qualified paths. This is especially important when specifying the path to the patch.
Hi,
I finally solved my problem. A file the service pack was looking for in c:windowsinstaller wasn’t there.So I had to uninstall Visual Studio manually, following Microsoft’s Support page instructions and then I could slipstream the service pack without problems
Any advices on integrating the SP1 into Visual Studio 2003? Please?
Serge, administrative installations are a feature of Windows Installer. Following the instructions about is a procedure for Winodws Installer, not specifically our patches. That said, you should be able to follow the same basic instructions for VS 2003 SP1.
Ive found a bug in VS2005 rtm so i had to install SP1.
I’m devloping on Win2003sp1 member of AD.
this the sequences of the events till I made it:
1. Try to install the sp1 – gets "Digital signature incorrect" error
2. Try to install the sp1 using the workaround – gets msp missing from instller directory.
3. try to use the rtm – cannot find C# complier
4. Try to repiar rtm install – didn’t workout
5. uninstall vs2005
6. try to install vs2005 rtm – failed
7. try to repair .NET 2.0 – failed
8. clean-up ,NET 2.0 – worked
9. Install .NET 2.0 – worked
10. made slipsteam installation on XP WS.
11. Install VS2005 sp1 slipstream – Finally worked!!!!
It took me 2 working days!!!!!!!!!!!!!
10x microsoft for good QA for SP 🙂
Esto es muy util, ya que por lo lenta que es la instalación del Service Pack 1 de Visual Studio 2005,
Microsoft 给了我们糟糕的用户体验
How to re-CAB the VS2005 installer after slipstreaming? It’s so big 🙁
Replika, as I mentioned in the post you’ll need to create CABs, optionally embed CABs, and keep some files loose all based on the Media table so be sure to understand the media table. Search my blog for "Media table" for more information and links to MSDN.
将visual studio 2005 SP1补丁整合到安装文件
Esto es muy util, ya que por lo lenta que es la instalación del Service Pack 1 de Visual Studio 2005,
Hi,
I tried installed sp1 two times, they all failed. First time was because there was no enough disk space; then I deleted a lot file and made 2G available. I started second time, it failed saying that the install package has problem. So I redownload the package and am about to try another time. Then I found my disk only has less than 200 Megabyte left.
I seems to me that each time the installer runs, it adds a lot of files to your hard drive, and those files from different runs are kept at diffent laction. Is this true? If so,
can you tell me where those files to located. I want to clean up those files from my previous failed installtions to make more space, so I can try third time.
thank you
Hua, you can remove anything in your %TEMP% directory. Other than that, see http://blogs.msdn.com/heaths/archive/2007/01/17/the-patch-cache-and-freeing-space.aspx. NEVER remove anything directly in %WINDIR%Installer.
Hi,
I finally managed to get more disk space. I tried another time of the installation. this time I got another error, error is "the installer has encountered an unexpected error installing this package. This may indicate a problem with this package. the error code is 2908". Any idea?
Thanks
Hua
Hua Yang, Error 2908 is typically caused by lack of disk space. Please note that the SP1 README recommends you have 6.2 GB of space available for a typical SP1 installation. Most of this will be freed upon completion of the SP1 installation.
Please note that if you have lots of products to which SP1 applies or the same product in different languages (which, with Windows Installer, is a different product) that the amount of space required multiplies for each language you have installed. You can use my Patch Applicability Browser at http://blogs.msdn.com/heaths/articles/pab.aspx to see to how many products a particular patch applies. You must extract the MSP from the EXE you downloaded by passing /extract to the EXE.
Hi,
I have 12GB disk space. I do not think the error 1908 was caused by lack of disk space.
Thanks
Hua, that sort of information would’ve been helpful before. In order to further diagnose the problem, I will need to see a verbose log. I recommend you open a bug on the Connect web site for Visual Studio 2005 at http://connect.microsoft.com/feedback/default.aspx?SiteID=210 and post the URL here so I can more easily find the bug. You should also ZIP and attach a verbose log of the patch install. Pass "/L*vx+ patch.log" (without quotes) to the EXE you downloaded to generate a combined, verbose debug log. ZIP’ing it will greatly reduce the size making it easier to upload.
I’ve notice several comments indicating errors in the initial steps to slipstream SP1 into a VS2005 distribution.
I’d rather see the EXACT steps reproduced ACCURATELY in one place than having to read all the comments and attempt to figure out what’s really the exact procedure. (Mainly because someone’s correction may also be in error.)
Also, in step 4, it says, "Copy the contents of the CD or DVD to the same directory – like \servershare in the example above – but do not replace any files". So this means that I copy all the files from the DVD to the place I ran the slipstream on, but I don’t want to replace any files? Does this mean the same thing as simply "adding" files from the DVD to the output image that are missing?
Once step 4 is complete, can the resulting output image be re-burned to DVD and used as an install disc?
I agree with Bit – more detailed info on step 4 would have helped. I managed to sucessfully slipstream SP1 and install vs 2005 after some trial and error. The first time around I got stuck during Setup when it wanted to install windows installer 3.1 and couldnt find the file. I tried to point it in the right direction and even though the file was in the folder I pointed it to it still said "The path is invalid".
Here is what worked for me: From the original source, select everything except the .cab files and copy that to \servershare. When asked to replace any files or folders say no. The only 2 folders it wants to replace are "program files" and "wcu". Program files is fine like it is, but you need to go into wcu (on original disk) select everything in there, then go to wcu in \server\share, copy it there and say no to any files or folders it wants to replace.
The final size of the install folder (without msdn) was 2.87 GB
After that I installed straight from my hdd and
even though it was a bit of a nervous process just waiting for the setup to ask me for a missing file again it went fine and was nice and quick.
vs2005sp1集成安装
Specifically, what more needs to be documented beyond what KB907759 that I linked in step 4 details?
The part about copying the contents of the fwcuu folder as well – I missed that step with my first try.
Well, the first set of instructions (according to many subsequent posts) contain errors. Therefore, the slipstreaming instuctions are not 100% correct, then followed by a loose set of errata.
In one post, an error was indicated followed by a comment that it would be fixed. Was it fixed? It doesn’t appear to be.
Since the command lines are complex and contain very specifc filenames and switches, a full update of the EXACT instructions with EXACT pathnames and all errata included would be helpful for everyone.
Right now, everyone who tries to do this must read ALL the posts to figure out how to make it work (because the initial steps still appear to be in error and/or contain omissions).
Bit, not everyone is having problems. And I do have several posts to address several issues, but do in fact have one that I will update regarding frequent issues. Read http://blogs.msdn.com/heaths/archive/2007/01/11/known-issues-with-visual-studio-2005-service-pack-1.aspx. We also have regular refreshes with the README content for each service pack, which you can find links to on the download pages. That information is intended to be read before installing the package, as with many installs even on different platforms.
Hi, (scratching my head).. why are we not running step 4 before step 3.. would that not save the additional burden of bothering about overwriting files ?
You wouldn’t believe what I went through the last 2 work days trying to fix/install/reinstall VS2005/.NET2/SqlServer.
Whatever I do, I get the same 1335 error. I can’t slipstream, neither from the CD directly nor from the HDD, nor can I install the SP1 cleanly, with or without the "/quiet" switch.
Why do I get this error?
NY, step 3 is actually applying the patch to the administrative installation, which is basically the product unzipped – not installed. Step 4 installs the patched product. Slipstreaming is the act of installing both the product and patches in the same transaction, so step 3 must come before step 4.
John, which service pack are you trying to slipstream? Please provide the complete file name and to which product you’re trying to apply it. Preferably I would like the ProductCode to uniquely identify it, so pass "/L*vx patch.log" (without quotes) when performing step 3.
What I meant is if steps 3 and 4 were re-written as follows. Maybe I am still not understanding this so kindly excuse since I am new to VS. :
3. Copy support files
The official deployment strategy for Visual Studio 2005 network installations can be found in KB907759. Copy the contents of the CD or DVD to the same directory – like \servershare in the example above – but do not replace any files. You really don’t need to copy the CAB files in the root directory, either. All those files have been expanded into source directories. This step is to copy the bootstrap files and other required components to the installation directory.
4. Apply the Patch
Now that you have the .msp file extracted for step 2, you must apply it to the administrative installation from step 1.
msiexec.exe /a \serversharevs_setup.msi /p “%TMP%VS80sp1-KB926601-X86-ENU.msp” /L*vx patch.log
5. Installing the Patched Product
Run setup.exe as normal. And choose to reinstall if you have the the base version installed.
Also on my xp sp2 Windows ® Installer. V 3.01.4000.1823 the patch update command had no /p option had to use /update also the %TMP% variable was not taken for some odd reason.. had to use the absolute path.
Well, the work around worked for me. I have a freshly installed W2k3 SP1 Domain Member and the SP didn’t install (digital signature error). I followed the work around at http://support.microsoft.com/kb/925336 and it installed fine.
Heath, thanks for the link to the work around.
Tried doing a administrative image of Visual Studio 2005 in vista but was unable to execute msiexec.exe /a D:vs_setup.msi TARGETDIR=\servershare /L*vx install.log in vista as the windows installation just pops up showing all the option & cmdline.
"vista", what you have posted is correct but I’m guessing you’re not really targeting "\servershare". Make sure that path is enclosed in quotes, as are any other paths with spaces in them.
Thks u Heath Stewart for the guide & advice. Slipstream SP1 together with VS80sp1-KB932232-X86 strange how they include a x86 naming to the KB when it support both 32bit & 64bit. Anyway cheers! Installation complete without error after adding all the files needed. Once again thks everyone for your valuable advice & input.
"Vista", actually the patch doesn’t update any 64-bit SKUs. Visual Studio 2005 is still 32-bit, which runs in WOW64 on 64-bit platforms. There are only a few actual 64-bit products, like the debugger extensions which were not patched.
将visual studio 2005 SP1补丁整合到安装文件
看过了HeathStewart’sslipstreaming的朋友们,认为此人大有强人风范啊!原因有二:1.人强,看他的weblog就知道了,非等闲之辈2.机器强,看他的weblog里全是…
VisualStudio2005的SP1补丁已经发行一阵子了,大家应该都已经打上这个补丁了吧.但是每次在安装visualstudio2005就已经需要很长的时间了,再一打补丁,好家伙,需要的时…
Yes, in terms of manhour, computer time, plus hard drive space. Standard installation of VS2005SP1 is
Esto es muy util, ya que por lo lenta que es la instalación del Service Pack 1 de Visual Studio 2005
Visual Studio 2005的SP1补丁已经发行一阵子了,大家应该都已经打上这个补丁了吧.但是每次在安装visual studio 2005就已经需要很长的时间了,再一打补丁,好家伙,需要的时间更长,有没有好方法让我们象当年整合window2000的SP补丁一样把VS2005 SP1补丁也整合到安装文件里呢?这样在以后安装就能节省很多的时间了.有的!
Link to Heath Stewart's Blog : Slipstreaming Visual Studio 2005 Service Pack 1 If you would like
On the recommendation of a trusted co-worker who shall remain unnamed, I had installed the March CTP
手头上有个项目要用到VS2005，无奈之下拿起那庞大的VS。想想升级sp1那漫长的过程，决定想想别的办法。心想既然windows、office之类的都可以集成补丁，vs2005应该也是可以的吧。Goo…
As most of you know Service Pack 1 for Visual Studio 2005 is a bit of a beast. I personally think…
将visual studio 2005 SP1补丁整合到安装文件中的方法
VisualStudio2005的SP1补丁已经发行一阵子了,大家应该都已经打上这个补丁了吧.但是每次在安装visualstudio2005就已经需要很长的时间了,再一打补丁,好家伙,需要的时…
将visual studio 2005 SP1补丁整合到安装文件
今更ですが、Visual Studio 2005 SP1 適用済みイメージの作成
Para desenvolvedores que trabalham com esta ferramenta, esse procedimento é bem interessante e poupará
Heath Stewart has made anice how to on his MADN biog.