At the end of our installation, an deferred custom action is invoked to
register our VSTS package as well as the CTC menu:
<InstallExecuteSequence>
<Custom Action="CA_DevenvSetup2005" Before="InstallFinalize" />
...
</InstallExecuteSequence>
<CustomAction Id="CA_DevenvSetup2005" Property="DEVENV_EXE_2005"
ExeCommand="/setup" Execute="deferred" Return="check" Impersonate="no" />
The installation succeeds and our package is registered to Visual Studio
(custom action return value is 1).
The problem is that the context menu doesn’t shown in the VSTS project
supported by our package just intalled. Manually running “devenv /setup” solves
the problem.
Something strange is that “devenv /setup” actually does everything other than
the context menu registration --- all the other functionalities provided by our
package works well in VS.
Does anyone have this problem before?
Thanks,
Xin Liu
Alias: v-liux
Group: Protocol Tools &Test Team
Occupation: Build Engineer
Seat: No. 2186 Sigma Plaza, Beijing
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Painter
Sent: Friday, September 07, 2007 11:53 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using WiX v3 Votive to build WiX v2 projects
This is why I've been asking Justin about using votive v3 to build wix v2
projects. It's a hybrid solution but it seems to work. The risk is minimal
since the points that could fail are at build time, not install time.
PS- IS is pretty easy to build with TFS once you learn how it works. I have
dozens of installers that I use TFS to build with nothing but .NET 2.0,
TeamBuild and IS StandAloneBuild installed. You just have to understand how
to map product configurations / releases to your solution config. If you
would like, I can send you a sample project.
http://blog.deploymentengineering.com/2007/05/tip-parallel-is122008-builds-using-tfs.html
[EMAIL PROTECTED] wrote:
Had a look at the files and I've finally got my head round this.
As i understand it WiX v2 .wixproj files, which are used for VS
integration, aren't MSBuild files. You have to create your own .wproj files
for that. Which means that WiX v2 isn't compatible withTeam Build (as it
tries to build the .wixproj file).
It'd be really cool if v2 did support Team Build and it's solution centric
build process. Without it we can't really consider using WiX v2 or v3 (as
it's not stable yet).
Which leads me to my next question, is there a rough time line for the
switch to v3?
Oh and in case it makes you feel better Justin I've been messing around
with IS for two days and 2 hotfixes later i still can't get it to build
with MS or Team! :-)
Matt
Matt Thompson
PERSHING
Tel: 020 7864 8000
Email: [EMAIL PROTECTED]
"Justin Rockwood"
ford.edu> To
Sent by: ,
wix-users-bounces
@lists.sourceforg cc
e.net
Subject
Re: [WiX-users] Using WiX v3 Votive
07/09/2007 02:22 to build WiX v2 projects
To get back to your original question where you're setting $(WixToolPath)
to point to the 2.0 versions… That should work fine unless you try to pass
in arguments that only the 3.0 versions support. I don't remember off the
top of my head what those new properties are, but you'd probably learn
pretty quickly when you get build errors. The WiX project property pages
within Visual Studio are targeted for the 3.0 versions and not all of the
various checkboxes and other settings will work when using the 2.0
candle/light/lit.
There are no plans to touch Votive v2 in any way and all active development
is being done against Votive v3. You could log a feature request, if you
wanted, to add the ability in Votive v3 to target a v2 candle/light/lit. To
be honest it probably won't happen (at least for a long time) simply
because I'm working on other higher priority features, but it's a nice
idea.
And why'd you have to throw in that last jab about "InstallShield has been
doing it for years"? J
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Painter
Sent: Thursday, September 06, 2007 6:11 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using WiX v3 Votive to build WiX v2 projects
The finer points of MSBuild/Team build are getting lost in these replies so
it's kind of pointless to continue. VDPROJ and WiX v2 are proper
comparisons because both have .xxproj files that are NOT MSBuild files.
Whether or not they `support` MSBuild is a non issue. For example to
build both you could use an Exec to go out of process and call devenv
solution /build project but thats really ugly as it adds another dependency
to the build box.
For Matt, I'd suggest that you just start wiring it up and what I've posted
previously will quickly become obvious. WiX v3 with it's native MSBuild
project format is just so much more cleaner and powerful from a TFS
perspective. It also happens to be the way InstallShield has been doing it
for years...
Bob Arnson wrote:
[EMAIL PROTECTED] wrote:
> I'm interested to know why V2 won't work for you as it does provide
support
> for MSBuild?
>
> My understanding of Votive is that it enables WiX projects to be viewed
in
> VS, still in there text\xml format. If the project is there but Votive
> isn't VS marks it as "unavailable". If that's the case MSBuild will
still
> build it... or no?
>
Yes, it will. Votive v2's project files aren't based on MSBuild; Votive
v3's are. But both WiX v2 and v3 include MSBuild tasks and targets and
therefore both can be built from TFS Build.
The same isn't true of .vdproj files, which are still not based on
MSBuild.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's
on, when.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
************************************************************************
************************************************************************
Pershing Email Disclaimer:
Pershing Securities Limited, registered in England number 2474912, is
authorised and regulated by the Financial Services Authority and is a member of
the London Stock Exchange. Registered address: Capstan House, One Clove
Crescent, East India Dock, London E14 2BH.
Pershing Limited, registered in England number 2072264, is authorised and
regulated by the Financial Services Authority and is a member of the London
Stock Exchange. Registered address: Capstan House, One Clove Crescent, East
India Dock, London E14 2BH.
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mis-transmission. If you receive this message in
error, please immediately delete it and all copies of it from your system,
destroy any hard copies of it and
notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the intended
recipient. Both Pershing Limited and Pershing Securities Limited reserve the
right to monitor all e-mail communications through its networks. Any views
expressed in this message are those of the individual sender, except where the
message states otherwise and the sender is authorised to state them to be the
views of any such entity.
Unless otherwise stated, any pricing information given in this message is
indicative only, is subject to change and does not constitute an offer to deal
at any price quoted.
Any reference to the terms of executed transactions should be treated as
preliminary only and subject to our formal written confirmation.
E-mail will be archived for at least three years and may be produced to
regulatory agencies or others with a legal right to access such information
************************************************************************
************************************************************************
________________________________
Looking for a deal? Find great prices on flights and
hotels<http://us.rd.yahoo.com/evt=47094/*http:/farechase.yahoo.com/;_ylc=X3oDMTFicDJoNDllBF9TAzk3NDA3NTg5BHBvcwMxMwRzZWMDZ3JvdXBzBHNsawNlbWFpbC1uY20->
with Yahoo! FareChase.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
