Ok, this is real frustrating. I have a project that includes a setup project. For the past 2 months I've been compiling and building the setup project (and installing it) without problems.
Now, for some reason as soon as the setup proj tries to build the MSI file the Windows Installer launches. I get "Please Wait While WIndows Configures Visual Studio .NET Enterprise." Then another box pops up saying:
"Error 1706. No valid source could be found for product Visual Studio .NET Enterprise Architect. Then Windows Installer cannot continue."
Then the damn thing starts all over again with the installer, the error message, and again. It's a nice endless loop of installer attempts. If I click on Cancel when the installer shows itself my setup project seems to complete its build; I don't know yet whether the MSI file was created properly. It's especially frustrating because I ran the build a number of times yesterday without this problem. Nothing has changed on my computer.
Did Microsoft figure I'd be so bored compiling my applications after a certain number of times and just throw this in to see how quickly I would eject my monitor through the window after watching their infinite loop?
If anyone knows what might be happening here I'd appreciate some assistance. As you can probably gather, this problem is getting on my nerves.
Thanks,
Oli
Now, for some reason as soon as the setup proj tries to build the MSI file the Windows Installer launches. I get "Please Wait While WIndows Configures Visual Studio .NET Enterprise." Then another box pops up saying:
"Error 1706. No valid source could be found for product Visual Studio .NET Enterprise Architect. Then Windows Installer cannot continue."
Then the damn thing starts all over again with the installer, the error message, and again. It's a nice endless loop of installer attempts. If I click on Cancel when the installer shows itself my setup project seems to complete its build; I don't know yet whether the MSI file was created properly. It's especially frustrating because I ran the build a number of times yesterday without this problem. Nothing has changed on my computer.
Did Microsoft figure I'd be so bored compiling my applications after a certain number of times and just throw this in to see how quickly I would eject my monitor through the window after watching their infinite loop?
If anyone knows what might be happening here I'd appreciate some assistance. As you can probably gather, this problem is getting on my nerves.
Thanks,
Oli