Thanks for the reply Bob. It appears that neither DIFx or DPInst support
the Sensor driver type. SetupAPI appears to work just fine, installing
the sensor as a "legacy" driver -- funny yet sad.
/rafael
On 2/26/2010 11:32 AM, Bob Arnson wrote:
> On 2/24/2010 10:33 AM, Rivera,
Howdy.
I put together a WiX 3.0 package, utilizing the DIFx extensions, to
install a Windows 7 Sensor (UMDF driver). During installation, DIFXAPP
logged "No matching devices found in INF" and simply threw the driver
into storage. I read I'm to populate my INF with an appropriate
DriverPackageT
Hi Chris,
Implemented Categories can be looked up in the registry properly,
instead of relying on Google, in HKEY_CLASSES_ROOT\Component Categories.
The GUID for generic .NET stuff is {62C8FE65-4EBB-45E7-B440-6E39B2CDBF29}.
I could not reproduce the issue you mentioned using 2.0.50727.4927 of
Right.
I responded to your previous email...
/rafael
-Original Message-
From: Vuchuru, Surekha (SBT US EXT) [mailto:surekha.vuchuru@siemens.com]
Sent: Monday, July 20, 2009 1:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Wix warning LGHT1076 :
I noticed Ondrej was having similar issues, so thought I'd report my
experience with shortcuts. Upon building of my MSI with the following
snippet, the shortcut gets created but points to file02.
If I ensure my Files, with Shortcut children, are placed first, the problem
Hi there.
$(env.xxx) is merely a pre-processing directive that means "substitute with
the compiling machine's value of env. variable xxx". It's not evaluated at
execution of the package, so you're in fact hard-coding a value (e.g.
C:\Documents and Settings\All Users). This is not what you want, he
ge that I noticed in the patch log:
>
> [snipped]
>
>
> -Original Message-
> From: Rafael Rivera [mailto:raf...@withinwindows.com]
> Sent: Thursday, July 02, 2009 3:17 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Patching a p
Chris,
Those elements appear to simply identify what certificate should be
given the green light for patching. I believe you still need to
digitally sign the resulting MSI using signtool.exe.
- Rafael
Chris Bardon wrote:
> My goal for getting patching to work is to be able to deploy an applica
Okay, I'll bite. Why do you need the Windows temporary folder vice the user's?
Sent via BlackBerry from T-Mobile
-Original Message-
From: "Igor Paniushkin"
Date: Thu, 2 Jul 2009 13:45:55
To: General discussion for Windows Installer XML
toolset.
Subject: Re: [WiX-users] How to referen
Neil, et al -
Disregard last transmission. Corrected an error on my end. Thanks for
the help.
- Rafael
Rafael Rivera wrote:
> Hi Neil,
>
> We looked into using WindowsVolume but it's still being set to D:\ vice
> C:\. I'd prefer to just expand an environmental variable
>
>
>
>
>
> This will normally set DATALOCATION to "C:\My data folder".
>
> Hope this helps.
>
> Neil
>
> -Original Message-
> From: Rafael Rivera [mailto:raf...@withinwindows.com]
> Sent: 24 June 2009 17:25
Howdy!
With ROOTDRIVE behaving more like DRIVEWITHMOSTSPACE, what's the
recommended approach to installing to the Windows volume?
I noticed there is environmental variable support... $(.) is evaluated
at compile time, !(.) at link... but what about at runtime? I found an
old post suggesting th
E-mail реклама - старт Вашего бизнеса! Мега качество от профессионалов.
Cамые полные регулярно обновляемые базы (Москва, Россия, СНГ)
Cамое современное оборудование
Отчет о проделанной работе
495: - 646-07-2О
-
This SF.net
Kuhne <[EMAIL PROTECTED]>
To: Bob Arnson <[EMAIL PROTECTED]>; Rafael Rivera Jr. <[EMAIL PROTECTED]>
Cc: wix-users@lists.sourceforge.net
Sent: Tue Oct 31 14:42:24 2006
Subject: RE: [WiX-users] Custom Action Type 17 (DLL, C++) Path?
Note that on Vista files in the same directory WON&#x
From: Bob Arnson <[EMAIL PROTECTED]>
To: Rafael Rivera Jr. <[EMAIL PROTECTED]>
Cc: wix-users@lists.sourceforge.net
Sent: Mon Oct 30 10:50:16 2006
Subject: Re: [WiX-users] Custom Action Type 17 (DLL, C++) Path?
Rafael Rivera Jr. wrote:
> Is there a way to explicitly specify the path
Hi,
Yet another email from me.
I've written a shiny new custom action support library for new shiny new
MSI file. I've jumped through all the right hoops coding wise but am
seemingly running into a manifest issue with Debug CRT libraries
(MSVCR80D.dll). My library and its dependencies have a m
Bob/Rob,
Thanks for the tips, works as advertised.
Respectfully,
Rafael
Bob Arnson wrote:
> Rafael Rivera Jr. wrote:
>
>> Are there any gotchas associated with ripping Tallow out of 2.x and
>> using that (understanding some changes may have to be done to the
>> ou
Is there a way to explicitly specify the path in which my Custom Action
Type 17 action runs in? It has a dependency on a library at init.
(imported) and cannot find it (Filemon shows it searching my PATH).
Thanks in advance,
Rafael
---
--
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Rafael
> Rivera Jr.
> Sent: Saturday, October 28, 2006 11:47
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Heat + .rc support?
>
> I'm new to WiX but quickly catching on. Unfortunately, I
been migrated into Heat yet?
Respectfully,
Rafael Rivera Jr.
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Downloa
20 matches
Mail list logo
