Not good at this inline stuff but I hope you can follow...

Personally I think it is a big issue. For me the dev cycle of WiX is too long, 
so I have to take what you have written and make it stand alone so I can keep 
it in my own dev/build cycle. That means making it build in an environment that 
anyone can build with no more than just the instruction "install WiX".

My BA - For the same reason, the Std BA wouldn't build without a lot of hassle, 
mine builds on it is own, you can download it from Codeplex and as long as WiX 
is installed you run build.bat - job done.

The only reason I say the extensions is that that was the original theme of my 
comment. I would like to add to the IIS Extensions if it was easy.

I appreciate the issue of splitting the code but in my opinion it would be 
worth it, as I see it it is currently too complex. I have been trying to build 
WiX code for many years and it has never been possible to resubmit my changes 
because the codebase is not structured in a way that makes it easy so I have to 
rely on submitting bugs and hoping you guys can fix them. For example, the IIS 
site code bug, the IIS log folder bug, IIS mine types - I solved these years 
ago but by writing extra code rather than enhancing the core code.

I am not trying to be negative (I am all for being devil's advocate too), I 
would just like it to be easier to contribute which I think would help the core 
code.

Neil

From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 19 January 2013 18:29
To: wix-devs@lists.sourceforge.net
Subject: Re: [WiX-devs] Building WiX Code

On 19-Jan-13 08:37, Neil Sleightholm wrote:

(Playing devil's advocate. For the record.<g>)


The problem I see with building and therefore contributing is that the code is 
structured as a single unit and to build any one part you have to have built 
the whole thing.
How serious an impediment do you think it is? Yes, you have to build a couple 
parts of the tree (not the whole thing, though that's the easiest approach) but 
only once. Then you can churn inside one project without ever rebuilding 
anything.


For example, I have created my own BA and the first thing I had to do
Why did you have to do that?


To make things easier I would like to suggest that all the WiX extensions
Why the extensions? Or, why *just* the extensions?


The BalExtension is quite good in that all the source is in the same folder but 
many others e.g. the IIsExtension has the code spread around to you have to 
look in the "ext" folder and "ca\serverca" to find the code.
It just requires a bunch of splitting the DLLs, mostly the Util stuff that 
lives in serverca.


--

sig://boB

http://joyofsetup.com/
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs

Reply via email to