Details

    • Type: Suggestion Suggestion
    • Status: Reported
    • Priority: Not Evaluated Not Evaluated
    • Resolution: Unresolved
    • Affects Version/s: 1.2.2
    • Fix Version/s: None
    • Component/s: General
    • Environment:

      Win 8, MSVC2013 preview, VS addin 1.2.2

      Description

      For all developers which have to compile C++ projects, VS2012 is useless since it has a bug in the code optimizer and produces crashing code as soon as "toASCIILower()" is called. In contrast, in VS2013 preview this bug is fixed.

      Therefore we have to expect many VS2012 devs to upgrade ASAP to VS2013 as soon as it is released - especially because the already released preview version has a go-live license.

      We should anticipate this and prepare Qt and particularly the VS-addin as soon as possible to support VS2013.

      Since VS2012 is similar to VS2012 in many details, I assume the adaption is primarily only a change in the installation path and in some install checks/procedures.

      1. AddInEventHandler.cs
        47 kB
        Torben Dannhauer
      2. CompilerToolWrapper.cs
        19 kB
        Torben Dannhauer
      3. ExtLoader.cs
        21 kB
        Torben Dannhauer
      4. HelperClasses.cs
        6 kB
        Torben Dannhauer
      5. ProjectImporter.cs
        19 kB
        Torben Dannhauer
      6. QMakeProcess.cs
        14 kB
        Torben Dannhauer
      7. qt5appwrapper2013.csproj
        6 kB
        Torben Dannhauer
      8. qt5appwrapper2013.sln
        0.9 kB
        Torben Dannhauer
      9. Qt5ProjectEngineLib2013.csproj
        8 kB
        Torben Dannhauer
      10. Qt5ProjectLib2013.csproj
        9 kB
        Torben Dannhauer
      11. Qt5VSAddin2013.csproj
        10 kB
        Torben Dannhauer
      12. Qt5VSAddin2013.sln
        4 kB
        Torben Dannhauer
      13. QtDefaultEditorsHelper.cs
        8 kB
        Torben Dannhauer
      14. QtProject.cs
        151 kB
        Torben Dannhauer
      15. QtProjectEngine.cs
        25 kB
        Torben Dannhauer
      16. Resources.cs
        9 kB
        Torben Dannhauer

        Activity

        Hide
        Torben Dannhauer added a comment -

        It is available NOW as prerelease ( alpha) !

        thanks at Qt and Digia team!

        Torben

        Show
        Torben Dannhauer added a comment - It is available NOW as prerelease ( alpha) ! thanks at Qt and Digia team! Torben
        Hide
        felixover added a comment -

        where can i get the alpha?

        big thanks to the Qt team!

        Show
        felixover added a comment - where can i get the alpha? big thanks to the Qt team!
        Show
        Torben Dannhauer added a comment - On http://qt-project.org/downloads just below the current stable release 1.2.2 of the VS addin. http://download.qt-project.org/development_releases/vsaddin/qt-vs-addin-opensource-1.2.3-alpha.exe
        Hide
        Marc-Berco Fuhr added a comment - - edited

        While upgrading our projects from VS2008 to VS2013 I noticed a bug in Qt VS Add-In v1.2.3 (and probably earlier versions). When adding existing Qt-based files (.cpp, .h and .ui) the add-in doesn't create proper entries in MSBuild-based projects.

        This may be because (from what I can see in the source code) the add-in doesn't really honour the change in build environment variables that has happened while transitioning to MSBuild. $(ConfigurationName) is now $(Configuration) and $(PlatformName) is now $(Platform). VS2010 and VS2012 may still support the old names, but as of VS2013 at least $(ConfigurationName) is no longer supported.

        I've logged a bug with Digia, but I thought I should mention it here as well.

        Show
        Marc-Berco Fuhr added a comment - - edited While upgrading our projects from VS2008 to VS2013 I noticed a bug in Qt VS Add-In v1.2.3 (and probably earlier versions). When adding existing Qt-based files (.cpp, .h and .ui) the add-in doesn't create proper entries in MSBuild-based projects. This may be because (from what I can see in the source code) the add-in doesn't really honour the change in build environment variables that has happened while transitioning to MSBuild. $(ConfigurationName) is now $(Configuration) and $(PlatformName) is now $(Platform). VS2010 and VS2012 may still support the old names, but as of VS2013 at least $(ConfigurationName) is no longer supported. I've logged a bug with Digia, but I thought I should mention it here as well.
        Hide
        Alex Blasche added a comment -

        Updating Support labels

        Show
        Alex Blasche added a comment - Updating Support labels

          People

          • Assignee:
            Akseli Salovaara
            Reporter:
            Torben Dannhauer
          • Votes:
            12 Vote for this issue
            Watchers:
            17 Start watching this issue

            Dates

            • Created:
              Updated: