The reason I coded that tidbit this morning was to lead u to ensure  
that the XML File you're reading, and the ISOTest.exe your using are  
both in the same Directory, or storage area what ever you want to call  
it.  From the sound of this post and your answer to me.  you may be  
suffering from a visual studio error.  I don't know what to call it,  
only how to explain it.

Scenario 1: Build 1 Project with all the included files.  This  
produces build output all in one release directory.

Scenario 2: Build 1 Projeect to Store Projects 1 2 and x.  The build  
process builds Release\1.exe, Release\2.exe, and Release\x.exe, all in  
their own namespace etc even though they are all part of one master  
project.  The trick here is that the master project builds no output  
it self, it only triggers the building of your included projects.  If  
this is the approach you used, you will have separate assembly  
bindings, as David points out.  My assumption is you wanted one  
binding??  In that case, each subproject you add should be a member of  
the same Namespace, like so:

MasterNamespace.IsoTestApp
MasterNamespace.XMLFileCreator
MasterNamespace.OtherItems

This forces the compiler to put all the output objects in one build  
directory, and when run, since they all share the same namespace they  
should all see eachother's different parts.

Carter


Quoting David Watson <dwat...@sdl.com>:

> Ideally configuration like this should be done at first run by your  
> application.
> Your installer should deploy the config file in a safe place under  
> your installation folder somewhere where it is not in use then it  
> should be copied to the live location during configuration by the  
> application.
> This way you can patch or update the config file without having the  
> headache of working out if it has changed by the user. All the  
> complex logic can go in your application.
>
> Doesn't answer your question though.
>
> How are you accessing the public methods of the .exe from your  
> custom action, it may this binding that's going a bit weird?
>



------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to