Home/ Questions/Q 595471
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T16:03:56+00:00

PLEASE READ THE FULL QUESTION BEFORE POST YOUR ANSWER Hello guys! I’m currently developing

  • 0

PLEASE READ THE FULL QUESTION BEFORE POST YOUR ANSWER

Hello guys!
I’m currently developing a “Extremelly customized Installer Application” in C# for installing a old classic ASP application. It’ll be used during the 2.0 version is developed (ASP.NET MVC with C#).

As its so different from the efault install packages, I’ve made it as normal windows application, not as setup application (a setup application don’t let us customize so much as I need).

And here is the problem: As its a windows application, I must “Release” it and send the compiled .EXE with the .DLLs, I must not “Publish” because if i do so, the published .EXE will “install the installer” and not my application. I need a way to verify and install the .NET Framework 3.5 like a bootstrap package prerequisite used in publishing option, but remember that I’m not publishing, I’m doing a “Release” build.

Thanks for any help!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Maybe it will help if you stop thinking about it being an installer but consider it a configuration utility. That needs an installer before it can run. Just create a regular Setup project for it, one that automatically launches the utility after it is installed. Check this thread for an example on how to do that.

    • 0