Hi
Can anyone please let me know what is the best practice for deploying
Sharepoint
components. We are planning to have WIX installer for all our sharepoint
projects. Please share your experiences in case you have worked on it earlier.
Regards
Anweshi
"I have code as below" did you mean to paste some code in your reply?
I looked around, but I didn't see any .cub files in either the downloaded "
Windows 7 Client Software Logo Toolkit - RTW" file or the installed Logo Kit
installation directory...
-Original Message-
From: Pally Sandher
You shouldn't need to schedule the MigrateFeatureStates action manually. The
UpgradeVersion element has an attribute called MigrateFeatures that you can
set to "yes".
As an example:
-
Learn WiX with the book:
https://www.packtpub.com/wix-a-developers-guide-to-windows-installer-xml
Hi.
I'm trying to support major updates for my application and it works fine so far.
Except for feature states.
I'm testing an update from version 1.9.0 to 1.9.1
ProductCode changes between MSIs (it's "*"/auto-generated for me)
Component GUIDs are stable for me (fixed)
1.9.0 and 1.9.1 have the s
>"An attempt was made to load a program with an incorrect format" usually
>indicates a 64/32 bit mismatch.
>
>Are you trying to load 64 bit candle in a 32 bit msbuild or something
>similar?
Yep, I think that is the issue. I was on vacation for a week and
while I was gone an "emergency" upgra
The ICE tests try to take into account scenarios that are rarely used, and
because of that are (at least somewhat) messed up (IMHO). Ideally you will
suppress individual reports instead of having to suppress the entire ICE,
but ...
-Original Message-
From: Will Sullivan [mailto:wsulli...@s
Windows Installer defines the ServiceInstall table with a foreign key to the
Component table because it considers each row of the ServiceInstall table to be
part of that component (exactly the same as files and registry values). Thus,
separating the service and file parts of the component is a s
The description for ICE69 says that it occurs when a formatted string is used
to reference a component.
http://msdn.microsoft.com/en-us/library/aa369019%28VS.85%29.aspx
Is Heat creating a file that uses formatted strings in this way?
-
Learn WiX with the book:
https://www.packtpub.com/wix-
Thanks Nick for your time. The picture is getting clearer.
Yes, I do intend buy this book but in ebook format to start off with.
Satesh
From: Nick Ramirez [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+5682799-1873990454-298...@n2.nabble.com]
Sent: T
It didn't come through bu that ampersand is actually the XML entity & plus
amp;
-
Learn WiX with the book:
https://www.packtpub.com/wix-a-developers-guide-to-windows-installer-xml/book
WiX: A Developer's Guide to Windows Installer XML
--
View this message in context:
http://windows-instal
Did you ever figure this out? If not, does this work for you?
-
Learn WiX with the book:
https://www.packtpub.com/wix-a-developers-guide-to-windows-installer-xml/book
WiX: A Developer's Guide to Windows Installer XML
--
Thank you for reply,
But still its not working.
i have same custome action in my another MSI which is made for 32bit
machine,and it works fine.
is it issue of Solution configuration is Debug and Solution platform is x64
as MSI is made for 64bit machine
On Thu, Oct 28, 2010 at 7:43 PM, Nick Ra
So, it sounds like you're trying to create an installer, but have recent
builds of your product incorporated in automatically? A sort of
constant-integration installer?
I think you may be on the right track by using Heat. It's a good tool for
generating a WiX source file for you. You probably al
In the log, does it give a specific error code after the part where it says
it's returning a status of 3? Oftentimes it will and you can use that to
look up its meaning.
I noticed that you're running this custom action as "immediate". If you're
deleting files, should it come during the deferred s
I find that logic concerning. What build of 3.5 did they use? How
frequently do they switch to a new build? What is the criteria they follow in
determining a new build is safe? Do they have special access to risk
awareness
by nature of internal relationships that you don't have? Do they h
Use a bootstrapper.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Hel
Hey, I have made a program, which uses gtk#.
Is it possible to add gtk# installer to my .msi? Or what would be the best
approach for that?
--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Crea
No, I meant that the Visual Studio 2010 MSI contains dlls from WIX 3.5 which
indicates that the Visual Studio 2010 installer was built with WIX 3.5. If
Microsoft uses 3.5 for releasing production code, we can.
They haven't integrated it into their runtime of Visual Studio 2010.
_
I also do have problems installing the latest weekly release (wix
3.6.1022.0). When trying to launch the setup from the wix36.exe
bootstrapper, it just says "Failed to install". When running the installer
by double-clicking the wix36.msi file in the "data" subdir, it starts and
runs for some time
I found a workaround to complete the 3.6.1022.0 installer: When the error
message complaining about wix36lib.cab appeared, I replaced this file with
the one from the 3.6.1015.0 and clicked retry.
Now I can build my .wixproj projects again from VS2010.
Something seems to be wrong with the 3.6.1
Does the Windows 7 logo testing suite come with new ICE .cub files which
are more lenient for ICE43 & ICE57? I have code as below for All User
Start Menu shortcuts in an All User package & it passed logo testing but
that was around 6 months ago so the test suite has probably been updated
since then
WiX v3.5 isn't technically more stable than WiX v3.0 (in development
beta code versus released final code) but if you want to use VS2010 you
have to use WiX v3.5 as VS 2010 didn't exist when WiX v3.0 was released.
Having said that unless you're using the new features in WiX v3.5 such
as IIS7 or .NE
"An attempt was made to load a program with an incorrect format" usually
indicates a 64/32 bit mismatch.
Are you trying to load 64 bit candle in a 32 bit msbuild or something
similar?
-Original Message-
From: Kevin Jones [mailto:krjon...@aye.net]
Sent: 28 October 2010 00:19
To: wix-users
23 matches
Mail list logo
