We recently upgraded from TFS 2010. Not long after, one of my team
members started using a package from NuGet that broke our build.
That made me look into TFS 2013's new build template. It now uses the
RunMSBuild activity for the actual build, and this new RunMSBuild
activity happens to support
Well, I have been playing with the idea of my own little publishing
scheme. Maybe this is the shove I needed. Thx for the input guys.
On Thu, Jun 5, 2014 at 7:22 PM, John H Bergman (XPedient)
john.berg...@xpdnt.com wrote:
Or, you could add an activity (and configuration point) that copies the
to configure the build template to use the output
directories of the solution, if you are interested, I'll dig up my notes and
send them to you, it was pretty straight forward though
-Original Message-
From: Rune Moberg [mailto:jjfl...@gmail.com]
Sent: Thursday, June 5, 2014 1:32 PM
...@xpdnt.com wrote:
There is also a way to configure the build template to use the output
directories of the solution, if you are interested, I'll dig up my notes and
send them to you, it was pretty straight forward though
-Original Message-
From: Rune Moberg [mailto:jjfl
, Rune Moberg jjfl...@gmail.com wrote:
I have a similar issue as David below. I install my product (with
announced shortcut), run my app, pin its icon, and finally I install a
newer version of my product. The result is a ghost shortcut (generic
icon pointing nowhere) and a confused user.
Any
I have a similar issue as David below. I install my product (with
announced shortcut), run my app, pin its icon, and finally I install a
newer version of my product. The result is a ghost shortcut (generic
icon pointing nowhere) and a confused user.
Any pointers/suggestions would be most welcome.
I have a mergemodule from Sybase (SQL Anywhere 12 ADO.Net provider)
where the following line exists in the EventMapping table:
Dialog_ = ProgressDlg
Control_ = ActionData
Event = ActionData
Attribute = Text
For every file copied (I assume as I get this error msg many times
during the setup):
On Fri, May 6, 2011 at 5:51 PM, Christopher Painter
chr...@deploymentengineering.com wrote:
The registry key under Uninstall is going to be the ProductCode not the
UpgradeCode.
Ah.
Do you have a copy of your old MSI so you can look at it in Orca to see if it
has an Upgrade Code Property?
On Sat, May 7, 2011 at 1:46 PM, Christopher Painter
chr...@deploymentengineering.com wrote:
I'm not an IA expert, but what you just described sounds like the PackageCode
not the UpgradeCode or the ProductCode.
You are indeed 100% correct Sir!
There was a project properties or something in the
My old installer used InstallAware and now I need my new installer to
perform a major upgrade of what is left out there.
I believe its upgrade code is {1DDFD196-41B9-4896-AB46-3BD7E23858A0}.
Such a node exists in my registry under
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.
On Tue, Apr 26, 2011 at 6:26 AM, Blair os...@live.com wrote:
Depends on when your custom action is scheduled. Can you describe in more
detail what you are trying to achieve?
My installer installs an empty database.
On upgrade, I need to call a stored procedure on said database. My
plan was to
On Mon, Apr 25, 2011 at 1:56 AM, Bob Arnson b...@joyofsetup.com wrote:
Deferred custom actions can only get a couple of system properties. To
get any other properties (public or not), you need an immediate CA that
writes CustomActionData for the deferred CA.
Funnily enough, this played
Given a feature or a component (or for that matter a file), what is
the best way for my custom action to determine the destination folder?
Do I have to drill down into the Directory table and build the full
path myself, or is there an easier way?
TIA.
--
Rune
I have tried the recipe described here:
http://www.wintellect.com/CS/blogs/jrobbins/archive/2011/02/23/web-application-installer-in-wix.aspx
But somehow it either doesn't work, or I have messed things up.
My IIS 6 setup:
Default Web Site (listening to port 81)
test (listening to port 82)
On Fri, Apr 15, 2011 at 6:15 AM, Bob Arnson b...@joyofsetup.com wrote:
The idea(l) is that the files are extracted then moved, so that only
complete and verified files are in the cache. When TMP and appdata are
on the same volume, it should be a move, afaik. Definitely a bug if the
files are
A potential customer informs us that they require installers to be
able to run without elevation.
I see two problems with this approach:
#1: Every user of a given PC will have to install the app separately
#2: ...so my potential malware will run no matter what, as long as
one of these users are
On Thu, Apr 7, 2011 at 11:22 AM, Peter Shirtcliffe pshirtcli...@sdl.com wrote:
Unless I'm misunderstanding something, I don't see how that can work. A
standard user doesn't have permission to change permissions or write to
ALLUSERSPROFILE. You need elevation to affect any machine-wide
On Thu, Apr 7, 2011 at 12:18 PM, Pally Sandher pally.sand...@iesve.com wrote:
Don't do anything which needs to access per-machine areas of the system
you'll be fine =)
I.e. tag my package as perUser, and if that user happens to be admin
then all users will see the shortcuts that are
I would like to set up a directory structure under CommonAppDataFolder
that looks something like this:
OrderImport
+- ProviderA
+- Drop
+- History
+- Error
+- ProviderB
+- Drop
+- History
+- Error
and so on... Not much more than this, but
On Wed, Apr 6, 2011 at 3:08 PM, Peter Shirtcliffe pshirtcli...@sdl.com wrote:
Add a generated registry value to each component and set that as the keypath.
Thanks Peter, that did the trick.
--
Rune
--
Xperia(TM) PLAY
On Mon, Feb 14, 2011 at 1:34 AM, Christopher Painter
chr...@deploymentengineering.com wrote:
1) Run out of process with no ability to access the MSI handle to query
tables,
get/set properties and write to the log. This means they will never be data
driven and are useless to debug when (
On Mon, Feb 14, 2011 at 1:10 PM, Christopher Painter
chr...@deploymentengineering.com wrote:
For #4, you are right, it is simple. I can do it in one line of XML in WiX
and
let MSI handle the details. For developers I can do it in 1 line of .BAT
using
the SC command. And, no, your
On Mon, Feb 14, 2011 at 3:08 PM, Christopher Painter
chr...@deploymentengineering.com wrote:
Well, Evil Genius, you clearly no more about installs then myself and Rob
Mensching combined so knock yourself.
I am not sure where I said I know more about installers?
I freely admit to being a n00b
On Sun, Feb 13, 2011 at 5:48 PM, Rob Mensching r...@robmensching.com wrote:
The Installer class is an anti-pattern in setup. You shouldn't use it for
anything.
Could you expand on this?
Speaking purely as an end-user, I will make the following observations:
1) Windows services should be able
On Wed, Feb 9, 2011 at 10:32 PM, bharatj bharat.ja...@gmail.com wrote:
My requirement is to get all the existing websites in IIS 7.0 and allow
users to create a subweb under any one of the existing website. Then create
a application pool and virtual directory for that newly created subweb.
I
On Tue, Feb 8, 2011 at 8:26 AM, Thai-Hoa Nguyen taiwa...@hotmail.com wrote:
A way to solve this, I no longer use Wix / ServiceInstall. I used
InstallUtil.exe instead. Then the database connection issue goes away.
I'm wondering if there is another way to register the WCF service hosted by
Some observations:
1) My package has InstallScope=perMachine because if I left it at
the default, my shortcuts showed up in my user's profile (not all
users).
2)
I need to create a shortcut for the user's manual:
Component Id=swemm3man
Guid=4e4f1188-a166-44ab-a7c6-3ed72207fef3
On Mon, Jan 31, 2011 at 3:45 PM, Pally Sandher pally.sand...@iesve.com wrote:
Rune take a look at the -arch parameter for candle as it sounds like
it'll do exactly what you need. Bob A mentions it in on his blog @
http://www.joyofsetup.com/2010/05/14/working-hard-or-hardly-working/
When using
On Mon, Jan 31, 2011 at 11:47 PM, Michael Osmond mosm...@baytech.com.au wrote:
PropertyGroup Condition= '$(Configuration)|$(Platform)' == 'Debug|x64'
InstallerPlatformx64/InstallerPlatform
/PropertyGroup
As soon as I put this in, I was able to change target in the Build
Configuration
Mr Sandher gave me some useful tips for building a platform neutral
setup and I'm trying to follow his advice as best I can.
http://blogs.msdn.com/b/astebner/archive/2007/08/09/4317654.aspx gives
an example of one project that outputs both x86 and x64 MSI files.
But I've tried different build
On Thu, Jan 27, 2011 at 5:09 PM, Rob Mensching r...@robmensching.com wrote:
IIRC, a Commit Custom Action *always* runs at the end of the install.
After all files have been removed..?
--
Rune
--
Special Offer--
While attempting to add an icon to my ARP entry, I accidentally set
this property (mentioned e.g. at
http://stackoverflow.com/questions/751000/how-to-install-program-shortcuts-for-all-users):
Property Id=ALLUSERS Value=1/
Error 1001. An exception occurred while uninstalling. This exception
will
CustomAction Id=UninstMM3Srv Execute=commit ExeCommand=-u
FileKey=MM3ServerExe Return=ignore/
InstallExecuteSequence
Custom Action=UninstMM3Srv After=DeleteServicesREMOVE ~=
ALL/Custom
/InstallExecuteSequence
In the log file I see this:
MSI (s) (84:D0) [15:01:37:844]: Note: 1: 2205
On Mon, Jan 24, 2011 at 11:25 AM, Pally Sandher pally.sand...@iesve.com wrote:
If you're clever about it you can build your 2 platform specific MSI's
embed them into a bootstrapper without doubling the size of your download.
See the -cc -reusecab switches for light.exe.
Given that I am a
I had a cunning plan.
I wanted to install everything - just in case. As a convenience for
the victim (uhm, customer) I wanted to add a feature that would
install a service.
If the user misses that feature, he can simply find the executable and
register the service using -i as a command line
On Tue, Jan 25, 2011 at 6:14 PM, Christopher Painter
chr...@deploymentengineering.com wrote:
I would suggest that if the user doesn't install the feature that contains the
service component that he could go into Add/Remove Programs ( Programs and
Features ) and use the Maintenance UI experience
On Sun, Jan 23, 2011 at 12:02 AM, Blair os...@live.com wrote:
If you wish to install your AnyCPU binaries in 64-bit spaces, you need a
64-bit MSI (yes, use the -arch switch, that is the correct approach).
Realize that an MSI marked 64-bit cannot be installed on a 32-bit system, so
you will
On Sun, Jan 23, 2011 at 5:58 PM, Rob Mensching r...@robmensching.com wrote:
Installing your program to Program Files (x86) isn't about looking good or
being grown up. It just means that you have a 32-bit program. There is
nothing wrong with that. For example, all of the WiX toolset installs to
I have a bunch of features. Some of them do not contain any file
resources, they're just there as a convenience to help the customer
get a few services up and running.
Given:
Feature Id=ProductFeature Title=Mikromarc server
ConfigurableDirectory=MIKROMARC3ROOT Level=1 Absent=disallow
On Fri, Jan 21, 2011 at 4:47 PM, Rob Mensching r...@robmensching.com wrote:
Actually, for Package/@Platform, it is better to use the -arch switch on the
command-line. That will flip your entire package to x64 as needed.
Related question (I hope): Is this the proper approach if your .Net
On Thu, Jan 20, 2011 at 2:01 PM, Rob Mensching r...@robmensching.com wrote:
If you don't want to generate another file (this is what WiX does), then my
new favorite trick is to do:
Product/@Version=!(wix.FileVersion.SomeFileIdInYourMsi)
Had I read your e-mail yesterday, I would have slept
I have googled my eyes out recently, trying to figure out an easy way
of setting my installer's version number to match that of my product.
I found three alternatives. None of them appeals to me, because they
are either kludgy, involves some kind of plug-in or ...well, kludgy:
On Thu, Jan 20, 2011 at 10:21 AM, Dandre dandre...@gmail.com wrote:
assemblyinfo.cs files and update the version numbers. Then using a wix
include file using the variable holding version 1.0.0.0 we update that
file and so all installers referring to that include file will get
I was hoping to
Looking at the output window, I see this:
candle.exe (...)
-dMessagesProject.TargetPath=C:\src\Flamingo\Main\bin\Messages.exe
which (admittedly after reading the help) lead me to believe that the
following might work:
File Id=Messagesexe Source=($var.MessagesProject.TargetPath)/
But light.exe
My bad, $(var works a lot better than ($var...
Kindly disregard previous message. Thx.
--
Rune
--
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them.
Hi all,
I finally took the plunge, downloaded WiX 3.5 (the Dec 30th edition),
installed it, and even read some of the documentation.
What I would like to achieve: Create a setup for one of the projects
in our main solution file and have the .msi built as part of our TFS
build.
One of the topics
46 matches
Mail list logo
