Hi all,
When a new program is installed, XP/Vista generally highlight the
start menu shortcut in orange (unless you have disabled it). Is there
anything that can prevent this from happening?
The shortcut from an installer I'm currently working on never appears
as a new program with
HI Stefan
Thanks a lot. Its working
Stefan Pavlik-2 wrote:
SaiTeja wrote:
actually I want to assign C:\ to some property. Presently I hardcoded
like
this.
Property Id=INSTALLPATH Value=C:\/
And am using this property in many places. Suppose if machine doesn't
have
C: drive it
Thanks for your attention!
The problem was that the typelib´s of some comvisible assemblies were not
registered. I thought that tallow would extract this information as well
when I ran tallow -c on the dlls.
I solved it by:
1 running regasm on my comvisible assemblies.
2 manually extracting the
That happened to me too, but I shut up because I thought there must be a
better way and I was about to be educated. :)
Tobias Holm wrote:
Thanks for your attention!
The problem was that the typelib´s of some comvisible assemblies were not
registered. I thought that tallow would extract this
Bob Arnson wrote:
Tony Hoyle wrote:
I've been tasked with modifying an existing installer to include
localised country names. Unfortunately wix seems to be mishandling
the registry entries and replacing every extended character with '?'.
You need to set a codepage that handles all
Hi All,
I'm trying to find the wxl files for localizing the WixUI. Gábor
mailto:[EMAIL PROTECTED] 's site
http://www.tramontana.co.hu/wix/loc/index.php suggests that most of the common
languages have been released, but I've no idea where to get them from? I found
a few in an early
Raymond Chen had a great blog post about the basics of Start menu
highlighting a couple of years ago that shed some light on the topic.
http://blogs.msdn.com/oldnewthing/archive/2005/11/24/496690.aspx
All that said, my understanding is that it's still kind of a black box
to us installation
Hi,
My INSTALDIR refers to C:\Program Files\Test Program\Client
Client Folder has, Some files and One folder with one file
While uninstalling, all files in Client are deleted properly. But Folder is
not deleted.
After uninstalling, In my program files Test Program Folder, Inside Client
What I think it happens is that the program will uninstall and delete only
the files that have been installed. I remember a note which warns that if
the user creates new files in the application directories, the files created
are not deleted, therefore the application directory is not deleted.
HI ALL,
I have been reading a while around on COM+ setup in wix. Unfortunately I
have not found so far the answer to my question.
My system has the following parameters:
1-sharpdevelop installation (I remark that sharpdevelop itself has got a
local copy of wix library)
2-wix 2.0 installation
I
This code:
ProgId Id=...
Extension Id=xyz ContentType=text/plain
...
Verb Id=6_Edit Command=Edit TargetFile=Notepad.exe
Argument=quot;%1quot; /
...
Works perfectly well in WiX2, but not in WiX3:
C:\blah.xml(65) : error LGHT0094 : Unresolved reference to symbol
It looks to me like the TargetFile attribute is intended to reference a file
you're installing (i.e. the Id of a File element). If you want to target
something other than a file you're installing, create a Property and use a
TargetProperty attribute set to the property ID.
Use an appropriate
It's another codepage problem. The default, codepage 0, forces ASCII only,
no extended characters. Set Product/@Codepage appropriately - you probably
want 1252, Western European.
You should also check that whatever editor you're using to create your .wxs
files is handling the file correctly, that
This is never going to work for you.
The problem is that Windows Installer files are ANSI (byte-oriented
character sets) internally. They can have only one associated codepage, and
it has to be one that can be set as the system default codepage - UTF-8 is
sadly not allowed.
WiX can readily
Hi Bob,
The only registry entries are as following (*snip*)
Action 13:22:14: InstallInitialize.
Action start 13:22:14: InstallInitialize.
Action ended 13:22:15: InstallInitialize. Return value 1.
Action 13:22:15: ProcessComponents. Updating component registration
Action start 13:22:15:
I own and maintain a wiki devoted to WiX at http://wix.mindcapers.com
I have just done some captcha work to avoid spam and have re-enabled
automatic account creation. Until you are a trusted user (known human), you
will be required to answer the captcha question for every edit you make. I
You can embed the sql right in your wxs file using sqlstring instead of
sqlscript. That will allow you to include properties in the sql statements.
Dana
On Dec 7, 2007 10:52 AM, Kevin Idzi [EMAIL PROTECTED] wrote:
Hello, I have a WiX Question. I've started using it for all of my
installs
Thanks, Nathan.
Turns out that having the word Install in the shortcut was enough to
get ruled out. Sheesh!
-kevin
Original message
From: Nathan Stohlmann [EMAIL PROTECTED]
Subject: Re: [WiX-users] Newly installed start menu highlight
To:
Hallo,
Virus found in this message, please delete it without futher reading
Any traveller, whether persian or beluch or afghan he does
this moment. Come! Without waiting to richard, slowly, in
a low voice, i came right.
How to add two conditions to one component in wix 2?
I try AND, OR but don't work
Jacek
--
System poczty na jablko.one.pl
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place
On Wed, 12 Dec 2007 12:16:22 +, Tony Hoyle wrote:
Tony,
It needs to have the native names for 20 odd countries including
korea and japan, so no single codepage is going to work.
Windows Installer still doesn't handle Unicode--I can't simply understand how
the developers got away with
Hey Jacek,
Condition represents just one field in the MSI table. Therefore, you can
have many conditions but they must all be inside the Condition element.
Try this instead.
Component Id=bmp DiskId=1 Guid=C4AC72F8-626F-444C-B7DF-24106409311A
ConditionSOMEPART=1 OR SOMELANG=1/Condition
Something
Windows Installer only removes files that were installed (and were not
marked Permanent). It only deletes folders that are empty. If your
application creates files in those folders and you want to ensure that they
are deleted when you uninstall the application, use appropriate RemoveFile
elements
As you've discovered, it basically comes down to knowing what the tools do in
this area. For example, regasm on an assembly registers classes and typelib,
but regasm with the /regfile option just generates class registration in the
output .reg file (no typelib entries). In Tallow's (open!)
DEXK JAHN, GXbor wrote:
Windows Installer still doesn't handle Unicode--I can't simply
understand how the developers got away with this :-)) So, it's not a
WiX limitation...
Maybe MSI 4 wil fix it.. we can only hope.
Tony
Considering the default versioning rules and non-versioned files, I'm wondering
if someone can help me see a better way to handle a problem.
The development team that I support deploys ASP.NET webservices which have
lots logic datadriven by XML files that are installed on the server side.
Mike Dimmick wrote:
I would strongly recommend using satellite resource DLLs rather than
registry entries if possible. Registry lookups are not free. If you have to
persist with this approach, look at creating a language-neutral installer,
which uses codepage 0, and a collection of language
DEÁK JAHN, Gábor wrote:
You have the link weekly releases at the end of the page but it only
applies to v2. V3 is still a moving target for localization, as far as I know.
That's correct. WiX v2 has 25 loc sets (currently available only in the
weekly source .zip due to a bug that'll be
Adam Langley wrote:
The only registry entries are as following (*snip*)
That's the script generation phase. The script execution phase is where
the values are actually written. Look for
ActionStart(Name=WriteRegistryValues, ...
to see the individual key/value writes. Make sure you
Please keep /wix-users/ on the thread so everyone can participate.
Bryan C. Boettcher wrote:
Well, adding those merge modules also broke other things in the MSI. Do
version incompatibilities (v2 vs. v3) matter? We're using v3.
It shouldn't, as long as the merge modules are correctly
Koloszar Jozsef wrote:
any pointers as to how to do this using wix? (which elements, what to sign,
ect...)
Sorry, I haven't used UAC patching yet. Peter's written about the new
patching tools on his blog http://blogs.msdn.com/pmarcu/.
--
sig://boB
http://joyofsetup.com/
Hi,
Following is my Directory structure
Setup.wxs
--
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder Name=PFiles
Directory Id=TEST_PRG Name=TP LongName =
TEST PROGRAM
32 matches
Mail list logo
