This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: no asp.net bin folder!
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 11, 2011
05:22 PM
no asp.net bin folder!
I am using VS2010 with ISLE 2011 to create an installer for an ASP.NET app. This type of app puts the built DLLs in the bin subfolder. If I create an installer that puts both the primary output and content output of the asp.net app into the INSTALLDIR, everything works fine with the installer created by VS; the DLLs end up in the bin subfolder of the install dir.
However, if I build the same project either locally using msbuild from the cmdline, OR remotely via TFS build, the installer doesn't create a bin folder at all (the DLLs instead end up in the INSTALLDIR), and of course the app doesn't work. (it does work if, after install, I manually create the bin subfolder and copy the DLLs there.)
So...I can also get things to work the opposite way: if I configure the installer to put the content in the INSTALLDIR and the primary output in an explicitly created subfolder of INSTALLDIR called "bin", then when I build with VS, the generated installer puts the DLLs into the [INSTALLDIR]\bin\bin folder! Of course the app doesn't work. However, if instead of VS I use either the local msbuild or remote tfs build, the installer puts the DLLs correctly in [INSTALLDIR]\bin and the app works.
So....how can I get the installers built with both VS AND msbuild/tfs build to work correctly? It is scary that the output the developer sees in VS is completely different than what occurs with msbuild/tfs build.
I have seen some forum discussions on the net that seem to refer to this bin\bin problem from back in 2003. Is this a long standing problem? Is there a known fix?
However, if I build the same project either locally using msbuild from the cmdline, OR remotely via TFS build, the installer doesn't create a bin folder at all (the DLLs instead end up in the INSTALLDIR), and of course the app doesn't work. (it does work if, after install, I manually create the bin subfolder and copy the DLLs there.)
So...I can also get things to work the opposite way: if I configure the installer to put the content in the INSTALLDIR and the primary output in an explicitly created subfolder of INSTALLDIR called "bin", then when I build with VS, the generated installer puts the DLLs into the [INSTALLDIR]\bin\bin folder! Of course the app doesn't work. However, if instead of VS I use either the local msbuild or remote tfs build, the installer puts the DLLs correctly in [INSTALLDIR]\bin and the app works.
So....how can I get the installers built with both VS AND msbuild/tfs build to work correctly? It is scary that the output the developer sees in VS is completely different than what occurs with msbuild/tfs build.
I have seen some forum discussions on the net that seem to refer to this bin\bin problem from back in 2003. Is this a long standing problem? Is there a known fix?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 15, 2011
02:11 AM
Hello Asanford,
I am currently looking into this issue and I should have further information in a day’s time, appreciate your patience on the same.
Thanks,
Madusree
I am currently looking into this issue and I should have further information in a day’s time, appreciate your patience on the same.
Thanks,
Madusree
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 25, 2011
08:38 AM
Hi,
I am currently working with the Support Specialist.
I understand your concern on this Issue, I will update with further information by Monday.
Appreciate your patience on the same.
Thanks,
Madusree
I am currently working with the Support Specialist.
I understand your concern on this Issue, I will update with further information by Monday.
Appreciate your patience on the same.
Thanks,
Madusree
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 28, 2011
12:41 AM
Hello,
Please provide us the sample solution sample solution that reproduces the problem. Also provide us the reproducible steps to perform the build from within Visual Studio.
Thanks,
Madusree
Please provide us the sample solution sample solution that reproduces the problem. Also provide us the reproducible steps to perform the build from within Visual Studio.
Thanks,
Madusree
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)