Disappointed

[jdixon]

It could just be me but I find Advanced Installer very difficult to use and get right. I find myself wasting more time dealing with the installer and problems it causes than actually writing the application. I'm attempting to deploy a MVC application to IIS while it also creates the database (first time installs) and updates the settings.xml file with new elements that I put in there.

What I find is it will mess up the comments in the settings.xml, not put the new elements in correctly, or overwrites the existing one.

It has really been a huge headache and I hate that I can't upgrade without paying another $1000 that may resolve my issue. I wish it worked out

[jdixon]

I guess what i'm asking is if anyone else is having trouble with XML files. Basically this is what i've been trying to do:

[*] Create IIS website if they enter a website that isn't created (but don't create the virtual directory)
[*] IF they enter an existing IIS website then create a virtual directory called CloudPanel
[*] Create database (this works)
[*] Set the SQL connection string in the settings.xml file (this works sometimes)
[*] Create additional elements in settings.xml if this is an upgrade and they are not there (This doesn't work most of the time or it puts them in an odd format which is invalid xml.. like: <!-- <!-- This is a coment --> --> )

On the XML what it does sometimes is completely wipe out the settings and put the default. Talking with Advanced Installer they tell me that those elements only work if they are in there on the previous install. I think what they meant is when I add a new element <ExchangeServerBackup></ExchangeServerBackup> it won't add on that new install I just did but it will add on the next install if they upgrade in order (so basically I have to know the future 2x ahead)

[Daniel]

Hello,

We are really sorry to hear this. Indeed, our XML Update support has some limitations. Since we really want to try helping you find out a resolution, can you please give us a detailed test case in which you have failed to accomplish your installation requirements?

For instance you can try to isolate the behavior in a buildable sample (.AIPs + their referenced files) which we can build and test on our side.

All the best,
Daniel