Timeline for Is it a good idea to include Installer Project within single solution?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19, 2013 at 19:53 | comment | added | Brian | Solution Load Manager for VS2010 may or may not be relevant to your problem. | |
| Feb 19, 2013 at 18:54 | answer | added | Arseni Mourzenko | timeline score: 1 | |
| Feb 19, 2013 at 9:46 | comment | added | Arseni Mourzenko | In large projects, nightly builds are used. The nightly build can sometimes take hours. Those of the companies which use external solutions like Windows Installer XML (WiX) are using them not because the ordinary installer project is slow, but because it is missing features they need. | |
| Feb 19, 2013 at 9:34 | comment | added | sarat | to add upon, in the large projects how developers managing the the installer projects? Is it in the same way? or they work with some scripts or external solution itself to make the packages? | |
| Feb 19, 2013 at 9:07 | comment | added | Arseni Mourzenko | If I remember well, installer projects have an option which you can turn on and off which actually builds the setup.exe; by default, it's turned off. Also, disabling projects (even other than the installer) is totally ok to optimize the compile time (and the time it takes to open the solution in Visual Studio). | |
| Feb 19, 2013 at 8:46 | history | asked | sarat | CC BY-SA 3.0 |