.net version for entire website erroneously being changed: We are using ISLE 2011 to install an ASP.NET app to IIS on w2003 and 2008. We want the setup to create the new app in the existing website (if any), and set the .net version of this new app to .net4 - but do NOT change the .net version of the root site or any other apps in the site. To try to do this, in isle iis view we create a new website with port=80, sitenumber=0 (that is, use the existing site, if any), and left the site's "ASP.NET version" property blank. We then created our new app in this site, and set the ASP.NET version to 4.0.30319. This does not work. After the installer runs, the existing web site, and all existing web apps, are moved to a new .net 4 app pool called "ASP.NET v4.0 Default App Pool". We looked in the win installer log, and it seems ISLE is executing aspnet_regiis.exe 3 times: 1) aspnet_regiis.exe -ir (this installs aspnet.) 2) aspnet_regiis.exe -k w3svc/1/root 3) aspnet_regiis.exe -s w3svc/1/root I think #2 and #3 are the problem - shouldn't they be for just the new app, not the entire root (that is the website)? This install breaks .net 2 apps that currently exist on the server. How can we get ISLE to use the correct path for #2 and #3? ... View more

I am using ISLE 2011. I need to redistribute the SQL Server native client (for 2008 R2, preferably) with my setup program. This link says Installshield 2011 includes SQL native client redistributables: http://blogs.flexerasoftware.com/installtalk/2011/03/deploying-legacy-web-applications-with-the-latest-version-of-sql-server.html However, I don't see these redistributables in my ISLE UI. How can I add them? Thanks! ... View more

I am using ISLE 2011 with an ASP.NET app. When I build the setup project in VS2010 (interactively), the setup program will put all of the .net assemblies for other projects in the solution that the web project is dependent on into the web app's bin folder (well, it actually puts them in the app\bin\bin folder, as described in another post.) However, when I build the exact same solution from TFS build, the only file that the resulting setup.exe program puts into the app's bin folder is the assembly for the web project itself - all of the dependent assemblies are missing! The setup is configured to put the "Primary Output" of the web project into an explicitly defined folder called "bin" under the [INSTALLDIR]; when I click "resolve project output", it only shows the one assembly for the web project itself, but when I click on "dependencies from scan at build", it shows all of the dependent assemblies. I also checked the .net "Scan at build" setting for the "primary output" element; it is set to "dependencies and properties". Is this correct? How can I fix this? ... View more

I am using ISLE-2011 to setup an asp.net app on windows 2008, including setup a new web site and application in IIS. There appears to be a known issue where the install will fail on 2008 if web.config that is being installed is marked as read-only. I am specifying this file in ISLE indirectly, via the ASP.NET web project's "Content Files". I tried clicking on this "Content Files" entry in my "destination computer's files" (bottom right pane in ISLE files view), right clicking, select properties, checking the "Override System attributes", and then making sure the "Read Only" checkbox is clear. However, this does not fix the problem. I verified that adjusting the "Content Files" entry's settings this way seems to have no effect on the files installed by manually changing the actual web.config file's read-only attribute to false, and then successfully installing. At this point, I view the attributes of the the files installed, and all the installed files except web.config are still set to read-only, even though I set the "Override System attributes" box and cleared the "read only" box for the "Content files" entry. I'd like to continue to use the "Content files" entry, instead of manually linking to files, because it avoids missing files when added, and also manually adding explicit links seems to put the full path to the file - which won't work for me because I'm using tfs build. How can I get "web.config" to be copied via "Content files" but still be marked as not-read-only, without having to actually set the web.config file to not be read only? I don't want to set the actual file to be not read only because I'm reading the files from TFS via tfs build (msbuild.) I suppose I could create some custom build step somewhere that changes the file attrib somewhere or checks out the file, but that seems hokey. ... View more

We want to create an installer for an asp.net app using ISLE 2011. We want to target iis 5.1 thru 7.5. We noticed then when we install our app on a clean ii6 install, aspx functionality (referred to in iis6 as a "web service extension") isn't allowed (it remains set as prohibited.) Is there an easy way to get the installer to enable the aspx web service extension in ii6 (if we're installing on ii6)? Will this also work for the iis7.5 "Isapi and CGI Restrictions" (that is, do we need to do a similar thing there)? Thanks! ... View more

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? ... View more

I have Installshield 2011 Limited Edition. Where do I mark a given installation as 64bit or 32bit? Some of the discussions imply that ISLE doesn't support x64 installations. This can't be true, right? This was a single-click change (set the TargetPlatform to x64) in the Visual Studio setup projects that ISLE is replacing. The ISLE help file has a whole section on "Windows Installer on 64-bit Operating Systems", and it discusses setting the "Template Summary" property, but it does not tell you how to do it. Thanks ... View more