InstallAware

Just wondering if anyone ever found a fix for this? My installer is doing exactly the same. I install between 1 and 3 websites based on the features selected and it looks like whichever is the last Virtual Directory to be created, updates "Default Web Site" and points it's physical path to $TARGETDIR$ rather than the default \inetpub\wwwroot. This is causing me problems as it means 2/3 websites do not work.

Cheers
Adam

Dear Adam,

can you please verify if the following topic helps you?
http://www.installaware.com/forum/viewt ... lt+apppool

If your issue can reproduced as reported with the above topic, it is also described a possible workaround.
The issue reported with the above topic as been added to our fix list.

Let me know if this helps you.

Regards.

Hi Francisco

While this is another problem, I can get around this problem by those exact methods for now.

My problem is that adding a Virtual Directory seems to change the root path for "Default Web Site" from c:\inetpub\wwwroot to the $TARGETDIR$ where the files for my virtual directory is kept. Let me know if you need some screenshots / test project if I'm not making any sense.

Cheers
Adam

Dear Adam,

If you could post me a very simple project ... It might help me to speed any test.

Regards.

Hi Francisco

I created a test project but everything worked as expected. After doing some debugging, I realised that the problem is potentially from creating one website and then Copy and Pasting it, then modifying it to another.

I re-entered the Create Virtual Folder's and it all worked as expected.

Cheers
Adam

Happy that you solved !

I am happy for Adam, but it didn't work for me.
I need to create two virtual folders, and to work around the "ASPNET version bug" I had to split the vdir creation, so I have FOUR create vdir instructions (two for IIS6 and two for IIS7). This is how I did it. I thought I copied/pasted the instructions, as Adam said, so I deleted them and re-created them by hand, but I still have the problem.
This is the end result As you can see, the default website path has been changed to the targetdir.
This is really annoying: we chose IA because it could handle IIS7 and application pool creation, but turns out it does it in a very unreliable way (a few years after IIS7 has been released!).
Any chance you have a new workaround? I am running out of ideas...

Let me see.

Regards

News?
Thanks

Dear User,

Unfortunately I do not have any news.

Could you please send me a very simple project that replicate the issue?

Regards

Did you try the setup I described in my email?
That's the only part of my script that deals with vdir creation. You should try to use variables for most of the params, and the if-then clause to handle the IA ASPNET bug.
Please let me know.

Dear User,

I haven't received any email ... did you send it to: [email protected]?

Regards

Sorry, I meant "previous post" not "email".
In the meantime I will try to strip down my setup, but it's no easy task.

... meantime, have you tried to see what happens using the new NX version (of course, you can use the trial)?

Regards

I can give it a try, but does this mean that with the new NX release you are abandoning 2012 customers???
I mean, don't you support at least the previous version?