Hello,
i am using version 6.0 an have some problems by configuration my IIS-Site.
i am not able to set 'script socure access', changing 'application protection' and ich can not 'default.aspx' as a default content page.
furthermore i am not able so change ASP.NET version is.
all these settings have no effect on my finish install-routine.
it's a win32-Setup project.
any ideas, how can i solve my problem?
best regards
Chris
Problems with configuration IIS-Sites
Problems with configuration IIS-Sites
Last edited by RetroMind on Fri Oct 27, 2006 1:04 am, edited 1 time in total.
-
- Posts: 904
- Joined: Thu Dec 22, 2005 7:03 pm
- Contact:
Hi Chris,
All of these appear to be supported using the pre-built MSIcode commands.
Can you provide any other details on the problem so we can track it down better?
All of these appear to be supported using the pre-built MSIcode commands.
Can you provide any other details on the problem so we can track it down better?
Candice Jones
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
Hello,
this code-part is placed in the MSIcode:
I have tried this code-part on several positions in the code, always the same effect.
Best regards
Chris
this code-part is placed in the MSIcode:
Code: Select all
~InstallAware Clipboard Data~
~Create Virtual Folder~
~{F5C0B08D-3214-4386-8D5B-671E1196F98C}~
~$KUNDE$~
~$WWWROOTDIR$\\$KUNDE$~
~TRUE~
~TRUE~
~FALSE~
~FALSE~
~TRUE~
~TRUE~
~2|~
~1|2~
~TRUE~
~Default.aspx,Default.htm,Default.asp,index.htm,Default.asx~
~~
~TRUE~
~TRUE~
~FALSE~
~~
~~
Code: Select all
Create Virtual Folder "$KUNDE$" in IIS Site #, pointing to physical location $WWWROOTDIR$\\$KUNDE$
I have tried this code-part on several positions in the code, always the same effect.
Best regards
Chris
-
- Posts: 904
- Joined: Thu Dec 22, 2005 7:03 pm
- Contact:
You need to provide a site index number, otherwise there is no way for IIS to know which site you are creating your virtual folder within.
Candice Jones
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
I'm having basically the same problem using version 6.4. The ASP.NET version is not getting set properly when I run the installer against Windows XP SP2 with IIS installed.
It creates the virtual directory and puts all of the files in the right places, but the ASP.NET version is not being set to 2.0.xxxx.
This is the line that I'm using, but I don't see any mention of ASP.NET 2.0. Not sure if it's even here. Do I need to set an IIS property manually to get that to work?
It creates the virtual directory and puts all of the files in the right places, but the ASP.NET version is not being set to 2.0.xxxx.
Code: Select all
~InstallAware Clipboard Data~
~Create Virtual Folder~
~{D55E07A2-2DD0-4FE6-AD93-2E6CDE7BB88D}~
~$FOLDER$~
~$TARGETDIR$~
~FALSE~
~TRUE~
~FALSE~
~FALSE~
~TRUE~
~TRUE~
~2|~
~1|2~
~TRUE~
~Default.aspx~
~~
~TRUE~
~FALSE~
~FALSE~
~~
~$WEBSITEINDEXVAR$~
Code: Select all
Create Virtual Folder "$FOLDER$" in IIS Site #$WEBSITEINDEXVAR$, pointing to physical location $TARGETDIR$
This is the line that I'm using, but I don't see any mention of ASP.NET 2.0. Not sure if it's even here. Do I need to set an IIS property manually to get that to work?
I was able to get around this by making a call to:
aspnet_regiis.exe -iru
followed by a call to:
aspnet_regiis.exe -s W3SVC/$WEBSITEINDEXVAR$/ROOT/$FOLDER$
It appears that setting the ASP.NET version doesn't work properly if it's installed, but not registered with the websites.
From what I'm seeing, I'm very pleased overall. There seems to be multiple ways to solve most problems, which would make working around bugs pretty easy.
aspnet_regiis.exe -iru
followed by a call to:
aspnet_regiis.exe -s W3SVC/$WEBSITEINDEXVAR$/ROOT/$FOLDER$
It appears that setting the ASP.NET version doesn't work properly if it's installed, but not registered with the websites.
From what I'm seeing, I'm very pleased overall. There seems to be multiple ways to solve most problems, which would make working around bugs pretty easy.
Who is online
Users browsing this forum: No registered users and 12 guests