also seeing this behavior --> installshield 2012, onto windows server 2008 R2 - not including a file named WEB.CONFIG, but seeing the file after installation wondering the same thing - what process is creating the WEB.CONFIG - is it INSTALLSHIELD when creating a virtual director and/or application? or is it something in IIS that detects a "missing" file and sticks one in there? and regardless of what is responsible, is it possible to disable that "feature" ??? ... View more

thanks - that worked just like i wanted! 🙂 ... View more

DISCOVERY! 1st, another piece of background info = installed under "Default Web Site" which was set to ASP.NET 4.0 --- so, i discovered that if i removed the ASP.NET 4.0 setting, the package gets delivered okay well, "okay" in that you just have to go into IIS afterward and specify 4.0 under the site's ASP.NET tab but that seems like a small sacrifice - or does it? ... View more

installed that hotfix - so far so good ~ no more crashes!! 🙂 ... View more

JohnBrent wrote: ... i'm so confused ... 😞 maybe not after rebuilding the package a few more times, running the setup now croaks at the "calculating size requirements" billboard maybe i shouldve included the following info earlier, but ... this install package is part of a Visual Studio 2010 project --- and i think the installation is getting corrupted by VS what other explanation can there be for INSTALLDIR now pointing to some non-local device? [aside - i've built a new package completely separated from VS & it works fine 🙂 ] ... View more

interesting ... i changed my "Look in-full path" to SUPPORTDIR but that didnt work (appears to be undefined at this point?) then i changed it to SOURCEDIR - and that worked! BUT now my DESTINATION_FOLDER dialog shows that my INSTALLDIR has changed to the exact path to the web.config file in the "sourcedir" here's what INSTALLDIR should be, as specified in the General Info page = [ProgramFilesFolder]VOLT Delta\ReplicationDirector (which should be C:\program files\...) here's the string that shows up as INSTALLDIR on the DESTINATION_FOLDER dialog = E:\INSTALLATION MEDIA\repdir004\DISK1\program files\VOLT Delta\ReplicationDirector\Web.config\ ... i'm so confused ... 😞 ... View more

thanks - yeah, i did that stuff - i looked in the list of dialogs with the direct editor, but it wasnt there - for all i could see, i had erased all mention of it from my project BUT when i built it, the log showed that the dialog was still being built - and sure enough, when i ran the installation, it was still presented so i gave up & started from scratch the end ... View more

plan = 1. package an installation that includes the file "xxxxx.config" 2. have the installation present a dialog that will gather info with which to modify file xxxxx.config 3. have that dialog pre-populated with the data from file xxxxx.config 4. NOT have to know where the installation media resides system = C:, D:, E:, F: package 1 works = 1. installation media copied to temp folder on local drive E: 2. file name = "applicationxyz.exe.config" 3. system search of path "\" finds file & extracts XML values 4. dialog presents values, accepts new values 5. TXT CHANGE wizard applies new values to designated file package 2 didn't work as follows = 1. installation media copied to temp folder on local drive E: 2. file name = "web.config" 3. system search finds 1st file with that name - it's the wrong file, so values are not extracted 4. dialog fields are blank 😞 5. installation stopped 😞 package 2 didn't work as follows = 1. installation media copied to known folder on local drive C: 2. file name = "web.config" 3. system search to known path finds file, values are extracted 4. dialog presents values, accepts new values 5. TXT CHANGE wizard does NOT modify file package 2 DOES work as follows = 1. installation media copied to known folder on local drive C: 2. package includes web.config (to be modified) and copy of web.config (renamed "uniquename.config" 3. system search of path "\" finds unique file, values are extracted 4. dialog presents values, accepts new values 5. XML CHANGE wizard successfully updated web.config ... View more

JohnBrent wrote: if i needed to search for something with a name like WEB.CONFIG, i'd be screwed unless i knew the exact path to look in in my installation package that successfully modified an included .CONFIG, the filename was "appname.exe.config" - and i used the TXT CHANGE wizard - yay for me as i tried to apply the things i did in the successful package to a new installation - one where the contents are an ASP web site - and the file i want to change is WEB.CONFIG --- i found that what i learned the 1st time around don't work so well this time apparently, you can't modify a file named "web.config" with the TXT CHANGE wizard -- i'm guessing because that's a protected file??? (not because of any MS attribute, but because it's a web page file???) BUT using the XML CHANGE wizard works like a champ changing that pesky web.config yay for me again 🙂 the only hack i had to employ was to include a copy of the web.config pre-renamed to some unique name - so that i don't have to know the exact path to the file & so that it wouldnt get lost among all the other web.configs on the system ... View more

well, it works because ... (1) the installation media was copied to a local drive this allows the SYSTEM SEARCH to find the file i need to examine, even tho at install-time it only exists in the installation (2) the file i need to examine has a unique name if i needed to search for something with a name like WEB.CONFIG, i'd be screwed unless i knew the exact path to look in ... View more