ИНТЕРНЕТ МАГАЗИН МЕБЕЛИ
Наша фирма занимается продажей и производством мебели уже более 14 лет.
Надеемся, что наша мебель Вам понравится и Вы подберете необходимую мебель
для себя.
mebelnyirai.ru
Телефоны: 364-04-53, 508-67-63, (499) 168-84-88
Мусорные пластиковые котейнеры, объем 60-1100 л.
Каталог и розничные цены на сайте: www.c-msk.ru
Оптимально для дома, офиса, дачи, промышленности.
НОВИНКА СЕЗОНА! ЦВЕТНЫЕ НАКЛЕЙКИ НА КОНТЕЙНЕРЫ!
У нас заказывает даже Фаина из города Белогорск.
Hi,
I am deploying to a directory under C:\Inetpub\wwwroot (e.g.
/Deploy/Sources/Application) and want to create the Application directory as
an IIS Application.
I can get it to create the application fine, however it also creates virtual
directories for /Deploy and /Sources (which I
I tried searching on Google and not much is coming back. If anyone could
help, I would appreciate it greatly.
WiX Version Info:
Microsoft (R) Windows Installer Xml Compiler version 3.0.3617.0
Snippet from my project file:
Component Id=C_SQL_AutoFind6SQL
Hello all,
My main development machine seems to have gotten a little confused. I've been
working on an install but just recently the uninstall is only removing some of
the files that are installed into [INSTALLDIR].
This is on Vista (Don't ask!).
I've set up brand new Vista and XP Virtual
Take a look at this thread:
http://community.installshield.com/showthread.php?t=181109
Specifically:
http://community.installshield.com/showpost.php?p=417549postcount=12
Run your uninstall with logging to see what's happening.
John Daintree [EMAIL PROTECTED] wrote:
Hello,
I am using V3.0.4116 to build a MSI file and I encountered the issue
when I tried to install a WiX generated MSI that creates a
WebSite/Virtual directory on Vista with SP1. The same MSI file could
successfully be installed on Vista without SP1.
From the error code E_ACCESSDENIED in the
Chris,
Thanks for the references. I'll compare and contrast the uninstall log from the
problem machine with the clean one.
john.
- Original Message -
From: Christopher Painter
To: John Daintree ; wix-users@lists.sourceforge.net
Sent: Friday, May 30, 2008 4:10 PM
Subject:
As was much discussed, all of the WiX mailing lists now require subscriptions
to the list before to mail will be delivered.
Hopefully, this will drive down spam but not new adoption. smile/
-
This SF.net email is sponsored
Hello -
For some reason my install packages is not detecting the prior install,
and the upgrade process is not working. I'm unable to see what I've done
wrong and hoping it's a simple thing.
Here's what I have:
Product Id=*
Version=$(var.Util-VersionDots)
Hi,
I have an exe file in a WIX installer, call it MyApp.exe.
Right clicking on this file and going to properties, then to Details shows that
its File Description is My Application, which it has picked up from the
resources when the file was built.
Is there a way to change the File
I don't believe any of those are missing on Windows 2000.
The program below is one I run to do a sanity check on this kind of thing. I
assume that protected system files are highly unlikely to be missing because
they are part of the core OS. It doesn't work on Vista because of the change in
I have not checked the first point. I have to write small C/C++
program to verify the requirement to use API. Or I have to dig the
documentation.
For the second point, I only need to do one of them to successfully install.
Thanks,
Hidemto Yamauchi
On Fri, May 30, 2008 at 11:29 AM, Rob
The templates are updated in today's build 3.0.4130.
Thanks for the feedback John and others. In addition to fixing the VS2005
compatibility issues, I fixed the reference assembly inclusion and improved the
build and clean behavior. The MakeSfxCA step now runs after the Compile step
but before
Downloaded and installing as we speak. :-) Thanks Jason!
Jason Ginchereau [EMAIL PROTECTED] wrote:
The templates are updated in today's build 3.0.4130.
Thanks for the feedback John and others. In addition to fixing the VS2005
compatibility issues, I fixed the reference assembly inclusion
I have the script below stored in a file called IISScripts.vbs.
I have this in my wxs file:
Binary Id=IISScripts src=IISScripts.vbs/
CustomAction Id=SetIISLog BinaryKey=IISScripts
VBScriptCall=SetIISLog Return=check /
InstallExecuteSequence
InstallExecute
When I was at Continental I saw plenty of cases where either WMI or the SMS
Advanced Client would just become corrupt, crap out and need to be repaired.
One of the guys on our team had actually written a script called WMI Reloaded
( he was a huge Matrix fan ) that would bulldoze the entire
My approach has been to separate the prerequisites bootstrapper (which still
probably needs to be C++) from the chainer, which I am currently building in C#.
Prerequisites work well data-driven, because almost everything can be described
as a registry item search, product code, service name,
I can agree with that. If you make the assumption that the C++ code is
responsible for getting MSI 4.5 and .NET 2.0 on the box, basic MSI servicing (
install, upgrades, multiple instances, ectera ) and then do everything as
embedded chaining and UI via DTF/C# from within the actual MSI, the
Christopher Painter: Can you show me how? I see a weblog element in the v2 chm
but it does not allow me to specify the directory for the log file -- just the
type. I'm constrained to wxs v2.
Thanks,
Siegfried
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
I've been building DTF CA's and then consuming and testing them via
InstallShield. Now I'm trying to play with WiX a bit and test my CA's via a
Votive WiX project inside the same solution.
When I right click the WiX Project ( .MSI ) I don't get an option to set it
as the default project
How can I have particular SqlScript files executed conditionally based on
debug mode? Basically I would like to install certain tables and stored
procedures when the install is built in debug mode (via visual studio).
Also, where can I find the latest documentation for the unstable releases?
Is
That feature does not exist in Votive. Feel free to open a Feature Request on
SourceForge, I don't see one there for that.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Painter
Sent: Friday, May 30, 2008 1:31 PM
To:
Thanks. BTW, do you have a simple way of accomplishing doing something like a
ProjectReference? I'm trying to wire up the CA.DLL into the Binary SourceFile
and have it work regardless of solution configuration and without doing some
kind of postbuild xcopy step if possible.
Jason
Adding a reference from the WiX project to the CA project allows you to use
var.ReferencedProjectName.* preprocessor variables. See the example XML snippet
at the bottom of my blog post:
http://blogs.msdn.com/jasongin/archive/2008/05/23/custom-action-project-templates.aspx
Previously, Justin
I need to make a correction for my statement in the previous email.
Adding 'msidbCustomActionTypeInScript +
msidbCustomActionTypeNoImpersonate', of course I have to add
''msidbCustomActionTypeInScript' to specify
'msidbCustomActionTypeNoImpersonate'', does prevent the error, but
WebSite/Virtual
I'm working on doing a major upgrade for a Wix install. Both the original and
version I'm upgrading to are Wix built installs.
When the install runs, I'm able to detect that an upgrade is in process, and
the install procedes normally. The Add/Remove Programs list shows just the
new version.
So,
chrpai wrote:
Sounds like an ALLUSERS problem. Basically the first install was either
per-user or per-machine and the second one was the other.
FindReleated/RemoveExisting only processes the same type so you ended up
with two installed products. One registered for AllUsers and one
The logfile would tell you what's happening.
tsollas [EMAIL PROTECTED] wrote:
chrpai wrote:
Sounds like an ALLUSERS problem. Basically the first install was either
per-user or per-machine and the second one was the other.
FindReleated/RemoveExisting only processes the same type so you
If you zip and attach the logs I could take a look at it for you.
tsollas [EMAIL PROTECTED] wrote:
chrpai wrote:
The logfile would tell you what's happening.
I was looking for something a little more specific, as the MSI log file
output is cryptic, at best. I did find in the log that
Can somebody help me figure out what I'm doing wrong here. I'm trying to
lookup a file path in the registry and then do a FileSearch to see if it
meets the minimum version I require. Here's my code:
Property Id=FLASH_FILE_PATH
RegistrySearch Id=FlashFilePath Root=HKCR Type=file
31 matches
Mail list logo
