Hi Rob,
Would you care to elaborate on this part a bit? If you already blogged it,
I apologize. I've followed the evolution of this issue for a while now and
I am always curious to learn more about it. To my knowledge, I don't
remember you or anyone else discussing any specific issues regard
I guess, I see your point, Rob. But making this functionality available
would open all kinds of doors for folks like me - I get to govern 'what,
how, and when' my clients install currently; our company is a 90% MS shop,
and most of our server deployments have .NET installed just for that reason
al
I have a feature that can only installed if .net 1.1 or higher is also
installed. The description for the feature indicates this requirement
but I don't want to trust to the users' good sense, some of them will
either not read the message or ignore it and get into trouble.
Searching through the ar
Take a look at wix\src\ext\SqlExtension\wixlib\en-us.wxl. You'll see
everything there is overridable.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta
Sent: Friday, March 16, 2007 2:13 PM
To: Don Tasanasanta; Rob Mensching; wix-users@lists.sourceforge.net
Subject: R
I found the problem:
Setting this to "yes" fixed it. Suddenly my MSI was 4meg and it worked.
I did read that _Streams was a temporary table in MSDN, but the instructions
for embedding a CAB (http://msdn2.microsoft.com/en-us/library/aa369279.aspx)
tell you to add it to the _Streams tabl
_Streams is not a real table. The documentation states "This is a temporary
table, created only when referenced by a SQL statement." The CABs are
actually stored as separate streams in the OLE Structured Storage file. You
can see them with the DocFile Viewer (dfview.exe) from Visual Studio 6.0 (it
Doesn't install unless the files are shipped along with the MSI.
Am I using a recent enough version of Candle\Light:
Microsoft (R) Windows Installer Xml Compiler version 2.0.3620.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
Thanks,
- Matt
From: Rob Mensching
Sent: Friday, Mar
Never heard of anyone having a problem with it where there wasn't a build
failure somewhere else. Does it install correctly?
Also, I don't remember if the cabinet shows up in the _Streams table... it may
just be stored as a stream with the name.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED
Well, unless running an elevated advertised installation, of course. I'm
coming to the conclusion that that's what per-user installs are for.
--
Mike Dimmick
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: 15 March 2007 02:57
To: Brett Kapilik
Cc
I'm searching the wixlib's for the sql error strings and only found them
in the sca.wixlib
None of the tuple's defined in the sql section has localization
variables and I haven't found associating fields in the wixui.wixlib
Does that mean that the sql errors have not been localized? In whic
I believe vb6fr.dll is a resource-only DLL containing translations of the
VB6 error message strings into French.
It looks like there is no merge module for this. The download page says that
the merge modules are localized into English, German and Japanese, but not
into French.
That being sa
The popup box is coming from the DLL's DllRegisterServer function. Fix your
self-registration code, or write the script manually.
You should not run heat on every build. It is intended for creating an
initial script. Generating new GUIDs on every build can cause component rule
violations, and g
I believe InstallShield lies in the Version column of the File table if this
option is set (setting it to something huge like 65535.65535.65535.65535,
which is the maximum supported value). I don't think this is a particularly
good idea, however. You can't do it with WiX - the linker takes the
info
Heat cannot handle COM server EXEs. You'll have to write the appropriate
registry entries yourself. See the , , ,
elements. You should strongly consider using non-advertised entries - see
Rob's blog entry at
http://robmensching.com/blog/archive/2007/03/12/RobMens-Recommendation-Do-no
t-advertise-C
Embeddding the cab:
Opening the msi with ORCA:
I see that the cab is listed as embedded in the media table -
DiskId
LastSequence
DiskPrompt
Cabinet
VolumeLabel
Source
i2
i4
L64
S255
S32
S72
Media
DiskId
1
7
#XUSB21.cab
The files that should be embedded in
An advertised shortcut is one which actually invokes Windows Installer when
activated. If the product feature that the shortcut points to is not
installed at that point, Windows Installer will install it, then invoke the
feature. This is how the 'install on demand' and 'advertised product'
features
Has anyone considered using DSL designers as an interface for creating wix
installers? On the surface, it seems like a good fit.
Thanks,
ClintBEGIN:VCARD
VERSION:2.1
N:Chapman;Clint
FN:Clint Chapman
ORG:Luminos Industries
TITLE:Software Developer
TEL;WORK;VOICE:(613) 225-7661
TEL;WORK;FAX:(613)
Ok maybe I don't understand .wxl files that well...
I found the identifier in the error table, created a .wxl file and used
light with a -loc to my wxl file and a reference to my rsp file.
When all was said and done I checked the error table but the error
identifier I tried to replace was
However, with static linking you have the servicing problem - if there's a
security issue in the CRT (not unknown) or in MFC, you will have to rebuild
your application to pick up the fix, then rerelease your application. By
contrast, if using the WinSxS versions, Microsoft can ship an update
direct
More importantly, the Windows Installer doesn't support it today. There are
actually "neat" problems you can introduce by loading the .NET Framework into
the Windows Installer process.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Levi Wilson
Sent: Friday, March 16, 2007 10:40
I don't know for certain, but my guess would be that there's no guarantee
that the .NET Framework has been installed on the client.
On 3/16/07, Dhaval Patel <[EMAIL PROTECTED]> wrote:
Will WIX 3.0 be adding the capability to call C# .dll files? If not,
WHY? :)
-
Will WIX 3.0 be adding the capability to call C# .dll files? If not,
WHY? :)
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT
Are you shipping these Merge Modules to customers? If not, I would highly
recommend moving to .wixlibs to share the logic across your Products.
If you are shipping to customers and need the dependency between Merge Modules,
check out the Dependency element.
From: [EMAIL PROTECTED] [mailto:[EMA
Does someone have a sample of a merge module referencing another merge
module?
Specifically, we have a merge module that contains a DLL for custom
actions. I did not see anything like this on the WiX tutorial site. Of
course, I may have missed it.
Thanks!
Rory
--
I'm not quite yet ready to make this a "recommendation" but I'm currently
leaning towards statically linking the libraries directly. I'm seeing hints
that the WinSxS/Fusion stuff they did for these libraries in VS2005 has some
seriously bad repercussions when it comes to patching and some possi
Richard,
That was exactly the problem. Thank you for your help.
Shayla
-- Original message --
From: <[EMAIL PROTECTED]>
Shayla,
An example from our own build process is as follows:
Candle -dMajorRev=1 -dMinorRev=2 -dPatchRev=3 –dBuildRev=4
Within the script, we us
There is an easier way. Go look at wix\src\wix\Data\tables.xml. That's the
Windows Installer schema in a format WiX can quickly digest.
From: Thomas Svare [mailto:[EMAIL PROTECTED]
Sent: Friday, March 16, 2007 5:25 AM
To: Rob Mensching; wix-users@lists.sourceforge.net
Subject: RE: Re: [WiX-user
Looking through the archives, there appear to be a couple of ways to
include things like the CRT and MFC redistributables in an installer.
Some have advocated including the DLLs directly, which seems to go
against the concept of having a redistributable MSM to link against. I
tried building with t
Shayla,
An example from our own build process is as follows:
Candle -dMajorRev=1 -dMinorRev=2 -dPatchRev=3
-dBuildRev=4
Within the script, we use (for example)
I'm not sure if you are actually including the ( and ) characters in the
command line. If so, that's where you're goi
[Oops... resending to the list so it is present for future reference.]
Use the command line parameter -d=
For this and other helpful information on available options run the
appropriate tool (e.g. candle, or light) with the "-?" command line
option.
Regards,
Richard
__
How can I pass a variable to the wix project during compile time?
TIA
Shayla-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & bu
Thanks Levi, I'll give that a shot as soon as I get access to my
development box back.
From: Levi Wilson [mailto:[EMAIL PROTECTED]
Sent: Friday, March 16, 2007 8:56 AM
To: Rowland, Chris
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] verify file
Sorry, prematurely sent it. Here is what I was getting at:
extern "C" UINT __stdcall LocateFile(MSIHANDLE hInstall)
{
char* pDirPath = NULL;
DWORD dw = 0;
if( ERROR_MORE_DATA!=MsiGetProperty(hInstall,"MYFOLDER",NULL,&dw) )
return ERROR_INSTALL_FAILURE;
dw += strlen("requiredfile.txt") +
Yeah, that's what I was trying to say. I believe this happens in the
AppSearch sequence. You probably will need to use a CA for this to happen.
I can try to help you with this as well, but it might look something like
the following:
extern "C" UINT __stdcall LocateFile(MSIHANDLE hInstall)
{
ch
If I look at the log after a completed installation, I can see the
following property values.
Property(S): MYFOLDER = C:\FTP\#This is the folder I
selected in the dialog
...
Property(S): MYFILEEXISTS = C:\requiredfile.txt #this is
where the file was found (MYFOLDER wa
I've only been working with WiX for a little over a month, so I'll _try_ to
answer your questions to the best of my knowledge:
On 3/15/07, DE <[EMAIL PROTECTED]> wrote:
I'd just like to ask some questions relating to this area, because I
cannot
find much meaningful documentation about it.
All
Hello,
Mostly for informational/research purposes. I know it's documented but
I'd like to get a look at things.
Thanks,
Tom
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 4:48 PM
To: Thomas Svare; wix-users@lists.sourcef
37 matches
Mail list logo
