Friedrich, Oliver schrieb:
AFAIR its not the Value, that is too long, but the identifier, that should
not be longer than 255.
Qt_accessible_qtaccessiblecompatwidgets1Modul.57F8AC9F_2E4B_4879_A18C_172F2EB1.0
Try to shorten it a bit.
Oliver Friedrich
Consultant - Software Solutions
Friedrich, Oliver schrieb:
Well, ICE03 claims following in Windows-SDK:
The string's length is greater than the column width specified by the column
definition. Note that the installer does not internally limit the column
width to the specified value. See Column Definition Format.
So
Hello, how can I do this, so that more apps can use this files.
In my case it will be binary files. But no library files.
smime.p7s
Description: S/MIME Cryptographic Signature
-
Take Surveys. Earn Cash. Influence the Future
Hello, by default side-by-side assemblys are placed under
%SystemRoot%\WinSxS\assembly...
But I my case I need, that the assembly dll put under
%SystemRoot%\WinSxS\assembly...\foodir
Any idea's how I can make that?
smime.p7s
Description: S/MIME Cryptographic Signature
Geoff Finger schrieb:
For me the assemblies are automatically removed on uninstall. I have
found however that during the testing process when i'm doing a lot of
installs and uninstalls in thre process of debuging my Wix code that
the state of things sometimes gets screwed up and files end up
Geoff Finger schrieb:
That looks correct for the final manifest file. Offhand the only
possible problem I can is that manifest files may not be equiped to
handle umlauts. Try using a different file name?
Yes, but the same result.
Any other idea's?
Frank
smime.p7s
Description: S/MIME
Frank Büttner schrieb:
Geoff Finger schrieb:
That looks correct for the final manifest file. Offhand the only
possible problem I can is that manifest files may not be equiped to
handle umlauts. Try using a different file name?
Yes, but the same result.
Any other idea's?
Frank
Now
all do. But the build fails with the error above.
Here is my file that I have tried:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Module Id=QtCoreModul Language=0 Version=4.2.2.0
Package Id= Manufacturer=Frank Büttner
Frank Büttner schrieb:
These steps has I all do. But the build fails with the error above.
Here is my file that I have tried:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Module Id=QtCoreModul Language=0 Version=4.2.2.0
Package Id
Geoff Finger schrieb:
Wix doesn't check the validity of the keys, that happens when the file
is actually installed into WinSxS. As far as I know it's not a bug
although that would be some great added functionality for Wix.
The public key is what you get by running pktextract on the
Frank Büttner schrieb:
Geoff Finger schrieb:
Wix doesn't check the validity of the keys, that happens when the file
is actually installed into WinSxS. As far as I know it's not a bug
although that would be some great added functionality for Wix.
The public key is what you get by running
Hello, when I build this Wxs file:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Module Id=QtAssistentClientKatalogModul Language=0 Version=4.2.2
Package Id=XXX Manufacturer=X InstallerVersion=300/
SFPCatalog Name=QtAssist.cat
How can I integrate an .cat file in my merge module.
This file is needed for my side-by-side assembly.
Simple use the File Tag will get the error:
error LGHT0104 : Not a valid manifest file;
How can I do this??
smime.p7s
Description: S/MIME Cryptographic Signature
must I change in the .wix file?
Here my code:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Module Id=QtAssistentClientModul Language=0 Version=4.2.2
Package Id=37691951-bcaf-4845-bd35-8239bca76dbc Manufacturer=Frank
Büttner InstallerVersion=301
Hello, how can I build an merge module witch will be installed as shared
side-by-side assembly under the WinSxS folder under the OS.
The files that must installed are C++ files compiled with the VS C++
2005 Express. So I thing it must be possible. But how.
At first I have build an default merge
Bob Arnson schrieb:
Frank Büttner wrote:
I have open an Bug report for some day on SF, but until now nobody has
replay to it.
It will likely take a while to track down the cause of the bug.
Are some news about fixing plains for it?
smime.p7s
Description: S/MIME Cryptographic Signature
I have try it but the file is too big for an upload it is 1,43MB but SF
only allow 250KB:(
smime.p7s
Description: S/MIME Cryptographic Signature
-
Using Tomcat but need to do more? Need to support web services, security?
Get
Bob Arnson schrieb:
but light will never return:(
How can I debug this to find out what goes wrong??
Start with -notidy and -v0 to see if you can pinpoint when it happens.
The only output I get is:
Microsoft (R) Windows Installer Xml Linker version 2.0.4415.0
Copyright (C) Microsoft
Hello, when I try to build my merge module light freeze.
What I have try:
candle -nologo -sw1044 *.wxs //to build all object's
light -nologo .wixobj
but light will never return:(
How can I debug this to find out what goes wrong??
smime.p7s
Description: S/MIME Cryptographic Signature
Hello, I try build merge modules witch needs other merge modules.
But when try to use it. The dependency's will not solved. Any ideas?
smime.p7s
Description: S/MIME Cryptographic Signature
-
Using Tomcat but need to do more?
20 matches
Mail list logo