From: Matthew Chambers <matthew.chambers@va...> - 2009-12-18 19:41:19
I don't understand what you mean "for test purposes" or "cannot be
packaged in a converter." What I do know is that due to the dependence
on .NET components (Agilent, Bruker, and ABI all include .NET) the
framework is a hard requirement when any of those components are part of
the build. And because of linkage to .NET, dynamic linkage to the C++
runtime is required. Thus the additional dependency on the MSVC
redistributable. However, both .NET and the MSVC redistributable can be
put in as "merge modules" in an installer package. Including all of .NET
would obviously be a very big package though which is why most
installers that need that capability just point to the online source to
download .NET on the fly; including the MSVC redistributable is small so
I can't tell you how many installers I've run that also install the
redistributable. It would be possible to have msconvert with only Thermo
and Waters support be linked statically to the MSVC runtime, but all the
other readers need .NET.
For cases where a machine has no network access, you'll obviously have
to deliver pwiz by optical or flash drives, so I suggest that in such
cases you not only include the pwiz tarball but also the MSVC 2008sp1
redistributable and the full .NET 3.5.sp1 installer. And 7zip since the
built in zip support can't extract tarballs. :) Now that we have a
TeamCity configuration for non-express Visual Studio, I may add a
deployment project to create an MSI installer for pwiz. But that won't
happen in the immediate future (from me, anyway).
And no, you don't need technically need Protein Pilot or MassLynx to use
the converters for their formats, but rather for legal reasons since
that is (as yet) the only mainstream legal way to get the
WiffFileDataReader /ClearCore and DACServer DLLs. We are close to
replacing the DACServer-based Waters reader with one based on a new
native C++ API, we're just waiting on a license agreement. And we're
waiting, and waiting, and waiting, and waiting on a license agreement
for redistribution of WiffFileDataReader.
Hope this helps,
Pierre-Alain Binz wrote:
> Hi Matt,
> As I understand, for Proteowizard, one needs to install MVC and .NET
> In the case I’m working on, I would need to use “only” msconvert to
> extract raw (thermo) or wiff (ABI) ( and Waters raw in a few of weeks)
> into mzML (or mzXML).
> If I get access right to the 4 ABI dlls, do I need the whole battery
> or can I somehow reduce it?
> My problem is the following: for test purposes, it is pretty heavy to
> install MVS and .NET. This cannot be packaged in a converter, as these
> are Microsoft components.
> A prospect might be ok to click a few times on next-next, but if they
> have to download and install manually these prerequisits, it might be
> blocking. Compared to for instance mzWiff or ReAdW (even if the
> functionalities there are reduced and a bit buggy) is much more
> convenient. One solution is to incorporate, into an installer, all the
> links to the Microsoft downloads. But this requires network, which is
> in a number of cases in clinics not available for MS instrumentation….
> Do you see a solution?