Hi
Thanks for the information I was able to fix the first two errors, whereas the
third on still remains. It could be great if anyone can suggest me on the below.
3) Not a valid source file; detail: The 'Directory' start tag on
line 57 does not match the end tag of 'Component'. Line 62, p
You don't say if the XP is 32 or 64 bit. You also didn't mention trying it
on 32-bit Win7.
I think it is a bitness issue, and the binary you are harvesting may be
written to accommodate it. According to this page
[http://msdn.microsoft.com/en-us/library/ms680091(v=VS.85).aspx] what the
ProxyStubCl
When I use heat.exe v3, or tallow.exe to gather registry information
on XP, I get the following data:
When I use heat.exe v3, or tallow.exe to gather registry information
on Win7 x64, I get the following data:
Is there a reason for the missing ProxyStubClassId entry on Win7 x64?
Thank
Anybody else been experiencing issues with build server errors like these:
Tracker.exe: Response file
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\e77d4f39272d45b581881d1fbf1378e9.rsp
not found.
I'm getting these errors only when building wix projects. I was at 3.5.1616.0,
but
Well, after much goofing around, I think UPGRADINGPRODUCTCODE check is
working for what I need. My design is wrong from the start to re-order
removal of existing products... but I will design the next installer with
this method in mind.
Thanks so much for your help Blair... and the great explana
In the first option, the steps are:
- build the updated msi with all the changes
- perform admin installs of both the current release and the newly built msi
- create your patch as a diff between the 2 MSIs (as usual) with torch, pyro
and a wix file.
The difference is that the wix file contains
I can certainly build through to completion and do an admin install. I require
that to ensure that the new baseline the patch is being pulled from actually
works in the first place. You lost me completely though about how to use the
Family element.
The second suggestion does seem like qu
Hi,
Wix files are XML based and as such follow its syntax rules.
Elements have to be self closing
Or in pairs with an opening and closing element.
The error is fairly literal, you have a with an unmatched
Maybe you have a typo, if you can't spot it you could post the code in
an email to th
On Tue, 5 Oct 2010 10:13:19 +
Sravan Kumar Rangaraju wrote:
> Hi All,
>
> I am encountering the below errors while building the wxs file can
> someone help me on this.
>
>
> 1) Tag was not closed
>
> 2) Expecting end tag
>
> 3) Not a valid source file; detail: The 'Direct
Hi All,
I am encountering the below errors while building the wxs file can someone help
me on this.
1) Tag was not closed
2) Expecting end tag
3) Not a valid source file; detail: The 'Directory' start tag on line 57
does not match the end tag of 'Component'. Line 62, position
Hi All,
I am encountering the below errors while building the wxs file can someone help
me on this.
1) Tag was not closed
2) Expecting end tag
3) Not a valid source file; detail: The 'Directory' start tag on line 57
does not match the end tag of 'Component'. Line 62, position
This is the same situation as we have here.
It's preferable, if you can to carry the build through to completion to produce
a new, updated MSI as though you were going to do a major upgrade. Then perform
an admin install of that and add Ref elements into the Family element to choose
which parts
12 matches
Mail list logo
