Using VS2K8 I added a Setup/deploy project to my solution. Reading through various guides online, they all say to "Add Project output" and VS will automatically select the correct files for you. Problem #1: VS doesn't properly select the correct output location of my project files. I end up with errors like:
Code Snippet
Could not find file 'C:\SVN_Projects\SP\trunk\MyXXX\Daemon\obj\Installers\Daemon.exe' 'The system cannot find the file specified.' Solution #1: Manually including the specific file(s) from each project that I need to put in the installer. Problem #2: After resolving the issues from problem #1, I successfully built the installer project. Ran it, verified it works, installs the needed files, etc. Yet, for some reason in the VS output window, it says the build failed. Any ideas why? How can I get more details from it?
Code Snippet
------ Skipped Rebuild All: Project: Config, Configuration: Installers Any CPU ------ Project not selected to build for this solution configuration ------ Skipped Rebuild All: Project: BusinessObjects, Configuration: Installers Any CPU ------ Project not selected to build for this solution configuration ------ Skipped Rebuild All: Project: BusinessLogic, Configuration: Installers Any CPU ------ Project not selected to build for this solution configuration ------ Skipped Rebuild All: Project: Persistence, Configuration: Installers Any CPU ------ Project not selected to build for this solution configuration ------ Skipped Rebuild All: Project: Services, Configuration: Installers Any CPU ------ Project not selected to build for this solution configuration ------ Skipped Rebuild All: Project: ADPicker, Configuration: Installers Any CPU ------ Project not selected to build for this solution configuration ------ Skipped Rebuild All: Project: UnitTests, Configuration: Installers Any CPU ------ Project not selected to build for this solution configuration ------ Skipped Rebuild All: Project: Client (Client\Client), Configuration: Installers Any CPU ------ Project not selected to build for this solution configuration ------ Starting pre-build validation for project 'DaemonInstaller' ------ ------ Pre-build validation for project 'DaemonInstaller' completed ------ ------ Rebuild All started: Project: DaemonInstaller, Configuration: Installers ------ Building file 'C:\SVN_Projects\SP\trunk\MyXXX\Bin\Installers\DaemonInstaller.msi'... Packaging file 'Daemon.exe'... Packaging file 'MyXXX.Services.dll'... Packaging file 'MyXXX.Config.dll'... Packaging file 'CipherLite.dll'... Packaging file 'MyXXX.BusinessObjects.dll'... Packaging file 'MyXXX.BusinessLogic.dll'... Packaging file 'MyXXX.Persistence.dll'... Packaging file 'config.xml'... ------ Skipped Rebuild All: Project: Daemon, Configuration: Installers Any CPU ------ Project not selected to build for this solution configuration ========== Rebuild All: 0 succeeded, 1 failed, 9 skipped ========== |
| BSOD2600 Monday, February 18, 2008 12:52 AM |
I've got this too. A simple win service installed via a Setup project in VS 2008 says it fails but I can't see where (I've tried adjusting the build output verbosity all the way up to diagnostic with no luck).
Any ideas???
|
| ragnasaur Wednesday, February 20, 2008 12:58 AM |
Bump.
Anyone know why the build failed, or how to get more info on the details?
|
| BSOD2600 Tuesday, February 26, 2008 9:07 PM |
I am also having this problem!
I have added a regular Setup Project to my solution, on the Application Folder I have added project output of my windows form application that have dependency's on other projects. This is working fine.
But when I build the Setup Project I get : ========== Rebuild All: 11 succeeded, 1 failed, 0 skipped ==========
The MDI/Setup file seems to be built but I do not know if I should use it?
I have also tried to turn the MSBUILD output from minimal to diagnostic but nothing but warnings can be found!?
Visual Studio 2008 Projects have diffrent frameworks, some use 2.0 and some use 3.5
|
| SnowJim Friday, February 29, 2008 10:03 AM |
Hey!
I have now tested to add a web setup project to my solution as well that handels the deployment of our WCF service, but this setup project also generates the same output?
The setup files simes to work fine even when thay get 1 faild?
|
| SnowJim Tuesday, March 04, 2008 3:20 PM |
Think i Figured this out.
I had pulled the projects in the solution in from a different solution. Then i created the setup proj and added the output of the main project. I also had inter-project references (project references) between the projects. On a hunch i blew away the references and re-added them from the new solution and the build failure went away.
Moral of the story: VS must create some solution level dependency when creating project references.
Ragnasaur
VSIP Partner |
| ragnasaur Tuesday, March 04, 2008 3:26 PM |
Sounds to me like VS2K8 is broken in this aspect. We should've be forced to create new solutions to remove build errors (false or not).
|
| BSOD2600 Wednesday, March 05, 2008 12:49 AM |
There's a similar problem on this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2962231&SiteID=1
I'm having the same problem, the solution builds ok, and an msi file is created, but visual studio reports:
========== Build: 1 succeeded or up-to-date, 1 failed, 0 skipped ==========
No visible errors are displayed. Why is it failing?!
Steve
|
| SteveGlen Thursday, March 13, 2008 5:00 PM |
I'm having the same problem as described here as well. The problem started when some projects were added to the solution. The projects use .NET 3.5 (LINQ) whereas almost all of the existing ones target .NET 2.0. I don't know if that's relevant.
I tried following Ragnasaur's suggestion -- I deleted all of the project references for the added projects and put them back in. That didn't result in any diffs in the project files, and didn't fix the problem. Has anyone else had success with this approach?
|
| EricSmith Tuesday, March 25, 2008 7:50 PM |
A colleague found this bug report that seems describe our problem: Setup Project Always Fails On BuildThere is sort of a workaround there as well. |
| EricSmith Wednesday, March 26, 2008 8:39 PM |