I have different IIS host hosts with simple svc files etc. I want you to be able to create deployment packages from our test server using the IIS export package so that the parameters can be saved and selected in Export so that the export is repeatable and automatic. That is, Export will always use the necessary manifest extensions, such as XmlFile, etc.
Websites exist in the solutions and then are assembled using the web deployment project in each solution, so that configuration substitutions are performed, etc.
We are now on VS 2008 SP1, so we do not have direct access to VS 2010
The first problem with MsBuild (works in TeamCity) is how to create an IIS website (with the goal = package) when there is no project file? This way, maybe I can avoid web deployment projects (I use them for various configurations, but I do not want to do this for deployment in Production, but rather for exporting from our fully tested stage to a package file that will be imported to the production server) .
Secondly, I want to avoid the need to configure Export in IIS 7 every time I run it. I just want to find the right set of extensions to use and create the necessary parameters for me. Is this done from the manifest file? I see how to use the .xml options, but I don’t know if I need to use the manifest.xml file (manually created) and how to link it. The idea is that the tester / deployment user should be able to do Export simply without having to include all the necessary extensions.
Any help or guidance would be greatly appreciated.
source
share