Randolpho said:
nosajis wrote:
I'm looking for any help I can get here.  I made a very simple web project.  It has four pages.  I then added a web setup project to my solution and added the primary output and content.

When I right click on the setup project and say build the main project builds but the setup project fails.  As far as I can tell, it just says 1 built and 1 failed.  I cannot even find a reason WHY it failed.

HINTS?!  Anybody know where I can even look to get more info about what failed?

Thank you - oh masters of web setup projects.


Arise, dead thread!

I'm just posting this for posterity: I had the same issue: both a web setup project *and* a CAB project would simply fail, with no reason given.

But I went to the output folder, and lo and behold, there were my project files.

I guess it's a bug in visual studio. It *does* successfully build, it just returns an error code.

wierd, huh?

It's not just web setup projects... I've got a Setup project for a Windows Service which suffered the same symptoms and I spent the last 2-3 hours pulling out my hair, trying to make any sense of it.

What killed me is that I've got another project with the same scenario that works in VS2008... I believe I upgraded it some time ago from VS2005 to VS2008.  I also think it's targeting .NET 2.0 only and not .NET 3.5... perhaps that's the difference.  I compared them side by side and could not find a difference in installer classes, setup project, etc.

My solution was giving me the now dreaded "1 successful, 1 failed", with no error text.  I tried setting the output to Detailed and ultimately to Diagnostic... still nothing indicating where an error might have occured.

I even went so far as to create a new Windows Service (WindowsService1, wouldn't you know!) and added zero code to it, except the installer class.  I then added a new Setup Project, selected the primary output and also added the primary output as custom actions.  Same result, 1 successful, 1 failed.

Google brought me here, and indeed after reading Randolpho's post, I checked the output directory.  There it was, perfect in all it's glory... mocking me for being so thorough as to create a new vanilla solution but not to think to check the output directory.

It's a VS 2008 bug... perhaps to be fixed in SP1 due out this summer?  I can't find a list to confirm, but can only hope.