Hi,

Below I have written the code but  I am getting the error  if anyone knows 
please let me know


" Error 4       The Component element contains an unhandled extension element 
'WebSite'.  Please ensure that the extension for elements in the 
'http://schemas.microsoft.com/wix/IIsExtension' namespace has been provided."


<?xml version="1.0" encoding="UTF-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";
       xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>

<Product Id="86c28e5e-8570-4776-9775-d9055bae38b3" Name="appServer" 
Language="1033" Version="1.0.0.0" Manufacturer="appServer" 
UpgradeCode="92c51df1-d8bb-4c5b-88e5-bde7ab4a9ede">
                <Package InstallerVersion="200" Compressed="yes" />
                <Media Id="1" Cabinet="appServer.cab" EmbedCab="yes" />
        <Directory Id='TARGETDIR' Name='SourceDir'>
                <Directory Id='ProgramFilesFolder' Name='PFiles'>
                        <Directory Id='ApplicationFolder' Name='AppDir' 
src='D:\Build\AppServer\AppServer.Host' >
                                <Component Id='WebSiteComponent' 
Guid='6b27e78e-bcbc-462a-bd7a-50cf991c7d39' DiskId='1'>

                                        <WebSite Id='WixWebSite'  
Description='Wix Web Site' 
xmlns='http://schemas.microsoft.com/wix/IIsExtension'>
                                                <WebAddress Id='AllUnassigned' 
Port='9093'  />
                                        </WebSite>
                                        <WebVirtualDir Id='TestWebVirtualDir' 
Alias='Test' Directory='InstallDir' WebSite='WixWebSite' 
xmlns='http://schemas.microsoft.com/wix/IIsExtension'>
                                                <WebApplication 
Id='TestWebApplication' Name='Test' />
                                        </WebVirtualDir>
                                </Component>
                        </Directory>
                </Directory>
        </Directory>
        <Feature Id='TestProductFeature' Title='Wix File Product Feature' 
Level='1'>
                <ComponentRef Id='WebSiteComponent' />
                <ComponentRef Id='WebVirtualDirComponent' />
        </Feature>

</Product>
</Wix>


Thanks & regrds
kedarnath

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Friday, July 11, 2008 7:44 PM
To: wix-users@lists.sourceforge.net
Subject: WiX-users Digest, Vol 26, Issue 46

Send WiX-users mailing list submissions to
        wix-users@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/wix-users
or, via email, send a message with subject or body 'help' to
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of WiX-users digest..."


Today's Topics:

   1. Votive fails to install on Visual Studio 2008 (Mohith Manoj)
   2. Re: Automating the inclusion of a mess of files (Jason Swager)
   3. Re: Votive fails to install on Visual Studio 2008
      (Martin MacPherson)
   4. Asian transforms busted buy msitran (A. Brooks Hollar)
   5. Re: Automating the inclusion of a mess of files (Neil Enns)
   6. Re: Automating the inclusion of a mess of files (Neil Enns)


----------------------------------------------------------------------

Message: 1
Date: Fri, 11 Jul 2008 18:30:31 +0530
From: "Mohith Manoj" <[EMAIL PROTECTED]>
Subject: [WiX-users] Votive fails to install on Visual Studio 2008
To: <wix-users@lists.sourceforge.net>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain;       charset="us-ascii"

Hi,

I am new to WIX (and Votive of course). I am trying to install WIX3
(Wix-3.0.2925.0.msi from Sourceforge), but every time I do the installer
tells me that "Votive, the WiX project and editor package for Visual Studio,
cannot be installed because Visual Studio Standard Edition or higher is not
installed".



How ever I have installed Visual Studio 2008 Professional (at least that's
what the Help>About says).



Please help





------------------------------

Message: 2
Date: Fri, 11 Jul 2008 06:05:31 -0700 (PDT)
From: Jason Swager <[EMAIL PROTECTED]>
Subject: Re: [WiX-users] Automating the inclusion of a mess of files
To: "General discussion for Windows Installer XML toolset."
        <wix-users@lists.sourceforge.net>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii

You may want to look at Paraffin 
(http://www.wintellect.com/CS/blogs/jrobbins/archive/2007/10/21/wix-a-better-tallow-paraffin.aspx).
  This tool was designed for WiX 2.0, so you have to WiXCop the resulting file 
if you use WiX 3.0.  Paraffin handles much of the GUID generation and updating 
for you.  For maintaining large directories of non-binary files where additions 
and removals are common, this tool works very well for me.  I just wish it 
generated WiX 3.0 code....

Jason Swager


----- Original Message ----
From: Neil Enns <[EMAIL PROTECTED]>
To: General discussion for Windows Installer XML toolset. 
<wix-users@lists.sourceforge.net>
Sent: Thursday, July 10, 2008 11:01:30 PM
Subject: [WiX-users] Automating the inclusion of a mess of files

My application will wind up shipping with a ton of loose resource files on 
disk*. We will have several items with the following well-defined structure:

MyFile1.foo
MyFile1_files
   \ 0
      \ somefile.txt
   \ 1
      \ somefile.txt
   ...
   \ 9
      \ somefile.txt

This is how the files live on disk as source, and how we need them to live on 
disk on the target machine. As you can imagine, I have no desire to author the 
WiX to install these suckers by hand, especially since they're going to change 
relatively often between now and when we ship. I want to automate the process 
somehow.

I started tonight by thinking a custom extension would do. My plan was to 
create a new <MyFile> element that took the root .foo file, then would 
automatically add all the necessary entries into the MSI for all the files and 
subdirectories. I got a custom extension up and running pretty quickly, but 
when it came time to actually think about adding the things to the MSI this 
approach seemed, well, insane. I have no desire to recreate what the <File>, 
<Directory>, and <Component> elements do in code.

My new alternate approach is to do this via a custom MSBuild task that runs 
before Candle and generates a WiX file that then gets added to the list of 
things to compile.

Anyone have any other suggestions for good ways to automate this?

Thanks,

Neil

* Don't ask why we have this structure and why they are loose files. It's a 
very long story best told over a frosty beverage.
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------

Message: 3
Date: Fri, 11 Jul 2008 14:18:37 +0100
From: "Martin MacPherson" <[EMAIL PROTECTED]>
Subject: Re: [WiX-users] Votive fails to install on Visual Studio 2008
To: "General discussion for Windows Installer XML toolset."
        <wix-users@lists.sourceforge.net>
Message-ID:
        <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1

Hi Mohith,

You can grab the latest build of Wix v3 from the following location (2925 is
a little old):

http://wix.sourceforge.net/releases/

The sourceforge list of releases is not currently update - though this
should be changing soon!!

2008/7/11 Mohith Manoj <[EMAIL PROTECTED]>:

> Hi,
>
> I am new to WIX (and Votive of course). I am trying to install WIX3
> (Wix-3.0.2925.0.msi from Sourceforge), but every time I do the installer
> tells me that "Votive, the WiX project and editor package for Visual
> Studio,
> cannot be installed because Visual Studio Standard Edition or higher is not
> installed".
>
>
>
> How ever I have installed Visual Studio 2008 Professional (at least that's
> what the Help>About says).
>
>
>
> Please help
>
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>


------------------------------

Message: 4
Date: Fri, 11 Jul 2008 09:31:04 -0400
From: "A. Brooks Hollar" <[EMAIL PROTECTED]>
Subject: [WiX-users] Asian transforms busted buy msitran
To: <wix-users@lists.sourceforge.net>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain;       charset="ISO-8859-1"

Howdy.

After using candle and light to create my english msi, I am creating
transforms for 8 foreign languages with msitan.exe.

This works fine for non-asian languages. Asian languages have mst's with all
characters being question marks...

Poking around, I've found many threads about msi 3 not being UTF-8
complient, but there must be some kind of work around....

Thanks for any help!
-ab

--

A. Brooks Hollar
Rosetta Stone?




------------------------------

Message: 5
Date: Fri, 11 Jul 2008 07:05:55 -0700
From: Neil Enns <[EMAIL PROTECTED]>
Subject: Re: [WiX-users] Automating the inclusion of a mess of files
To: General discussion for Windows Installer XML toolset.
        <wix-users@lists.sourceforge.net>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"

Thanks for all the suggestions everyone, lots for me to go and look at.

Neil

________________________________
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Jason Swager [EMAIL 
PROTECTED]
Sent: Friday, July 11, 2008 6:05 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Automating the inclusion of a mess of files

You may want to look at Paraffin 
(http://www.wintellect.com/CS/blogs/jrobbins/archive/2007/10/21/wix-a-better-tallow-paraffin.aspx).
  This tool was designed for WiX 2.0, so you have to WiXCop the resulting file 
if you use WiX 3.0.  Paraffin handles much of the GUID generation and updating 
for you.  For maintaining large directories of non-binary files where additions 
and removals are common, this tool works very well for me.  I just wish it 
generated WiX 3.0 code....

Jason Swager


----- Original Message ----
From: Neil Enns <[EMAIL PROTECTED]>
To: General discussion for Windows Installer XML toolset. 
<wix-users@lists.sourceforge.net>
Sent: Thursday, July 10, 2008 11:01:30 PM
Subject: [WiX-users] Automating the inclusion of a mess of files

My application will wind up shipping with a ton of loose resource files on 
disk*. We will have several items with the following well-defined structure:

MyFile1.foo
MyFile1_files
   \ 0
      \ somefile.txt
   \ 1
      \ somefile.txt
   ...
   \ 9
      \ somefile.txt

This is how the files live on disk as source, and how we need them to live on 
disk on the target machine. As you can imagine, I have no desire to author the 
WiX to install these suckers by hand, especially since they're going to change 
relatively often between now and when we ship. I want to automate the process 
somehow.

I started tonight by thinking a custom extension would do. My plan was to 
create a new <MyFile> element that took the root .foo file, then would 
automatically add all the necessary entries into the MSI for all the files and 
subdirectories. I got a custom extension up and running pretty quickly, but 
when it came time to actually think about adding the things to the MSI this 
approach seemed, well, insane. I have no desire to recreate what the <File>, 
<Directory>, and <Component> elements do in code.

My new alternate approach is to do this via a custom MSBuild task that runs 
before Candle and generates a WiX file that then gets added to the list of 
things to compile.

Anyone have any other suggestions for good ways to automate this?

Thanks,

Neil

* Don't ask why we have this structure and why they are loose files. It's a 
very long story best told over a frosty beverage.
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------

Message: 6
Date: Fri, 11 Jul 2008 07:12:52 -0700
From: Neil Enns <[EMAIL PROTECTED]>
Subject: Re: [WiX-users] Automating the inclusion of a mess of files
To: General discussion for Windows Installer XML toolset.
        <wix-users@lists.sourceforge.net>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"

Rob,

Any pointers on tips for getting the GUIDs right? Will HeatTask take care of 
this for me? If not, what rules do I need to follow?
Neil

________________________________
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Rob Mensching [EMAIL 
PROTECTED]
Sent: Friday, July 11, 2008 1:48 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Automating the inclusion of a mess of files

There is a "HeatTask" provided by the WiX toolset already.  Getting the GUIDs 
right is the hardest part of "autogenerating" .wxs files.  The Windows 
Installer is brutally unforgiving for messing up your Component/@Guids.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm
Sent: Friday, July 11, 2008 00:30
To: General discussion for Windows Installer XML toolset.; General discussion 
for Windows Installer XML toolset.
Subject: Re: [WiX-users] Automating the inclusion of a mess of files

Neil

Have you considered using a variant of Heat to generate the WiX code 
dynamically? I have done this sort of think in v2 using a tool called mallow 
(it is a variant of tallow) I think you should find it on the web if you search 
but if not let me know and I send you a copy. It can scan a folder full of 
files and generate WiX code and manage the GUIDs for you so it shouldn't break 
the component rules.

I know this sort of thing it considered bad but in the real world we have to 
consider things like this!

Neil

Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>


________________________________

From: [EMAIL PROTECTED] on behalf of Neil Enns
Sent: Fri 11/07/2008 07:01
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Automating the inclusion of a mess of files



My application will wind up shipping with a ton of loose resource files on 
disk*. We will have several items with the following well-defined structure:

MyFile1.foo
MyFile1_files
   \ 0
      \ somefile.txt
   \ 1
      \ somefile.txt
   ...
   \ 9
      \ somefile.txt

This is how the files live on disk as source, and how we need them to live on 
disk on the target machine. As you can imagine, I have no desire to author the 
WiX to install these suckers by hand, especially since they're going to change 
relatively often between now and when we ship. I want to automate the process 
somehow.

I started tonight by thinking a custom extension would do. My plan was to 
create a new <MyFile> element that took the root .foo file, then would 
automatically add all the necessary entries into the MSI for all the files and 
subdirectories. I got a custom extension up and running pretty quickly, but 
when it came time to actually think about adding the things to the MSI this 
approach seemed, well, insane. I have no desire to recreate what the <File>, 
<Directory>, and <Component> elements do in code.

My new alternate approach is to do this via a custom MSBuild task that runs 
before Candle and generates a WiX file that then gets added to the list of 
things to compile.

Anyone have any other suggestions for good ways to automate this?

Thanks,

Neil

* Don't ask why we have this structure and why they are loose files. It's a 
very long story best told over a frosty beverage.
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08

------------------------------

_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


End of WiX-users Digest, Vol 26, Issue 46
*****************************************


DISCLAIMER:
This email (including any attachments) is intended for the sole use of the 
intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE 
COMPANY INFORMATION. Any review or reliance by others or copying or 
distribution or forwarding of any or all of the contents in this message is 
STRICTLY PROHIBITED. If you are not the intended recipient, please contact the 
sender by email and delete all copies; your cooperation in this regard is 
appreciated.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to