This post originated from an RSS feed registered with .NET Buzz by Scott Hanselman. Original Post: Web Setup MSI fail when used on Servers with the Loopback Adapter installed Feed Title: Scott Hanselman's ComputerZen.com Feed URL: http://radio-weblogs.com/0106747/rss.xml Feed Description: Scott Hanselman's ComputerZen.com is a .NET/WebServices/XML Weblog. I offer details of obscurities (internals of ASP.NET, WebServices, XML, etc) and best practices from real world scenarios. Latest .NET Buzz Posts Latest .NET Buzz Posts by Scott Hanselman Latest Posts From Scott Hanselman's ComputerZen.com

Travis, who works with me, sent out a useful Gotcha today that was too useful to not blog.

We have a VM that requires the Host OS to use the Microsoft Loopback Adapter in order to create an internal subnet that is local to that machine.  It keeps the VM sequestered. 

However, due to the way the Loopback Adapter works, Visual Studio Web Setup Projects (MSIs) will fail.  To fix it, disable the Loopback Adapter, run the install, then enable the adapter.

(The problem is that, on install, the installer looks at the path it's going to install to and it comes back like http://machinename/http://machinename/targetpath <http://machinename/http:/machinename/targetpath>  - note the looping back going on there.  The installer doesn't like that.)

Interesante, but that's what you get when you do unusual stuff, eh?