When setting up a setup project for a .NET 2.0 windows service in Visual Studio 2008 I ran into a novel problem this morning -- the setup project itself would always fail to build but wouldn't leave any error messages behind.
A Google search turned up a recent complaint about this in StackOverflow (http://stackoverflow.com/questions/847893/visual-studio-setup-and-deployment-build-fails-with-no-errors) but it wasn't exactly on target.
It provided enough clues to give me a workaround -- it seems to be related to the LINQ to SQL add-ins when making the setup project. The temporary answer was to create a new setup project, explicitly making it a .NET 2.0 project, and then try the build.
This made it work fine.
It'd be interesting to try and find a good solution for the problem but this works for now.
Subscribe to:
Post Comments (Atom)
1 comment:
A comment to myself ... I just installed WinSDK (both .NET Framework 2.0 and 3.5 versions -- I needed 2.0 for the code-level-security tools referenced in the 70-536 exam). Perhaps that had something to do with this new behavior?
Post a Comment