1.  For these types of problems it just takes digging into the specific error 
message.  I've been extremely disappointed with the complexity of creating 
Visual Studio Packages (like our Votive), especially stuff that tries to work 
on VS2005 and VS2008.  We have tons of software on the build machine since it 
is also configured to build WiX v2 and that had support for VS2003.  The only 
upside is that you know two places are correctly building so there must be 
something in the configuration somewhere (some other software installed) 
gumming up the works.  I'd love to spend more time investigating but I 
personally just don't have cycles to spend sorting out the difference between 
the official WiX build machine and yours...

2.  WiX v2 is already officially released.  WiX v3 is targeting official 
release before the end of the year (August'ish).  We are targeting that date 
because we are delivering it to VS2010 and that's when they said they wanted 
the last build.  However, we've already started the process of trimming the 
amount of change that goes into WiX v3.  MSI5.0 support was (I think) the last 
big issue to tackle.  We already have a 100 fewer bugs open against v3 than we 
shipped in v2.  WiX v3 is really quite stable (delta the new MSI5.0 stuff) and 
I expect that in a couple months we will just be sitting around looking for 
that "big bad bug that just can't ship" (which hopefully doesn't exist and 
we'll be rock solid for 6 months).

-----Original Message-----
From: Oliver Wickham [mailto:oliver.wick...@skinkers.com]
Sent: Monday, January 19, 2009 10:51
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Votive Fails to compile

Thanks for coming back to me so quickly. Can you point me the direction
of somebody who is able to illuminate some of the darker places in WIX?
Also, can you describe your build environment? Maybe that would help me
understand what I have different to you.

BTW, I love the idea of WIX. Can you please give me an approximate
timeline for an official release, and is it true that it is going to be
integrated in VS2010? That would meet our requirements perfectly!

Olly

-----Original Message-----
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: 19 January 2009 18:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Votive Fails to compile

The latest WiX toolset was just built on Saturday.  Your deep in Votive
and MSBuild territory.  Neither place I'm strong.  It is also some of
the more dark and twisty places.

-----Original Message-----
From: Oliver Wickham [mailto:oliver.wick...@skinkers.com]
Sent: Monday, January 19, 2009 10:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Votive Fails to compile

Hi All,



I wonder if anybody has the solution to an issue I have whilst compiling
WIX? I have followed Neil Sleightholm's blog entry on creating a Wix
build machine, which is a pretty good article. Therefore I *should* have
all the prerequisites in place to build WIX, however, my build is still
failing whilst compiling Votive. The log reveals:



     [exec] Target VsTemplatePathsTarget:

     [exec]
C:\code\sharedlibs\upstream\Wix\cvs\wix\src\votive\SDK_VS2008\Tools\Buil
d\Microsoft.VsSDK.targets(348,5): error MSB4062: The "VsTemplatePaths"
task could not be loaded from the assembly
C:\code\sharedlibs\upstream\Wix\cvs\wix\src\votive\SDK_VS2008\Tools\Buil
d\Microsoft.VsSDK.Build.Tasks.dll. Could not load file or assembly
'Microsoft.VsSDK.Build.Tasks, Version=8.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Access is
denied. Confirm that the <UsingTask> declaration is correct, and that
the assembly and all its dependencies are available.

     [exec] Done building target "VsTemplatePathsTarget" in project
"Votive2005.csproj" -- FAILED.

     [exec]

     [exec] Done building project "Votive2005.csproj" -- FAILED.

     [exec]

     [exec] Build FAILED.

     [exec]
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets :
warning MSB3247: Found conflicts between different versions of the same
dependent assembly.

     [exec]
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets :
warning MSB3088: Could not read state file
"C:\code\sharedlibs\upstream\Wix\cvs\wix\build\obj\debug\x86\Wix\Wix.csp
roj.GenerateResource.Cache". Unable to cast object of type
'Microsoft.Build.Tasks.ResGenDependencies' to type
'Microsoft.Build.Tasks.StateFileBase'.

     [exec]
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets :
warning MSB3247: Found conflicts between different versions of the same
dependent assembly.

     [exec]
C:\code\sharedlibs\upstream\Wix\cvs\wix\src\votive\SDK_VS2008\Tools\Buil
d\Microsoft.VsSDK.targets(348,5): error MSB4062: The "VsTemplatePaths"
task could not be loaded from the assembly
C:\code\sharedlibs\upstream\Wix\cvs\wix\src\votive\SDK_VS2008\Tools\Buil
d\Microsoft.VsSDK.Build.Tasks.dll. Could not load file or assembly
'Microsoft.VsSDK.Build.Tasks, Version=8.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Access is
denied. Confirm that the <UsingTask> declaration is correct, and that
the assembly and all its dependencies are available.

     [exec]     3 Warning(s)

     [exec]     1 Error(s)



Does anybody have a clue as to what could be causing this error? I see
that a post was made on the mailing list mid-last year by somebody else,
with a similar error, but there was no response. I am hoping for better
luck this time! At least can somebody please confirm that the CVS head
for WIX compiles at the moment?



Kind Regards,



Olly

------------------------------------------------------------------------
------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------
------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to