That's a pretty good summary of the MPF. J To answer your question more
completely. VB/C#/C++ were all written using the native C++ project system
that was in existence years before MPF even came about. MPF is part of the
Visual Studio SDK and was written originally as a port of the C++ code. The
problem (IMHO) is that the native code project system was flawed in its
design to begin with. It was overly complex and burdensome to work with. The
VS SDK team had a golden opportunity to clean it up and make it so much
easier to use when creating a new SDK for Visual Studio based on managed
code. Unfortunately, I don't think they got it right. Interestingly, in
Votive 2.0 I had written my own SDK that was a lot easier to use than the
MPF (it was before the MPF was around). I think knowing what I do now about
the MPF and the bugs/lack of features, I might not have switched over to it.
At any rate, I don't foresee VB/C#/C++ being rewritten to use the MPF since
it is not up to par (yet).
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Don Caton
Sent: Wednesday, May 14, 2008 9:53 PM
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Did WiX V3 projects break compatibility with
earlier builds?
Scott:
MPF stands for 'Managed Package Framework', an incomplete and buggy
framework for building project systems that integrate into Visual Studio.
It's part of the Visual Studio SDK. Consider yourself lucky that you don't
have to deal with it.
Don
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer
Sent: Wednesday, May 14, 2008 9:43 PM
To: Justin Rockwood
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Did WiX V3 projects break compatibility with
earlier builds?
It seems the real bug then is that there are two code paths... VB/C/C++
should be implemented via the MPF stuff as well... then this never would
have happened. I say this still not knowing what MPF stands for or anything
about it though.
Scott
On 14-May-08, at 10:45 AM, Justin Rockwood wrote:
No, other projects that are not based on the MPF (which includes VB/C#/C++)
do not lock because they do not have that bug. However, projects that are
based on the MPF (IronPython, if I remember correctly) do exhibit the same
bug that WiX has. This bug, in my mind, is one of the most annoying ones
that should have higher priority (along with the other one that you pointed
out - same line output). Thanks for the bug reports!
Justin
From: Scott Palmer
Sent: Wednesday, May 14, 2008 7:14 AM
To: Justin Rockwood
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Did WiX V3 projects break compatibility with
earlier builds?
On Tue, May 13, 2008 at 7:05 PM, Justin Rockwood wrote:
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.
Are you saying that other tasks like compiling and linking C/C++ code lock
things the same way.. but I assume for short enough periods of time that it
isn't noticeable? I'm just wondering why I only notice this with WiX
projects.
...
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
