Qt in Visual Studio 2013
-
Hi and welcome to devnet,
Unless you are using some very specific VS feature, you can use Qt Creator while waiting for an updated Add-in
-
or you could do a manual install of the vs addon and see if it works with vs 2013 - little harder then said but do-able
-
im working on it myself now,
got it installed just need to change a couple of assembly versions
ill give you a shout once i get it done[edit] got it working :) ill just upping the files now
-
here you go :)
this is an unoffical version, works a treat for me
http://www.minioncoding.com/QTVS2013Addin.ziphope this helps
Phil -
[quote author="StaticPhilly" date="1384621620"]here you go :)
this is an unoffical version, works a treat for me
http://www.minioncoding.com/QtforVS2013.zipif your on windows 64 bit then:
@extract the zip, copy the Digia folder to c:\Program Files (x86)
run the "qt vs 2013 reg keys 64bit" reg file@if your on a 32bit version of windows then
@extract the zip, copy the Digia folder to c:\Program Files
run the "qt vs 2013 reg keys 32bit" reg file@hope this helps
Phil[/quote]Thank you very much
-
[quote author="StaticPhilly" date="1384621620"]here you go :)
this is an unoffical version, works a treat for me
http://www.minioncoding.com/QtforVS2013.zip
[/quote]Hi Phil,
I was just myself facing this problem as I was changing from VS2012 to VS2013, but sadly your link does not work as the connection times out.
Is this a DynHost that is maybe not always available?Thanks,
Apollo -
Hi Apollo,
Im just on rebuilding the machine that I use as the web host, if you give me about 30 mins ill have it all back online again.
-
Apollo, Sorry Iv had one of those days were iv not been able to sit for 5 mins without something coming up :)
what iv done is packed it into an installer, the reasons being are:
It now registers the dll so you can use the new project wizards without it causing an error
When the official version is released its easy to remove
No need to edit a reg file anymorehttp://www.minioncoding.com/files/QTVS2013Addin.zip
and yes of course you can mirror if you wish :)
[Edit]
Just a positive note :)
Because I only use a static Qt libs, unlike the official version, I did not have to include the typical dll;s you normally do with a Qt application, so instead of a typical 40+meg install its now to 14meg - if only it was the days when space was such an issue xDalso the first zip I posted is still up so if you don't want an installer then you can use that, just remember to reg that dll
-
reupload plese
-
You don`t need installer to work with addin in Visual Studio 2013.
Just do next steps:- Copy contents of "C:\Program Files (x86)\Digia\Qt5VSAddin\11.0" folder to
newly created "C:\Program Files (x86)\Digia\Qt5VSAddin\12.0". - Run VS2013, goto menu Tools->Options->Environment->Addin Security,
add "C:\Program Files (x86)\Digia\Qt5VSAddin\12.0" folder to the list. - Restart VS2013.
And voila, you have QtVSAddin working in VS 2013 :).
- Copy contents of "C:\Program Files (x86)\Digia\Qt5VSAddin\11.0" folder to
-
[quote author="couragic" date="1388153881"]
But Wizards, Q_OBJECT headers handling and other qt stuff doesnt work :(.[/quote]In other words, that makes it useless.
If I may make a suggestion to whoever maintains this plugin... I have some gripes I need to vent. But first, no, I cannot use Qt creator so please don't suggest it.
a) The mechanism by which the plugin stores metadata on which files to MOC is black magic. Right now I can't figure out how the plugin "remembers" which files to moc. It makes it hard to make changes to this by hand. It requires manual, annoying steps in point d) below.
b) Is it possible for us mere mortals to understand how the plugin goes from knowing which files to process, to actually constructing the command-line it seems to add to the custom build? More black magic by the plugin? It seems to either works in full, or fails and you're SOL with no ability to troubleshoot.
c) The sources to the plugin are useless. Why? Because even though we can compile this abomination, from there, it isn't clear how to produce the final installer. And for anyone that knows anything about this plugin, the job done by the installer is just as important as the job done by the plugin. Case in point -- this thread, where merely adding the plugin to VS is useless.
d) Too often I end up in broken situations, where I have to remove Q_OBJECT from all my files, or, remove all my files and re-add to the project. I have hundreds of files across many folders, so this process is manual and painful and while doing this I send curses to some unknown soul out there every time I need to do it (too often).
Ok I'm done, thanks.
-
Hi enry,
Have you tried wiping your build tree and re-running qmake? Qt "remembers" which files need re-moc-cing/rebuilding using Makefiles. qmake generates these Makefiles.
If you want to reach the maintainer of the VS Add-In, try subscribing to and then posting the "Interest mailing list":http://lists.qt-project.org/mailman/listinfo/interest. That's where many Qt engineers are.
-
Unfortunately this website doesn't seem to exist right now:
http://www.downforeveryoneorjustme.com/http://www.minioncoding.com
Can anyone who downloaded the file post it somewhere more stable?I was wondering if the current installer is going to work for Visual Studio 2013, because I found this article that suggested that add-ins had been deprecated:
http://msdn.microsoft.com/en-us/library/5abkeks7.aspxWhat I'm really interested to see is if the new VSPackage will install on Visual Studio 2013 Express...
-
Hi all!
Here is "QTVS2013Addin.zip":https://mega.co.nz/#!nMRDWQzR!W2lCQ3-tuReacwEUbv0i2yB3acVqYAVbnd6xl21Ey7o installer originally created by StaticPhilly uploaded to mega file share.
Installed and seems worked well in VS2013 Ultimate.
