Спецкурс по международным перевозкам в Москве
Участники курса рассмотрят сравнительные логистические характеристики
различных видов транспорта, узнают о методах выбора перевозчика, получат
представление об особенностях международных перевозок, изучат основные методы
моделирования
Just to add my thoughts on this.
For me the key thing was learning that deployment is hard, no very hard!
I was relatively late to MSIs but have used Wise Installer and SMS
Installer (same thing really) to write many script based installs. I
found these tools hide far too much from me and
I have an MSI that is intended for Only Vista and Vista SP1.Can anybody give
me some hints to prevent install on Windows 2008? I have tried the following
condition but it doesn't work
Condition Message= blah blah WindowsBuild = 6000 OR WindowsBuild =
6001 AND ServicePackLevel = 1/Condition
NB:
Hello all,
Is it possible to install IIS (ie one of the standard Windows Components)
via WIX/Windows installer?
Thanks,
John.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual
Example:
Condition Message=Only Vista install supported VersionNT = 600 AND
ServicePackLevel = 1/Condition
For more, see this link:
http://msdn.microsoft.com/en-us/library/aa370556(VS.85).aspx
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
I have tried that but still it's not preventing install on Windows 2008..
Holmgren Mathias wrote:
Example:
Condition Message=Only Vista install supported VersionNT = 600 AND
ServicePackLevel = 1/Condition
For more, see this link:
Вниманию Участников ВЭД всё о экспорте и импорте товаров в 2OO8 г.
4-6 июня 2OO8 г.
Новое во внешнеторговой сделке и ее таможенном оформление в 2OO8 г.
В семинаре принимают участия специалисты из Российской Таможенной Академии,
ФТС России, Отдела таможенных режимов ЦАТ.
04 06
Выход собственника из оперативного управления компанией
03-04 июня, Москва, эксклюзивный семинар-практикум
Может ли собственник без последствий для бизнеса:
- Передать управление наемному менеджеру?
- Продать компанию?
- Заняться новым бизнесом?
В программе:
Кризис ролей владельца и
Check out the amazing shots taken by these paparazzi http://www.cosatenal.com/
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Anidil wrote:
I have tried that but still it's not preventing install on Windows 2008..
Windows 2008 is the identical kernel to Vista SP1 (in fact Win2008 makes
a great client OS for development - Vista without the cruft.. several
people here have switched to it already).
There should be no
Well I dropped by to ask for help (I wonder if I will get it now :-)) but
first I have to chime in and agree with Chris and Mark. I dislike that what
I am about to post is basically a rant, but I think there are a lot more
people on their side than others seem to think, so I want to show my
How about MsiNTProductType or some of the other MsiNTXXX properites?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anidil
Sent: Tuesday, May 13, 2008 00:31
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] To Prevent Install on Windows 2008
I
I just updated WiX from the 2925 build (still the last beta posted to SF)
to the May 9 weekly build 4109. Now all of my WiX project don't build.
They don't even get started. I instantly get this error when trying to
build:
3-- Build started: Project: Stream, Configuration: Release Any CPU
Checkout the ServiceInstall/ and ServiceControl/ elements.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Willie
Burton
Sent: Tuesday, May 13, 2008 11:29 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] installing services with wix
Is there a way besides using a
I just saw a bug get opened about the build targets having issues. Try 4102
and if that fixes the problem then you probably are seeing the same bug. I’ll
make sure the bug gets fixed by the next build.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer
Sent: Tuesday,
Cool thanks.
Another thing... I dropped in an older wix.targets file so I could do a
build and noticed that output from Light didn't have the right
line-endings.. everything showed up on one line in the dev studio output
window.. The build was done and I didn't even know it because the message
Agreed.
Software Engineering is many times about risk management. Many projects leave
understanding the deployment model of an application until just before it
ships, and then because MSI often isn't well understood and the product wasn't
written to work well with MSI people run into problems
As this was my comment I thought I should respond.
I believe you should write the install then the code - if you can't install
it, don't code it.
That's simply not the way it works, and that isn't going to change. I get
where you are coming from though... the general installation layout of
Hello.
I am trying move out of InstallShield to Wix. I used Wix 2 about a year
ago however now I like to know which build should I use going forward.
I don't like to start using version 2 and in less than a year, upgrade
it to version 3.
Cheers
Reza Farzin
Computer System Analyst
Is there any manual or referece about WIX3?
I'm using version 2 now because there's tutorial and manual of it but I
couldn't find any for WIX3.
If anyone knows, please tip me off
-
This SF.net email is sponsored by:
On Tue, May 13, 2008 at 1:26 PM, Josh Rowe [EMAIL PROTECTED] wrote:
snip
The moral of the story is that deployment procedures really are part of
the source code for an application. They are also risky, so implement them
first to minimize risk.
This is the problem. Deployment SHOULD be
4102 works better.. though it still has problems with Light output. The
text description of errors is missing - you just get a code, and it's all on
one line in visual studio.
Scott
On Tue, May 13, 2008 at 12:02 PM, Scott Palmer [EMAIL PROTECTED] wrote:
Cool thanks.
Another thing... I
I take it back 4102 crashes visual studio... The huge lock ups I could
tolerate... barely.
Why doesn't someone address the issue where running Light.exe locks up the
entire dev environment (let alone bring the entire machine to a crawl) for
several minutes? I always laugh at the little pop-up
МОСКВА ТЕАТРАЛЬНАЯ
495 517 83 08 495 202 86 89
билеты, доставка
LADIES NIGHT. Мужская комедия для женщин - 19.05, 9, 16, 23.06 - В.
ЯРЕМЕНКО, Г. КУЦЕНКО, М. БАШАРОВ, Э. КЮРДЗИДИС
Scott,
I actually agree with you. Deployment SHOULD be trivial. It's usually risky
and non-trivial because people tend to write programs that require special
steps during deployment. By understanding the desired deployment model
up-front you reduce the tendency to write software that
I know what you are saying here. I don’t know enough about the Visual Studio
architecture to understand why this happens but I’ll ask the guys working on
Votive again.
PS: I know what is taking forever in light.exe, two things. 1. Cabinet
creation is I/O intensive and can take a while. 2.
The line endings is a different bug that has been open for a long while.
Again, I don’t understand Visual Studio integration well enough to know what is
causing this.
Are you by chance running on VS2005? I’m beginning to think that because
pretty much everyone working on WiX has moved to
Yes, I am using VS2005. The 2925 build on SourceForge works properly with
the line endings. That narrows it down to only around 1200 builds :-)
Regards,
Scott
On Tue, May 13, 2008 at 4:12 PM, Rob Mensching [EMAIL PROTECTED]
wrote:
The line endings is a different bug that has been open for
Yeah, unfortunately “1200” == “one year”. Okay, I’m going to kick Justin to go
back and look at VS2005. I’m more and more certain that behavior is regressing
badly on that codebase and not being tested except by people picking up new
drops. I appreciate any bug fixes you can open and please
Looking at converting to WiX 3 from WiX 2.
FragmentRef seems to be gone. I used these fairly extensively in V2.
Most everything is in a Fragment and I pull everything together with the
FragmentRefs. Any suggestions for the best way to proceed? I'm not sure
what to substitute for those
This is not WiX specific but this does happen to installs authored in WiX as
well
If you search the web for error 1937 you will see that there are many people
out there encountering this error on many different products; including VS
2008, MS Office, and .Net Framework. It happens at the
You are invited to CLICK (RSVP to this invitation)TO READ YOUR MESSAGE INSIDE.
By your host Phillipe Ouattara:
Date: Tuesday May 13, 2008
Time: 9:00 pm - 10:00 pm (GMT +00:00)
Will you attend? RSVP to this invitation at:
The WiX toolset creates references for you. Likely you don't need the
FragmentRefs at all.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chad Petersen
Sent: Tuesday, May 13, 2008 14:12
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] FragmentRef - Converting from WiX 2
The HRESULT: should provide a error code that details why it failed.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta
(Volt)
Sent: Tuesday, May 13, 2008 14:18
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Error 1937
This is not WiX specific but this
I hate the locking as well. Unfortunately, this is a bug in the MPF (the Visual
Studio SDK) that they have not fixed yet. We will have to just fix it on our
own instead of waiting for a fix from them. Note that it's not a trivial fix
either because it requires a separate thread to do the build.
The long lines in VS 2005 has been around for a while. This is due to a bug in
Visual Studio 2005 that was fixed in Visual Studio 2008. There are some ways
around this bug, but none of them are pretty. We'll have to take another look
at it and see what we can come up with.
Justin
From:
During uninstallation of our product, the FilesInUse dialog appears (as
expected), the user clicks Ignore and at the end is prompted for a reboot.
However, if the user selects 'yes', the reboot does not occur.
Looking in the log there are many entries regarding files that need a reboot
to
2) If this is a known problem, I tried to skip starting services if the OS
is vista using
InstallExecuteSequence
StartServices Suppress=yesVersionNT = 600/StartServices
/InstallExecuteSequence
but it do not respect the condition and it don't let start the services on
any OS. Is
The blog mentions bug 1581071:
http://sourceforge.net/tracker/index.php?func=detailaid=1581071group_id=10
5970atid=642714
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: Monday, May 12, 2008 1:16 PM
To: Jody Belka (WCS);
Administrative Installation
(http://msdn.microsoft.com/library/aa367541.aspx) is not directly related to
custom actions running with administrative privileges
(http://msdn.microsoft.com/library/aa368069.aspx).
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harini
Gurusamy
Sent:
Since this conversation is going nowhere (perhaps because WiX is dependent
on MSI, and MSI seems to predicate most of the limitations) I would like to
introduce a tangent: whether other install / deployment / packaging
technologies have made an impact.
How about Altiris Software Delivery
Hello,
I'm new to WiX (and Windows Installer in general). I've hit an issue
that I cannot seem to solve with Google or help documents...
I have an install file that presents a configuration dialog where users
can enter database connection string information, which is used to
update a
42 matches
Mail list logo
