Hi All,
I have a solution converted from VS 2005 to VS 2008 (no problems during the conversion). It contains C# projects only. When I build setup it says something like
Rebuild All: 3 succeeded, 1 failed, 0 skipped
But there are no error or warning messages neither in errors list nor in output. All projects are built correctly, the msi file and setup.exe file are created successfully. Each project is solution gives no error when I build it separately.
Not that it creates me any problems but I would like to know the reasons for "1 failed" message. Any ideas?
Thanks,
Artem | | Artem Kliatchkine Thursday, February 28, 2008 9:29 AM |  interesting observation ... do you mind pasting your output window stuff here ?? | | Praveen K. Jha Sunday, March 02, 2008 10:16 PM | We are changing the issue type to "Comment" because you have not followed up with the necessary information. If you have more time to provide more information, please feel free to change the issue type back to "Question" by editing your initial post and changing the radio button at the top of the post editor window. If the issue is resolved, we will appreciate it if you can share the solution so that the answer can be found and used by other community members having similar questions.
| | Chunsheng Tang Wednesday, March 05, 2008 5:39 AM | I have run into the same problem. I created a windows form project. Added a setup project and then attempted to build solution in debug and release. I get the following:
Code Snippet
------ Rebuild All started: Project: test, Configuration: Debug Any CPU ------
D:\WINDOWS\Microsoft.NET\Framework\v3.5\Vbc.exe /noconfig /imports:Microsoft.VisualBasic,System,System.Collections,System.Collections.Generic,System.Data,System.Drawing,System.Diagnostics,System.Windows.Forms,System.Linq,System.Xml.Linq /optioncompare:Binary /optionexplicit+ /optionstrict:custom /nowarn:42016,41999,42017,42018,42019,42032,42036,42020,42021,42022 /optioninfer+ /rootnamespace:test /doc:obj\Debug\test.xml /define:"CONFIG=\"Debug\",DEBUG=-1,TRACE=-1,_MyType=\"WindowsForms\",PLATFORM=\"AnyCPU\"" /reference:"D:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Core.dll","D:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Data.DataSetExtensions.dll",D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll,D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Deployment.dll,D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll,D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll,D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Windows.Forms.dll,D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll,"D:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Xml.Linq.dll" /main:test.My.MyApplication /debug+ /debug:full /filealign:512 /out:obj\Debug\test.exe /resource:obj\Debug\test.Resources.resources /target:winexe ApplicationEvents.vb Form1.vb Form1.Designer.vb "My Project\AssemblyInfo.vb" "My Project\Application.Designer.vb" "My Project\Resources.Designer.vb" "My Project\Settings.Designer.vb"
test -> E:\Documents and Settings\jdarnell\My Documents\Visual Studio 2008\Projects\test\test\bin\Debug\test.exe
------ Starting pre-build validation for project 'Setup1' ------
------ Pre-build validation for project 'Setup1' completed ------
------ Rebuild All started: Project: Setup1, Configuration: Debug ------
Building file 'E:\Documents and Settings\jdarnell\My Documents\Visual Studio 2008\Projects\test\Setup1\Debug\Setup1.msi'...
Packaging file 'test.exe'...
========== Rebuild All: 1 succeeded, 1 failed, 0 skipped ==========
It is the setup project that fails but I don't understand why. . .
JD
| | JD5309 Thursday, March 06, 2008 3:45 PM | I am having the same issue. Does anyone know of a solution? | | sscowden Saturday, March 15, 2008 3:18 AM | I'm having the exact same problem.
I have two projects, both of which build fine.
The setup project then builds, returns as failed, but the MSI seems to be built fine.
I have tried removing the setup project and creating a totally blank new one, without even linking it to the other two projects, but when I build the solution I still get the same thing.
I've got Diagnostic level build output on and there is no mention of anything failing at all in there.
I think that I migrated the solution from VS2005 as well, although I couldn't guarantee it.
Any help, advice or ideas would be greatly appreciated.
Cheers,
Jeremy
| | Jeremy Walker Monday, March 24, 2008 5:57 PM | I've just gone through and recreated the solution and the projects from scratch, copying the relevant files between directories.
Doing that has sorted the problem.
I think it is an issue with the 2005 -> 2008 transfer but I have no more ideas than that.
Cheers,
Jeremy
| | Jeremy Walker Monday, March 24, 2008 6:52 PM | I have the same problem.
I have created this morning a new "Web Setup Project" in an existing Solution (VS.Net 2008). It is intended to deploy one web site and 3 libraries. All of these build correctly.
Only the build of the new "Setup Project" reports a failure without any additional info (and nothing in the eventlog).
However, the .msi is well created and seems to work fine...
Code Snippet
------ Build started: Project: Company.Framework.Configuration.Repository.Entities, Configuration: Debug Any CPU ------
Company.Framework.Configuration.Repository.Entities -> Company.Framework.Configuration.Repository.Entities\bin\Debug\Company.Framework.Configuration.Repository.Entities.dll
------ Build started: Project: Company.Framework.Configuration.Repository, Configuration: Debug Any CPU ------
Company.Framework.Configuration.Repository -> Company.Framework.Configuration.Repository\bin\Debug\Company.Framework.Configuration.Repository.dll
------ Build started: Project: Company.Framework.Configuration.Repository.Provider, Configuration: Debug Any CPU ------
Company.Framework.Configuration.Repository.Provider -> Company.Framework.Configuration.Repository.Provider\bin\Debug\Company.Framework.Configuration.Repository.Provider.dll
------ Build started: Project: Company.Framework.Configuration.Repository.Host, Configuration: Debug Any CPU ------
Company.Framework.Configuration.Repository.Host -> Company.Framework.Configuration.Repository.Host\bin\Company.Framework.Configuration.Repository.Host.dll
------ Starting pre-build validation for project 'Company.Framework.Configuration.Deployment' ------
------ Pre-build validation for project 'Company.Framework.Configuration.Deployment' completed ------
------ Build started: Project: Company.Framework.Configuration.Deployment, Configuration: Debug ------
Building file 'Company.Framework.Configuration.Deployment\Debug\Company.Framework.Configuration.Repository.msi'...
Packaging file 'Company.Framework.Factory.dll'...
Packaging file 'Company.Framework.Communication.dll'...
Packaging file 'Company.Framework.Configuration.Repository.Provider.pdb'...
Packaging file 'Company.Framework.Configuration.Repository.Provider.dll'...
Packaging file 'Web.config'...
Packaging file 'Company.Framework.Diagnostics.Instrumentation.dll'...
Packaging file 'Company.Framework.Configuration.Repository.Host.dll'...
Packaging file 'Company.Framework.Configuration.Repository.dll'...
Packaging file 'Company.Framework.Configuration.Repository.Provider.dll'...
Packaging file 'Company.Framework.Configuration.Repository.dll'...
Packaging file 'Company.Framework.Configuration.Repository.pdb'...
Packaging file 'Company.Framework.Configuration.Repository.Host.pdb'...
Packaging file 'Company.Framework.Configuration.Repository.Entities.dll'...
Packaging file 'ConfigurationRepository.svc'...
Packaging file 'Company.Framework.Environment.Platform.Provider.dll'...
Packaging file 'Company.Framework.Environment.Platform.dll'...
Packaging file 'Company.Framework.Configuration.Repository.Entities.pdb'...
Packaging file 'Company.Framework.Configuration.Repository.Entities.dll'...
========== Build: 4 succeeded or up-to-date, 1 failed, 0 skipped ==========
I am affraid that there could be some hidden issues with the resulting msi, as it will be used to deploy our application in a production environment (after testing for sure! However...) | | Valery Letroye Monday, March 31, 2008 9:47 AM | I'm also running into the same problem. I found a similar thread here, but the issue still has not been resolved. Here is my output:
Build Output
------ Starting pre-build validation for project 'D2ConfigurationSetup' ------
------ Pre-build validation for project 'D2ConfigurationSetup' completed ------
------ Build started: Project: D2ConfigurationSetup, Configuration: Release ------
Building file 'C:\BDM\D2\D2ConfigurationSetup\Release\setup.msi'...
Packaging file 'AjaxControlToolkit.dll'...
Packaging file 'D2Configuration.dll'...
Packaging file 'MigrationObjectLibrary.dll'...
Packaging file 'Microsoft.ApplicationBlocks.ExceptionManagement.Interfaces.dll'...
Packaging file 'Microsoft.ApplicationBlocks.Data.dll'...
Packaging file 'Microsoft.ApplicationBlocks.ExceptionManagement.dll'...
Packaging file 'Utils.dll'...
========== Build: 3 succeeded or up-to-date, 1 failed, 0 skipped ========== | | jerhinesmith Thursday, April 03, 2008 4:58 PM | This is an issue that we have some knowledge about.
When a Link to SQL class is added to the project it adds some things that erroneously causes a communication error between the setup project and the other project. This erorr causes the setup project to report a build failure.
In actuality the build has not failed, and the error doesn't seem to cause any change in the setup project's behavior. In other words, the build is actually successful and correct.
This is a known issue that has not yet been fixed yet. It is on the radar and in the plan, but we cannot promise when this issue will be fixed. I wish I could give more specific information, but I personally will continue to push to get this fixed as soon as is reasonable.
I know this doesn't help with build scripts, which is one of the key reasons to push for the fix.
I do hope this helps to alleviate concerns, or at least clarifies the situation a bit. | | David Guyer MSFT Monday, April 07, 2008 5:45 AM |
Also, if you want to help encourage this bug to be fixed... go to the http://connect.microsoft.com site and add a vote to ID 317870
| | David Guyer MSFT Monday, April 07, 2008 5:49 AM |
|
index > ClickOnce and Setup & Deployment Projects > Setup build reports error but the msi is created