anged
is empty.
Tom Isaacson
-Original Message-
From: Interest [mailto:interest-bounces+tom.isaacson=navico@qt-project.org]
On Behalf Of Henry Skoglund
Sent: Friday, 10 March 2017 11:56
To: interest@qt-project.org
Subject: Re: [Interest] Support for Visual Studio 2017
Hi, just gu
al Message-
From: Karsten Heimrich [mailto:karsten.heimr...@qt.io]
Sent: Thursday, 9 March 2017 23:22
To: Tom Isaacson ; Qt Interest
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
ableExtension
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 ; Qt Interest
Subject: RE: [Interest] Support for Visual Studio 2017
Hi,
w
ch, 8. März 2017 18:16
To: Qt Interest
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 Ka
erest
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=nav
Behalf Of Tom Isaacson
Sent: Monday, 27 February 2017 07:46
To: Constantin Makshin ; Qt Interest
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 rel
Sent: Monday, 27 February 2017 07:46
To: Constantin Makshin ; Qt Interest
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/
stantin Makshin
Sent: Sunday, 26 February 2017 12:51
To: Qt Interest
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
17-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: Q
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
Subject: Re: [Interest] Support for Visual Studio 2017
Still looks so
gt; 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: wh
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:
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
Subject: Re: [Interest] Support for Visual Studio 2017
On quinta-feira, 23 de fevereiro de 2017 02:08:12 PST Jean-Michaël Celerier
wrote:
> Some MS guys said on reddit that VS2017 has ABI compatibility with
> VS2015, so maybe it'll just work ?
Remains to be proven, but we'd l
On quinta-feira, 23 de fevereiro de 2017 02:08:12 PST Jean-Michaël Celerier
wrote:
> Some MS guys said on reddit that VS2017 has ABI compatibility with VS2015,
> so maybe it'll just work ?
Remains to be proven, but we'd like to know from experience by our users: what
happens if you just take the
QtWebKit supports VS2017
>
> Oliver
> Send from a Mobile Device. Encoding Problems can happen.
> Originalnachricht
> Von: NoRulez
> Gesendet: Donnerstag, 23. Februar 2017 07:38
> An: Qt Project MailingList
> Betreff: [Interest] Support for Visual Studio 2017
>
> Hell
Some MS guys said on reddit that VS2017 has ABI compatibility with VS2015,
so maybe it'll just work ?
Best,
Jean-Michaël
On Thu, Feb 23, 2017 at 10:28 AM, NoRulez wrote:
> Thank you very much for the clarification
>
> > Am 23.02.2017 um 08:52 schrieb Thiago Macieira <
> thiago.macie...@intel.co
Thank you very much for the clarification
> Am 23.02.2017 um 08:52 schrieb Thiago Macieira :
>
>> On quarta-feira, 22 de fevereiro de 2017 22:38:09 PST NoRulez wrote:
>> Hello,
>>
>> since visual studio 2017 will be released on march 7th, which Qt version
>> will support it?
>
> Qt 5.8.0, unl
On quarta-feira, 22 de fevereiro de 2017 22:38:09 PST NoRulez wrote:
> Hello,
>
> since visual studio 2017 will be released on march 7th, which Qt version
> will support it?
Qt 5.8.0, unless Microsoft broke something after the last RC.
> Are there any pre-builts for it?
Not yet. That will happ
Hello,
since visual studio 2017 will be released on march 7th, which Qt version will
support it?
Are there any pre-builts for it?
Thanks in advance
Regards
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/
20 matches
Mail list logo
