Unfortunately it fails for me:
10/03/2017 11:31:08 AM - Microsoft VSIX Installer
10/03/2017 11:31:08 AM - -------------------------------------------
10/03/2017 11:31:08 AM - vsixinstaller.exe version:
10/03/2017 11:31:08 AM - 15.0.26228.0 built by: D15REL
10/03/2017 11:31:08 AM - -------------------------------------------
10/03/2017 11:31:08 AM - Command line parameters:
10/03/2017 11:31:08 AM - C:\Program Files (x86)\Microsoft Visual
Studio\2017\Professional\Common7\IDE\VSIXInstaller.exe,C:\Users\Tom\Downloads\qt-vsaddin-msvc2017-2.1.1-beta
(1).vsix
10/03/2017 11:31:08 AM - -------------------------------------------
10/03/2017 11:31:08 AM - Microsoft VSIX Installer
10/03/2017 11:31:08 AM - -------------------------------------------
10/03/2017 11:31:09 AM - Initializing Install...
10/03/2017 11:31:09 AM - Extension Details...
10/03/2017 11:31:09 AM - Identifier :
QtVsTools.13121978-cd02-4fd0-89bd-e36f85abe16a
10/03/2017 11:31:09 AM - Name : Qt Visual Studio Tools
10/03/2017 11:31:09 AM - Author : The Qt Company Ltd.
10/03/2017 11:31:09 AM - Version : 2.1.1
10/03/2017 11:31:09 AM - Description : The Qt Visual Studio Tools
allow developers to use the standard development environment without having to
worry about any Qt-related build steps or tools.
10/03/2017 11:31:09 AM - Locale : en-US
10/03/2017 11:31:09 AM - MoreInfoURL : http://www.qt.io/
10/03/2017 11:31:09 AM - InstalledByMSI : False
10/03/2017 11:31:09 AM - SupportedFrameworkVersionRange : [4.6,)
10/03/2017 11:31:09 AM -
10/03/2017 11:31:09 AM - SignatureState : Unsigned
10/03/2017 11:31:09 AM - Supported Products :
10/03/2017 11:31:09 AM - Microsoft.VisualStudio.Pro
10/03/2017 11:31:09 AM - Version : [15.0]
10/03/2017 11:31:09 AM - Microsoft.VisualStudio.Premium
10/03/2017 11:31:09 AM - Version : [15.0]
10/03/2017 11:31:09 AM - Microsoft.VisualStudio.Ultimate
10/03/2017 11:31:09 AM - Version : [15.0]
10/03/2017 11:31:09 AM - Microsoft.VisualStudio.Community
10/03/2017 11:31:09 AM - Version : [15.0]
10/03/2017 11:31:09 AM -
10/03/2017 11:31:09 AM - References :
10/03/2017 11:31:09 AM - Prerequisites :
10/03/2017 11:31:09 AM -
-------------------------------------------------------
10/03/2017 11:31:09 AM - Identifier :
Microsoft.VisualStudio.Component.CoreEditor
10/03/2017 11:31:09 AM - Name : Visual Studio core editor
10/03/2017 11:31:09 AM - Version : [15.0.26208.0,16.0)
10/03/2017 11:31:09 AM -
10/03/2017 11:31:09 AM -
-------------------------------------------------------
10/03/2017 11:31:09 AM - Identifier :
Microsoft.VisualStudio.Component.VC.CoreIde
10/03/2017 11:31:09 AM - Name : Visual Studio C++ core
features
10/03/2017 11:31:09 AM - Version : [15.0.26208.0,16.0)
10/03/2017 11:31:09 AM -
10/03/2017 11:31:09 AM - Signature Details...
10/03/2017 11:31:09 AM - Extension is not signed.
10/03/2017 11:31:09 AM -
10/03/2017 11:31:09 AM - Searching for applicable products...
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio
Professional 2013
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 2013
Shell (Integrated)
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio
Professional 2015
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio
Community 2015
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 2015
Shell (Integrated)
10/03/2017 11:31:09 AM - Found installed product - Global Location
10/03/2017 11:31:09 AM - Found installed product - Visual Studio Professional
2017
10/03/2017 11:31:09 AM - PKGDEF Information: Looking for master PkgDef file,
Path: C:\Program Files (x86)\Microsoft Visual
Studio\2017\Professional\Common7\IDE\master.pkgdef
10/03/2017 11:31:09 AM - PKGDEF Information: Creating PkgDefCacheNonVolatile
10/03/2017 11:31:09 AM - PKGDEF Information: Double-checking master pkgdef file
10/03/2017 11:31:09 AM - PKGDEF Information: PkgDefManagement initialized
10/03/2017 11:31:09 AM - PKGDEF Information: RootFolder, Path: C:\Program Files
(x86)\Microsoft Visual Studio\2017\Professional\
10/03/2017 11:31:09 AM - PKGDEF Information: ShellFolder, Path: C:\Program
Files (x86)\Microsoft Visual Studio\2017\Professional\
10/03/2017 11:31:09 AM - PKGDEF Information: PkgDefSearchPath, Path: C:\Program
Files (x86)\Microsoft Visual
Studio\2017\Professional\Common7\IDE\Extensions;C:\Program Files
(x86)\Microsoft Visual
Studio\2017\Professional\Common7\IDE\CommonExtensions;C:\Program Files
(x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.admin.pkgdef
10/03/2017 11:31:09 AM - PKGDEF Information: ImageManifestSearchPath, Path:
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Professional\Common7\IDE\Extensions;C:\Program Files
(x86)\Microsoft Visual
Studio\2017\Professional\Common7\IDE\CommonExtensions;C:\Users\Tom\AppData\Local\Microsoft\VisualStudio\15.0_d6e029fd\Extensions
10/03/2017 11:31:09 AM - PKGDEF Information: ApplicationExtensionsFolder, Path:
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Professional\Common7\IDE\Extensions
10/03/2017 11:31:09 AM - PKGDEF Information: "ZeroImpact" = dword:0,
"MergeRegistry" = dword:3
10/03/2017 11:31:09 AM - PKGDEF Information: Could not find
ConfigurationChanged timestamp., PKGDEF: 80070002
10/03/2017 11:31:09 AM - PKGDEF Information: Could not find
ConfigurationChanged timestamp., PKGDEF: 80070002
10/03/2017 11:31:09 AM - PKGDEF Information: PkgDefCache flags, PKGDEF: 7001
10/03/2017 11:31:09 AM - PKGDEF Information: Could not find
ConfigurationChanged timestamp., PKGDEF: 80070002
10/03/2017 11:31:09 AM - PKGDEF Information: Could not find
ConfigurationChanged timestamp., PKGDEF: 80070002
10/03/2017 11:31:09 AM - PKGDEF Information: PkgDefManagement startup complete
10/03/2017 11:31:11 AM - The extension with ID
'QtVsTools.13121978-cd02-4fd0-89bd-e36f85abe16a' is not installed to Visual
Studio Professional 2017.
10/03/2017 11:31:17 AM - The following target products have been selected...
10/03/2017 11:31:17 AM - Visual Studio Professional 2017
10/03/2017 11:31:17 AM -
10/03/2017 11:31:18 AM - Beginning to install extension to Visual Studio
Professional 2017...
10/03/2017 11:31:24 AM - Install Error : System.IO.FileFormatException: File
contains corrupted data.
at MS.Internal.IO.Zip.ProgressiveCrcCalculatingStream.Read(Byte[] buffer,
Int32 offset, Int32 count)
at MS.Internal.IO.Zip.ZipIOModeEnforcingStream.Read(Byte[] buffer, Int32
offset, Int32 count)
at
Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.WriteFilesToInstallDirectory(InstallableExtensionImpl
extension, String installPath, ZipPackage vsixPackage, IDictionary`2
extensionsInstalledSoFar, AsyncOperation asyncOp, IProgress`1 progress)
at
Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.PerformLegacyInstall(InstallableExtensionImpl
extension, IDictionary`2 extensionsInstalledSoFar, List`1
extensionsUninstalledSoFar, IInstalledExtensionList
modifiedInstalledExtensionsList, IProgress`1 progress, InstallFlags installFlags,
AsyncOperation asyncOp, Boolean isPackComponent, IInstalledExtension&
newExtension)
at
Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.PerformSetupEngineInstall(InstallableExtensionImpl
extension, Boolean installPerMachine, Boolean isPackComponent, IDictionary`2
extensionsInstalledSoFar, List`1 extensionsUninstalledSoFar,
IInstalledExtensionList modifiedInstalledExtensionsList, IProgress`1 progress,
InstallFlags installFlags, AsyncOperation asyncOp, IInstalledExtension&
newExtension)
at
Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.InstallInternal(InstallableExtensionImpl
extension, InstallFlags installFlags, IDictionary`2 extensionsInstalledSoFar,
List`1 extensionsUninstalledSoFar, IInstalledExtensionList
modifiedInstalledExtensionsList, AsyncOperation asyncOp, IProgress`1 progress)
at
Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.BeginInstall(IInstallableExtension
installableExtension, InstallFlags installFlags, AsyncOperation asyncOp)
at
Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.InstallWorker(IInstallableExtension
extension, InstallFlags installFlags, AsyncOperation asyncOp)
Tom Isaacson
-----Original Message-----
From: Karsten Heimrich [mailto:karsten.heimr...@qt.io]
Sent: Thursday, 9 March 2017 23:22
To: Tom Isaacson <tom.isaac...@navico.com>; Qt Interest
<interest@qt-project.org>
Subject: RE: [Interest] Support for Visual Studio 2017
Hi,
we've uploaded a beta version of the Qt Visual Studio Tools extension to
http://download.qt.io/development_releases/vsaddin .
-- Karsten
-----Original Message-----
From: Interest [mailto:interest-bounces+karsten.heimrich=qt...@qt-project.org]
On Behalf Of Tom Isaacson
Sent: Mittwoch, 8. März 2017 18:16
To: Qt Interest <interest@qt-project.org>
Subject: Re: [Interest] Support for Visual Studio 2017
Thanks. Keep up at https://bugreports.qt.io/browse/QTVSADDINBUG-459
Tom Isaacson
-----Original Message-----
From: Interest [mailto:interest-bounces+tom.isaacson=navico....@qt-project.org]
On Behalf Of Karsten Heimrich
Sent: Thursday, 9 March 2017 05:33
To: Qt Interest <interest@qt-project.org>
Subject: Re: [Interest] Support for Visual Studio 2017
We'll release a test version for VS 2017 within the next few days.
-- Karsten
-----Original Message-----
From: Interest [mailto:interest-bounces+karsten.heimrich=qt...@qt-project.org]
On Behalf Of Tom Isaacson
Sent: Dienstag, 7. März 2017 17:47
To: Qt Interest <interest@qt-project.org>
Subject: Re: [Interest] Support for Visual Studio 2017
*crickets*
Visual Studio 2017 is being released today. Does anyone know if there's a plan
to add support to the Qt Visual Studio Plug-In?
Tom Isaacson
-----Original Message-----
From: Interest [mailto:interest-bounces+tom.isaacson=navico....@qt-project.org]
On Behalf Of Tom Isaacson
Sent: Monday, 27 February 2017 07:46
To: Constantin Makshin <cmaks...@gmail.com>; Qt Interest
<interest@qt-project.org>
Subject: Re: [Interest] Support for Visual Studio 2017
Final release is on March 7th.
We still need the Qt Visual Studio Plug-In. There's a comment from Karsten
Heimrich on the last release page:
http://blog.qt.io/blog/2016/11/11/qt-visual-studio-tools-2-0-released/
"I did an initial commit that supports VS 2017 RC, you can find it here:
https://codereview.qt-project.org/#/c/177499 Once we did some more testing, I will upload
an RC at download.qt.io."
Does anyone know if this happened?
Tom Isaacson
-----Original Message-----
From: Interest [mailto:interest-bounces+tom.isaacson=navico....@qt-project.org]
On Behalf Of Constantin Makshin
Sent: Sunday, 26 February 2017 12:51
To: Qt Interest <interest@qt-project.org>
Subject: Re: [Interest] Support for Visual Studio 2017
Well, if that's true (we still have to wait for the final release of
VS2017) then, as Harri said, upgrade from VS2015 will be much easier for
everyone. :)
On 02/24/2017 08:51 PM, Tom Isaacson wrote:
VS2017 is ABI-compatible with VS2015:
http://stackoverflow.com/questions/40854917/is-visual-c-2017-binary-co
mpatible-with-vc-2015
There's a comment here that suggests VS2017 uses the same C++ standard library
implementation (search for "msvcp140.dll"):
https://news.ycombinator.com/item?id=12967901
"MSVC STL dev here. We're doing something different this time around. VS 2015
RTM and Update 1/2/3 were binary-compatible (as usual) while adding lots of features
to the compiler and STL (unusual). VS 2017 RTM and its Updates will continue to be
binary-compatible while adding features, meaning that our DLLs are still
vcruntime140.dll, msvcp140.dll, etc. The versions are admittedly a mess, so here's
the magic decoder ring:
VS 2015: IDE version 14, DLL version 140, toolset version 140, compiler version
19.0 (the C++ compiler is older than the Visual part of Visual C++).
VS 2017: IDE version 15, DLL version 140 (same!), toolset version 141,
compiler version 19.1 We still recommend that you build everything with VS 2017
consistently, as this will give you the most performance and correctness.
However, you can mix in object files, static libraries, and DLLs compiled with
previous versions all the way back to 2015 RTM, and things will continue to
work (although you won't necessarily activate fixes in the newer version).
For more info, read the comments on
https://blogs.msdn.microsoft.com/vcblog/2016/08/24/c1417-fea... where I mentioned
WCFB02."
Tom Isaacson
-----Original Message-----
From: Interest
[mailto:interest-bounces+tom.isaacson=navico....@qt-project.org] On
Behalf Of Constantin Makshin
Sent: Saturday, 25 February 2017 00:22
To: Qt Interest <interest@qt-project.org>
Subject: Re: [Interest] Support for Visual Studio 2017
Still looks somewhat risky to me. Unless VS2017 uses C++ standard library implementation
from VS2015's "msvcp140.dll", of course.
On 02/24/2017 12:44 PM, Tom Isaacson wrote:
I had the prebuilt VS2015 libraries downloaded and installed and I was able to
rebuild and run our app in VS2017. I didn't have to rebuild Qt myself.
Tom Isaacson
-----Original Message-----
From: Interest
[mailto:interest-bounces+tom.isaacson=navico....@qt-project.org] On
Behalf Of Harri Porten
Sent: Friday, 24 February 2017 20:30
To: interest@qt-project.org
Subject: Re: [Interest] Support for Visual Studio 2017
On Thu, 23 Feb 2017, Tom Isaacson wrote:
It worked for me; I was able to run our VS2015 app in VS2017 with no problems.
I think Thiago meant something different: what if you are compiling your
application with VS 2017 against a set of Qt libraries build with VS 2015?
If that works flawlessly a big upgrade pain of the past would be gone.
Harri.
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
