Member Avatar for Solution Hall

Hello!

Good Day to All,

I am working on Visual Studio 2015.
I have two workstation computer systems, in both same operating system and Visual Studio is installed.

When i Build the main project it succeeded, and no any problem and my project runs normally on both systems.
Then i made a Setup And Deployment project to the solution using the Category...
Other Projects => Visual Studio Installer => Setup Project

The Setup project made successfully and i am able to install my application from this setup project any other computer system.

But problem is that when i needed to work on my other computer system, i copy the entire solution to that computer and after making some work i Build the main project and it was Build Successfully and my project is executing normally as on the other machine. But as i tried to Build the Setup Project then it Failed but the strange thing is that there are no any error came and the error list was empty.

I Tried many time but Build was failed in the same way every time.
Then i added a new setup project and then try to Build it but it Failed in the same way that no error came and the error list was empty ............. !!!!!!

I am very worried what the problem was ????

The more strange thing is that i copied the entire solution to my previous computer system and i was quit wonder that on that computer both the setup projects was build successfully.

Can anyone guide me what the problem is ????

Thanks a lot for this act of kind as this glitch is just pinching my brain.

Best Regards:
Solution Hall

  • 2 Contributors
  • 1 Reply
  • 381 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by rproffitt

Dani AI

Generated

A short expert note that complements the thread from and : a Setup/.vdproj build that shows "Failed" but produces no Error List entry is almost always an environment or configuration problem (different VS extensions/updates, missing outputs, broken file references, or suppressed build messages). 's clean suggestion is useful; the checklist below expands diagnostic steps and gives practical ways to reveal the hidden error.

  • Increase build diagnostics: Tools → Options → Projects and Solutions → Build and Run → set "MSBuild project build output verbosity" to Detailed or Diagnostic, then rebuild and inspect the Output window (choose "Build").
  • Remove stale state: Clean Solution, then delete solution-level caches and intermediate folders (.vs, *.suo, each project's bin and obj folders).
  • Confirm installer support: ensure the Visual Studio Installer Projects (.vdproj) extension/support on the failing machine matches the working machine. A missing or mismatched installer extension can fail silently.
  • Check configuration/outputs: open Configuration Manager and make sure the Setup project references the correct configuration (Release/Debug) and that all dependent projects are checked to build. Verify "Primary output" files actually exist in the target bin folder.
  • Inspect Setup project items: in File System and Custom Actions views confirm no absolute or network paths are broken and that any custom action assemblies are present.
  • Permissions/AV/paths: rule out antivirus locking, insufficient rights, or MAX_PATH issues (long paths). Run Visual Studio as Administrator to test.

A reliable way to capture the real error is building from the VS command line. Example:

"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com" "C:\Path\Solution.sln" /build "Release" > C:\Temp\buildlog.txt

If the log still hides the cause, reinstall/repair the Installer Projects extension or repair Visual Studio. As a last resort consider migrating the installer to WiX/Inno/Wix Toolset or another packaging tool so builds are driven by msbuild and CI.

Member Avatar for rproffitt

I do not have this version to test with but some other. But I did have build issues a few years back and after some thinking I tried the CLEAN SOLUTION and the next time it did build. https://docs.microsoft.com/en-us/visualstudio/ide/building-and-cleaning-projects-and-solutions-in-visual-studio?view=vs-2017 and other articles note this.

Choose Clean Solution to delete any intermediate and output files.

When you copy projects around you could trip over this and will need to use the clean option.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.