QtWS16- Introducing Qt Visual Studio Tools, Maurice Kalinowski, The Qt Company

About this tutorial:

Video duration: 21:58
Day 2 at QtWS16, Maurice Kalinowski, The Qt Company “Introducing Qt Visual Studio Tools”
Many Qt users enjoyed the benefits of the Qt Visual Studio AddIn provided for various Visual Studio versions, starting with Visual Studio 2010. Unfortunately, Microsoft decided to deprecate the API to implement an AddIn a while ago and completely removed this functionality with Visual Studio 2015. This caused a significant break in developer experience for those users who have been relying on the Qt Visual Studio Addin. Hence, the Qt Company has been working on the Qt Visual Studio Tools, which will…

Post Author: OfficeTutes.com

Apple lover, ICT and LEAN consultant, MS Office lecturer My other website with video tutorials - Tutorials, guides and news for iPhones and iPads

8 thoughts on “QtWS16- Introducing Qt Visual Studio Tools, Maurice Kalinowski, The Qt Company

    Rukna Eejrenab

    (September 11, 2019 - 10:40 am)

    what theme are they using??

    Çağlar Dursun

    (September 11, 2019 - 10:40 am)

    qt.natvis file has poor support of Qt data types. A few variable definition exists which like QRect, Qpoint etc.That's why the debugging on vs or vscode is a pain in the ass. Have you ever try to see inside of QFile or QJSonDocument object ? You should understand what I meant

    Otuya david odeke

    (September 11, 2019 - 10:40 am)

    Could you make a video about combining QCustomPlot with visual studio….I am getting link issues as soon as I add the qcustomplot.h and qcustomplot.cpp files

    João Nogueira

    (September 11, 2019 - 10:40 am)


    Vicenzo Vendetta

    (September 11, 2019 - 10:40 am)

    I'm planning to use Qt, but I don't want to install more IDEs, and after reading things even the comment from Gnarrrl, I think Qt IDE is not so good in debug, that is essential for any kind of programming. So I would like to know if there's any support to VS17?


    (September 11, 2019 - 10:40 am)

    it's going to be sweet when the qt creator just works within vs


    (September 11, 2019 - 10:40 am)

    Developing on Windows, targeting Windows and Android with QtQuick, we use Qt Creator as the development IDE but are practically forced to use MSVC for debugging and profiling purposes. Why? Because the debugger integration in Creator looks like a childs toy compared to Visual Studio. It's painfully slow, not just when resolving local variables but also the application is running noticeably slower when attached compared to MSVC. It does not support custom expressions in watches (anything except "locals" is practically unusable anyway; try to do calculations or call const functions within watch), data breakpoints, stepping into qt sourcecode by pointing the debugger to the source file in debug builds or setting comprehensive debug break conditions, the thread view contains almost no information, the list goes on and on… The whole debugging interface in Qt Creator is severely lacking in amount and depth of information it provides to the developer in general.
    Visual Studio instead offers powerful performance and memory profiling tools for C++ even in the community edition. The only thing MSVC is missing out of the box is a resolver that can interpret and pretty print qt objects like QString. I sure don't miss having to develop with MSVC itself (started in 2001), nor dealing with its horrible make system, but the debugger and profiling tools are great and I would be very happy to see more qt-aware tools of a similar or greater power level shipping with Qt Creator some day.

    MK Ultra

    (September 11, 2019 - 10:40 am)

    I tried it but it is still too buggy. Have some serious Intellisense issues.

Leave a Reply

Your email address will not be published. Required fields are marked *