Thanks Bob,
I tried to make the tags advertised by the following code. But I am
receiving an error saying:
The Class/@Server attribute cannot be specified when attribute Advertised is
present with value 'yes'
*<**TypeLib** **Id**=**"ABE539FW-EE0A-4F6D-B336-5E6A16123456
Hi!
We have a quite big project and wix uses huge amount of memory. (more than
500 MBs)
Is there any possibility to maximize the memory usage?
How does the package generation works?
Thanks a lot
Tamas
--
View this message in context:
http://www.nabble.com/memory-usage-tf2774539.html#a7739632
S
We could get rid of the CRT dependencies and I used to do that work (had to
port over sprint to do it too, that was a pain). However, the new CRT has a
lot of really nice security checks built-in that I don't want to try to port
over. So, we static link the CRT now to get those security featur
Just for the record, WiX bootstrapper at least 6 months away from being truly
useful.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Thielen
Sent: Wednesday, December 06, 2006 19:34
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] bootstrapper - final questions (
Wow, "deliberate omission" that's pretty strong. Yeah, Justin left that
feature out while he was working his tail off to get all the other (basic)
features working. He told me Tuesday night that he has this feature working
again and is just testing it for regressions. Depending on his holiday
Uhh, maybe but you'd need to be a lot more specific about what in your project
is "quite big".
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tamas Tiboldi
Sent: Thursday, December 07, 2006 05:58
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] m
The result msi is 250MB.
About 2500 files are being installed and more then 20 000 registry keys.
We split the wix files into many parts.
We have one wxs containing the projects and main folders, and many xmls.
These xmls are included into the main wxs.
Regards,
Tamas
Rob Mensching wrote:
> Uhh,
Are you compressing your files? If so, what compression level are you using?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of TibTam
Sent: Thursday, December 07, 2006 09:36
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] memory usage
The resu
If you installed wix using the wixv3 msi, then all of the extension dlls should
be in the same location as candle and light. If you used the zip file, just
make sure that you unzipped the extension dlls.
If it's not finding it using the -ext WixUtilExtension, you can also use -ext
[FullPathToF
Please, keep the mailing list on all replies.
I assume all your seeing the memory hit in the linker (light.exe), right? I
haven't checked the memory usage in a while but your project is very large so
that might be a very reasonable number right now. I don't think Office, VS, or
SQL complain a
Hi;
Ok, this may be more than planned but I figure it doesn't hurt to ask.
We would like the ability in the bootstrapper to have it call our code,
written in C#/.NET 2.0, that looks like part of the install process. So
it has to load this code after checking and installing the .NET
framewor
There are a couple of ways to get this information.
You could check out the wix .chm file. That has documentation on all of the
elements and attributes for all of the 'standard' extensions.
If you don't like documentation, you could check out the source, it's all on
sourceforge. The extension
off topic: Sorry, i pressed Reply instaed of Reply All...
on:
You are right, light uses lot of memory. About 300-350 MB normally, but
some said that on his machine it uses more than 500 MB. This sounds a
bit strange to me, because he uses the same files and method to create
the msi. Is this po
Do you have just one gigantic XML file or are you splitting your product into
many smaller .wxs files and letting the linker bring them back together?
There is nothing special in the compiler. Normally it completes in seconds
because there is very little IO. However, if you make one gigantic X
We have one wxs and many xmls with . These xmls contain the
folders/files/registries. We have the UI in a different xml too.
If we can manage the xml files to be smaller, that can speed up the candle?
Rob Mensching wrote:
Do you have just one gigantic XML file or are you splitting your
produc
Eeek! Don't do that! Organize your product into many different Fragments and
let the linker do the work of hooking the parts back together. Include files
are really only intended to make it easy to share things like and
such. IMHO, software projects should have 0 - 1 Include files (i.e.
*e
If you make your project use multiple .wxs files, rather than a single .wxs
with a bunch of .wxi (which all get added in to the main file), then candle
should seem faster, and the processing would show as spikes, rather than
constant usage.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On B
Hi,
I am tring to develop an installation application using WIX and WixEdit
that will show a dialog after the files were installed so that I can run
some scripts using PERL that were installed during the application. I am
encountering the following problems that I was wondering if you might now
1. Windows Installer doesn't work that way. You ask your questions up front,
the data gets preserved in the transaction where you operate on it. The
Windows Installer isn't a scripting engine, it's a transaction engine. Have to
think about the problem a little differently.
2. Take a look a
Please keep all threads on the mailing list.
You'll want to understand the Directory table in detail. Check out this series
of blog entries:
http://blogs.msdn.com/robmen/archive/2006/10/17/deciphering-the-msi-directory-table-part-7-directories-are-properties.aspx
From: [EMAIL PROTECTED] [mai
Ok, but please help me in on doing that
We decided to use includes because we have huge directory tree and some
parts of the tree are in the main wxs file, and some are in the included
xmls. We need to refer to the folders from the xmls to the wxs (for
example at shortcut creation). And it
My install has a very large directory structure in which the root folder
is defined by the user. If the user doesn't change the default root
directory then everything works fine but if the default is changed then
the install creates a root folder in the new location but only the files
directly unde
Don,
I had this problem with a 32 bit component in a 64 bit merge module.
The 32 bit component needed to go in
Program Files (x86)\MyCompany\MyProduct
I've never fully understood why I had this problem but the issue was
happening because I was using all uppercase Directory Id's. Once
Rob,
I looked at the link you referred. From that info, I still don't see how
to get the directory.
Is there any chance you could show me an example or make the one below so
that it refers to the directory correctly?
If you could show me the syntax or way to make the MY_APP_TARGET
accessible,
Thanks for the responses guys. I've changed it to statically link and it
seems to be working fine now. After doing some digging into the issues
surrounding this, it sure does seem like MS dropped the ball with Win32
SxS. *sigh*
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Thursday, Dece
I would encourage you to walk through the WiX tutorial:
http://wix.sourceforge.net/tutorial. There is a lot in your snippet below that
doesn't make a lot of sense so I'm guessing you're new to setup (I apologize,
if I've guessed wrong).
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: T
ProgramFilesFolder is a special folder where PROGRAMFILESFOLDER is your own
custom thing.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Svare
Sent: Thursday, December 07, 2006 13:17
To: Don Tasanasanta; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Directory rea
Rob,
I have been through the tutorial. I did not see anyplace that shows how
to connect an installation directory ID to a path used for a Binary
declaration or anything similar to that.
All that I need is the syntax to connect MY_APP_TARGET from this snipet:
to the SourceFile value,
I think you are confused about the purpose of the Binary element. The Binary
element stores stuff inside the MSI for use during the install, it is not the
element that installs files. You want the File element for that. Also, your
Directory tree that you showed below is not a valid directory
TibTam wrote:
Ok, but please help me in on doing that
We decided to use includes because we have huge directory tree and
some parts of the tree are in the main wxs file, and some are in the
included xmls. We need to refer to the folders from the xmls to the
wxs (for example at shortcut cre
aparna wrote:
The Class/@Server attribute cannot be specified when attribute
Advertised is present with value 'yes'
The error is pretty explicit in the code, so I'm not sure what the
problem is. Unfortunately, I don't know much about COM advertisement --
it's not recommended these days.
Don Tasanasanta wrote:
My install has a very large directory structure in which the root
folder is defined by the user. If the user doesn't change the default
root directory then everything works fine but if the default is
changed then the install creates a root folder in the new location but
Chris,
From the snippet you posted below, it looks like you're trying
to, at install time, choose what file gets included in the MSI. That doesn't
work. You have to author the MSI (call this build time) before you can try to
install it. At build time, you have to supply all o
In that case, Could you please tell me the recommended approach to register
a COM server?
-aparna
On 12/8/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
aparna wrote:
The Class/@Server attribute cannot be specified when attribute Advertised
is present with value 'yes'
The error is pretty explici
Thanks, i'll take a look.
What can be the cause of this error (still the same, big, problematic
package)?:
candle.exe : error CNDL0001 : Exception of type
'System.OutOfMemoryException' was thrown.
Exception Type: System.OutOfMemoryException
Stack Trace:
at System.String.GetStringForStringBu
35 matches
Mail list logo
