|
John, thanks for your comments. This
is kind of the same thought that some of us had. In reality, there’s not
a huge benefit to moving to 2.0. We wanted to do it mainly to have a consistent
build environment for our tools. Votive for the 3.0 branch will be exclusively
.NET 2.0 targeting VS 2005. If we didn’t get any pushback for the idea,
we thought we’d just move everything to the 2.0 branch. It sounds like
there are users out there (yourself included) that rely on having a 1.1 version
of the tools. We’ll most likely stick with having a 1.1 version around, but
we’ll leave the thread open for more feedback. Justin From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
Lemire I think it’s very nice that candle/light/etc now run on
either. We too develop apps that must run on either so we have some dev
boxes that only have 1.1 on them. Naturally this includes the automated build servers which only have
1.1 and VS2003 on them to ensure no code references 2.0 classes. Perhaps if you itemized a few pros/cons it would help make the
descision clearer. eg. the impetus is these x proposed features would be significantly
easier to develop using these y new 2.0 framework classes. Can’t say because I’m very new to wix and haven’t
even looked at the source yet but just in thinking of what these tools do
it’s not obvious where new 2.0 classes would be of great benefit. I don’t think as a dev tool we can really say that perf is an
issue and hence probably not generics either. I’d have to say if there are truly time/pain saving use cases
for new 2.0 framework classes then I’d be open to taking the pain of
having to build the installer on a 2.0 box. However if it’s just because of the pain having VS2003 around
or the pain having to set up B to enable targeting 1.1 from VS2005 then
I’d lean against it. Managed plugin api wise I could certainly see how future versions
of votive could only target VS2005. I think it would be a fair tradeoff to say
if you want to use VS2003 you’re stuck with votive 3.0 or less but
that’s because there’s a big distinction between an authoring tool
and a building tool. exactly two cents worth J, -john From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Justin
Rockwood There has been some talk on the core team about moving Wix
3.0 over to use the .NET Framework 2.0 instead of 1.1. We wanted to know how
many people this would affect and in what ways. If you have any concerns about
using .NET 2.0, please respond to this email and let us know. Conversely, if
moving to .NET 2.0 would help you, please let us know that as well. Thanks, Justin |
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
