Sorry, I don't have neither enough time to come up with the sample nor ready
sample.
One of the possible solutions for your problem is Qualified components
(http://msdn2.microsoft.com/en-us/library/aa370947.aspx) and PublishComponent
table (http://msdn2.microsoft.com/en-us/library/aa370921(VS.85
She rode me in ecstacy over and over again during our wild lovemaking session -
I guess size really does matter.-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.at
Not a problem! Glad to be of assistance.
Cheers,
Boris
Daryn Mitchell wrote:
>> -Original Message-
>> From: wix-users On Behalf Of Boris Krivonog
>>
> ...
>
>> Attached is a simple VS 2005 project which locates a process by name and
>> sends it a WM_CLOSE.
>>
>
> That's re
> -Original Message-
> From: wix-users On Behalf Of Boris Krivonog
...
> Attached is a simple VS 2005 project which locates a process by name and
> sends it a WM_CLOSE.
That's really generous of you, Boris. Thanks for sharing that with the
community.
Daryn.
--
Just did, same problem. I have a simplified example dll that triggers
the error, however it may not be useful without the context of the
software it is intended for (it's a plug-in). I'm not going to spam
the list with an attachment, but I can send it directly to anyone
who'd like to check
thank you Rob!
On Wed, Feb 27, 2008 at 2:45 PM, Rob Hamflett <[EMAIL PROTECTED]> wrote:
> You need to set the level of those features to something below (or above?
> check the docs) of the
> level used for a Typical install.
>
> Rob
>
> Maxim Vyazovsky wrote:
> > Hi All,
> > I can't understand -
Windows Installer does not count references, strictly. It notes in the registry
which products have installed a component, and where the key path of the
component was installed to. It adds one reference for each product that
installs the component.
When you uninstall a product, or remove a feat
The only difference I can see in the logs is that version 1.0 has this
Component: cECWERM; Installed: Local; Request: Absent; Action:
Absent
And version 2.0 has this
Component: cECWERM; Installed: Absent; Request: Null; Action: Null
I'm inventing these version numbers obviously. This m
On 27 Sep 2007, at 20:03, Kelly Leahy wrote:
>
Sorry for resurrecting an *old* old thread...
> I think you want something like:
>
> Value="[JDKHOME15]" Execute="firstSequence">JDKHOME15 AND NOT
> JVMPATH
> Value="[JREHOME15]" Execute="firstSequence">JREHOME15 AND NOT
> JVMPATH
>
>
Hello again all,
I'm back sooner than I thought I would be, with a reference counting
issue. Imagine you had a software product, you release new versions
every 6 months so customers frequently run previous versions of the
software with current versions. Imagine now that you installed version
1.0 t
In article <[EMAIL PROTECTED]>,
Anidil <[EMAIL PROTECTED]> writes:
> I noticed when I initially tested MSI on a machine I was asked to install a
> JRE .
JRE = Java Runtime Environment?
No, MSI does not require this, but the application being installed
with that MSi may have required it.
--
You need to set the level of those features to something below (or above? check
the docs) of the
level used for a Typical install.
Rob
Maxim Vyazovsky wrote:
> Hi All,
> I can't understand - how to declare feature that it does not included in
> the typical installation
>
> Now i have 4 featur
Hi,
I am trying to implement upgrade in the installer. The application for which
the installer is built is a web based application. This requires creating
application pools, virtual directories in the IIS.
Following is the code that I added for upgrades
So, UPGRADE_FROM_CURREN
Hi All,
I can't understand - how to declare feature that it does not included in the
typical installation
Now i have 4 features, and all these features are included in typical
install, but i want some features to be excluded from typical install.
--
Thanks,
Max
Hooray!! That did the trick..Thanks Boris!!!
Boris Krivonog wrote:
>
> Attached is a simple VS 2005 project which locates a process by name and
> sends it a WM_CLOSE. If that doesn't close the app, it will forcibly
> kill the app; as specified by http://support.microsoft.com/kb/178893.
> In
Attached is a simple VS 2005 project which locates a process by name and
sends it a WM_CLOSE. If that doesn't close the app, it will forcibly
kill the app; as specified by http://support.microsoft.com/kb/178893.
In order to use it, build the attached project, add the build library
(KillMeSoftly.
feature is available with onlu Wix v3.0 right? How do we
implement the same functionality using WiX v2.0?
Mike Dimmick-2 wrote:
>
> Right now the CloseApplication feature can optionally do the following:
>
> - Send a WM_CLOSE message to the process's main window(s);
> - Set a property if the
Thanks for the reply Boris.
As per my understanding, there is a feature with Wix
v3.0 which sends the WM_CLOSE message to the systray.exe.But right now i'm
using WiX v2.0; any idea how to implement the same here?
Boris Krivonog wrote:
>
> You should terminate your system tray application "soft
You should terminate your system tray application "softly", meaning that
you send WM_CLOSE message to systray.exe. This way, the systray.exe
application is notified that it is about to shut down and has time to
remove icon from tray. See link for details:
http://support.microsoft.com/kb/178893.
Hi,
Yes, you can do a per-user installation of COM component, but then, only the
installing user can instantiate that COM component since it is registered only
in that user's registry.
How does you per-user installation fail? How do you install the COM component,
using the TypeLib element or i
20 matches
Mail list logo
