We're not trying to do anything that has not been done before, it's a basic install:
1) create a website or vdir and set some properties based on options collected in the MSI wizard 2) drop or update some .config files based on user options (I've read it is better to create them so they are not blasted in an update) 3) effectively xcopy the website into this vdir * 4) create a few databases There's more, but that is the basic idea. It's including the build of the MSI into VS where things seem to get cloudy for me. * the entire website is managed code. It's also 2.0 and precompiled.. I have read and understand the concern about MSI and component rules, but in this day and age it seems to be a little excessive. We no longer register components, we're using local assemblies... with precompilation the content files are not even required.. really the majority of the files we're talking about (outside the binaries) are images, .css and .js files. It would be SO nice to have an integrated build for this where outputs from the web deployment project could be piped into Votive project with options to refresh GUIDS and versions... bah, pipe dream I realize. Even if I could just specify a folder that contains the tree to be packaged I would be happy (if it was within VS ;) ) Currently our update/patch process is download a .zip file and drop files on top (website), and run a .sql script on application databases. An MSI to run this through with the help of custom actions would be great - and my research brought me here. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams Sent: Thursday, October 19, 2006 5:11 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] rookie here: suggestions for Votive / Web DeploymentProject / wildcard inclusion ? Mark: With your Web Deployments, what things are you trying to do? David Adams MSN MessengerID: [EMAIL PROTECTED] >From: "Mark Bailey" <[EMAIL PROTECTED]> >To: <wix-users@lists.sourceforge.net> >Subject: [WiX-users] rookie here: suggestions for Votive / Web >DeploymentProject / wildcard inclusion ? >Date: Thu, 19 Oct 2006 15:01:10 -0400 >MIME-Version: 1.0 >Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by >bay0-mc9-f1.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Thu, 19 >Oct 2006 13:41:40 -0700 >Received: from sc8-sf-list1-new.sourceforge.net (unknown [10.3.1.93])by >sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 52AA3E48D; Thu, 19 Oct >2006 13:41:40 -0700 (PDT) >Received: from sc8-sf-mx2-b.sourceforge.net >([10.3.1.92]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net >with esmtp (Exim 4.43)id 1Gaehu-0000io-07for >wix-users@lists.sourceforge.net; Thu, 19 Oct 2006 13:41:38 -0700 >Received: from smtp3-server95.ilap.com ([216.223.130.191])by >mail.sourceforge.net with esmtp (Exim 4.44) id 1Gaehr-000441-FZfor >wix-users@lists.sourceforge.net; Thu, 19 Oct 2006 13:41:37 -0700 >Received: from DEV05 (TOROON12-1168099190.sdsl.bell.ca >[69.159.199.118])(authenticated bits=0)by smtp3-server95.ilap.com >(8.13.1/8.13.1/S3 - Internet Light and Power(tm) * http://ilap.com/ (tm)) >with ESMTP id k9JJ1vdX011708for <wix-users@lists.sourceforge.net>;Thu, 19 >Oct 2006 15:02:00 -0400 (EDT) >X-Message-Info: LsUYwwHHNt2IIC7bhvJ+cS6iY3N8MbqPx8/12zVNq30= >X-Mailer: Microsoft Office Outlook, Build 11.0.6353 >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 >thread-index: AcbzsPC5dwJ7mWK7Q5KjyWwEDqhisA== >X-Spam-Score: 0.2 (/) >X-Spam-Report: Spam Filtering performed by sourceforge.net.See >http://spamassassin.org/tag/ for more details.Report problems >tohttp://sf.net/tracker/?func=add&group_id=1&atid=2000010.2 HTML_60_70 > BODY: Message is 60% to 70% HTML0.0 HTML_MESSAGE BODY: >HTML included in message >X-BeenThere: wix-users@lists.sourceforge.net >X-Mailman-Version: 2.1.8 >Precedence: list >List-Id: "General discussion for Windows Installer XML >toolset."<wix-users.lists.sourceforge.net> >List-Unsubscribe: ><https://lists.sourceforge.net/lists/listinfo/wix-users>,<mailto:wix-users- [EMAIL PROTECTED]> >List-Archive: ><http://sourceforge.net/mailarchive/forum.php?forum=wix-users> >List-Post: <mailto:wix-users@lists.sourceforge.net> >List-Help: <mailto:[EMAIL PROTECTED]> >List-Subscribe: ><https://lists.sourceforge.net/lists/listinfo/wix-users>,<mailto:wix-users- [EMAIL PROTECTED]> >Errors-To: [EMAIL PROTECTED] >Return-Path: [EMAIL PROTECTED] >X-OriginalArrivalTime: 19 Oct 2006 20:41:40.0604 (UTC) >FILETIME=[FAF083C0:01C6F3BE] > >Hello all, I have come across WIX just recently and I am quickly growing >attached to this solution. > > > >That said, I am hoping to get some direction on how to proceed with a >commercial web application deployment. > > > >Current process (this are all steps of a team build): > >Libraries build > >Web site compiles > >Web Deployment project merges web assemblies > >Team Build takes output piped from web deployment and does some cleanup > > > >Deployment is really done through xcopy and database scripts (although the >manual steps are removed by a home made installation). > > > >Now I want to move to MSI but vdproj does not offer enough flexibility. > > > >I was thinking that I could pipe the project outputs of either the team >build or web deployment project into a wixproj but I see that is not the >way >things are done. No problem, I decided to create the wxs file manually. >then of course I recognize how long that will take given the hundreds of >files involved. So I search for a way to add files using a wildcard, and >recursively and run into some threads debating the use of <FileGroup> and >it >seems the winner was deprecating this element. > > > > >From what I read there are tools that can help enumerate the files. but >my >question is, how is this integrated if at all with Visual Studio / Votive? > > > >It seems like I might be better off giving up the idea that the deployment >packaging can be part of my solution, and just have it exist as a >standalone >project to run after a release build. i.e. when team build is done - take >its output, and use some trick to enumerate the directories and files to >include in a wxs. After each release build the manual task would be to >compare the file set with a previous release, update GUIDs and edit the >.wxs >file. am I on the right track? > > > >Does anyone have a good example of a .wxs that serves the installation of a >web application that they could share? > > > >Thanks. > > > > > > > >------------------------------------------------------------------------- >Using Tomcat but need to do more? Need to support web services, security? >Get stuff done quickly with pre-integrated technology to make your job >easier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >_______________________________________________ >WiX-users mailing list >WiX-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wix-users _________________________________________________________________ Try Search Survival Kits: Fix up your home and better handle your cash with Live Search! http://imagine-windowslive.com/search/kits/default.aspx?kit=improve&locale=e n-US&source=hmtagline ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
