How do I install an ASP.Net MVC application on IIS 7 using Wix?

The IIS extensions for WIX don't support IIS7. The IIS team keep rewriting the metabase between versions. There are quite a few things that don't work, the lack of an integrated app pool amongst them Until the extensions get rewritten, you're left with three options: Use build in custom actions to invoke appcmd.

Exe Use XmlConfig to update applicationHost. Config Write your own custom actions I've opted for the xmlconfig option at the moment as you can do this within a component and tie it to a feature.

The IIS extensions for WIX don't support IIS7. The IIS team keep rewriting the metabase between versions. There are quite a few things that don't work, the lack of an integrated app pool amongst them.

Until the extensions get rewritten, you're left with three options: Use build in custom actions to invoke appcmd. Exe Use XmlConfig to update applicationHost. Config Write your own custom actions I've opted for the xmlconfig option at the moment as you can do this within a component and tie it to a feature.

That's not exactly true. Mike has done a lot of work to get IIS7 supported by the existing CustomActions. Unfortunately, the code only supports the "legacy" stuff.As noted above, integrated pipe-line needs custom code.

– Rob Mensching Mar 26 '09 at 23:02 OK - I wasn't aware work was being done to support IIS7 - I saw a comment suggesting Apache support may come sooner :p I was under the impression that some stuff worked if you switched on IIS6 metabase compatability and that was it. Good to hear. – matthewthurlow Mar 27 '09 at 0:06 To be clear, you still need IIS6 metabase compatability but, at least, it should work.

And that was my off hand comment when I was pissed at IIS. – Rob Mensching Mar 27 '09 at 2:15 Is this still the case with IIS7.5? – Terrance Jan 26 at 23:11.

I personally recommend using AppCmd. Exe (matthewthurlow's first bullet) because you don't have to count on the legacy management components being installed, or risk modifying the configuration XML manually. If you are not comfortable with AppCmd, Mike Volodarsky has a great article on Getting Started with AppCmd.

Exe, and the Microsoft IIS Configuration Reference is excellent, offering UI, Code and AppCmd examples for modifying each of the configuration items (e.g. Application Pools ). The IIS7 Administration Pack also includes a Configuration Editor that allows you to generate AppCmd scripts from any existing configuration.To integrate AppCmd into WiX, you need to create and schedule two custom actions for each command. There is general information in the WiX v3 manual documenting this procedure, and I've included a concrete example below.

First, you need to set up an immediate action to store the command line in a property: Next you set up a deferred action which references this property: And finally, you need to schedule these. The immediate action that sets the properties seem to work well after InstallFinalize, and the deferred action works after InstallFiles. I haven't got as far as figuring out rollback actions yet.

MapGuide Open Source does this method extensively; you can see the CA scheduling in our MapGuide. Wxs file, and the CA definition in our IIS7. Wxs file.

Thanks for the good information Jason! – Si. Nov 30 '09 at 1:42 This was very useful to me yesterday, and thanks for the links to the examples too!

– Simon Steele Dec 4 '09 at 10:40.

Thanks to @matthewthurlow, I was able to use the XML utils to achieve what I needed to do: The rest of the actions do seem to work fine with IIS 7.

Well, unfortunately the IIS extentions is not supported by IIS7 yet.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.