Web Platform Installer
Version 4 and still useless with many corporate proxies
Last post Sep 24, 2012 10:31 PM by ChrisSfanos
Sep 11, 2012 06:43 PM|myscreennamewastaken|LINK
Sep 12, 2012 12:14 PM|myscreennamewastaken|LINK
Sep 12, 2012 11:55 PM|ChrisSfanos|LINK
Thanks for the post - this is an area we do need to continue to address. In the meantime, we have a workaround using WebPICMD.exe and the /offline cache feature. If the list of products you want to install with WebPI is pretty static/known, creating a
local cache of these products and using the offline feed to offer these in the Enterprise is a potential solution
Is that interesting?
Sep 15, 2012 11:39 AM|myscreennamewastaken|LINK
Sep 18, 2012 09:44 PM|ChrisSfanos|LINK
Thanks for the additional feedback - I'll file that away for future work we do with proxy handling
In the meantime, as a last-ditch workaround, you could create the offline cache outside of your corporate office and bring the resulting cache set in via USB/etc - I know it's not optimal :-)
Sep 18, 2012 10:13 PM|Colin Skopinski|LINK
Here's what we had to do to workaround:
1.) Download WebPICMD.exe (http://www.iis.net/learn/install/web-platform-installer/web-platform-installer-v4-command-line-webpicmdexe-preview-release_1072)
2.) Use it with the Offline flag to download the items you need (this step has to be done outside of the network, i.e. on a home PC)
- The list is available at http://www.microsoft.com/web/webpi/4.0/WebProductList.xml (Use the productId)
- Example of a batch file to download the Web Farm Framework 2.2 (Product ID = WebFarmFrameworkv2) and SQL Server Data Tools for VS2010 (Product Id = SSDTVS2010) to the C-drive.
WebPICMD.exe /Offline /Products:SSDTVS2010,WebFarmFrameworkv2 /Path:C:\
3.) Copy contents onto developer machine. Note the directory.
4.) Create a batch file in the <ProductId>\feeds directory called "Install.bat"
5.) Paste the following:
WebPICMD.exe /Install /Products:<ProductId> /XML:"<Copy Location>\<ProductId>\feeds\shadow-webproductlist.xml" /Log:Install.log
6,) Run the batch file
7.) Review log file for errors
1.) Some extensions are dependent on certain versions of the Web Platform Installer (believe it or not). For example, the Web Farm Framework v2.2 is dependent on WPI v3
2.) Sometimes the installation file needs to be run directly (for example, SSDT). You should be able to determine the location of the file from the log file.
Links to WPI versions
Sep 20, 2012 09:40 PM|myscreennamewastaken|LINK
Sep 24, 2012 10:31 PM|ChrisSfanos|LINK
I thought I posted this already, but as a note for everyone, please do NOT use the WebPICMDLine preview any more - please only use the version that ships in the main WebPI v4 MSI - the command line preview feed is no longer maintaned