none
Call to Devenv from plugin hangs when Rebuilding a sln file

    Question

  • Hi,

    We are attempting to rebuild a sln file via plugin which calls devenv. This is done through the command prompt the path is set from the VS2013 command prompt. When we call devenv it fails to rebuild the sln file. We think it maybe an issue that is derrived VS.

    We use Windows server 2008 R2, Visual Studio 2013 update 3, and if it matters TFS 2013 update 2.

    the command we use is

    >xyz -b %buildid% devenv abcdefgh.sln /REBUILD DEBUG

    Please advise.

    Hansal

    • Moved by Caillen Monday, December 08, 2014 6:09 AM
    Wednesday, November 05, 2014 6:49 PM

Answers

  • If devenv abcdefgh.sln /REBUILD DEBUG hangs without your plugin involved you should start there.

    Ensure in the Add-In Manager that you don't have add-ins marked as safe for the command prompt.

    Try rebuilding different solutions to see if the problem is a specific solution or your VS environment. Try on different machines.

    Once you get devenv abcdefgh.sln /REBUILD DEBUG working on a VS command prompt, you can get back to calling that command line from a console app. BTW, why do you call xyz a plugin that calls devenv.exe? Plugins for Visual Studio don't call devenv.exe, they are loaded by devenv.exe (VS).


    * My new blog about VSX: http://www.visualstudioextensibility.com * Twitter: https://twitter.com/VSExtensibility * MZ-Tools productivity extension for Visual Studio: http://www.mztools.com.

    Thursday, November 06, 2014 7:35 AM

All replies

  • - Does it work if you run the following from the VS command prompt?

    devenv abcdefgh.sln /REBUILD DEBUG

    (that is, without your plugin xyz?)

    - Which error do you get?

    - How is your plugin calling devenv?


    * My new blog about VSX: http://www.visualstudioextensibility.com * Twitter: https://twitter.com/VSExtensibility * MZ-Tools productivity extension for Visual Studio: http://www.mztools.com.

    Wednesday, November 05, 2014 9:24 PM
  • also tried the comman via the VS command line and no error it just hangs it shows nothing. the command is being run with the plugin. Not entirely sure as to how the plugin calls devenv.

    Thanks for responding.

    Wednesday, November 05, 2014 9:47 PM
  • If devenv abcdefgh.sln /REBUILD DEBUG hangs without your plugin involved you should start there.

    Ensure in the Add-In Manager that you don't have add-ins marked as safe for the command prompt.

    Try rebuilding different solutions to see if the problem is a specific solution or your VS environment. Try on different machines.

    Once you get devenv abcdefgh.sln /REBUILD DEBUG working on a VS command prompt, you can get back to calling that command line from a console app. BTW, why do you call xyz a plugin that calls devenv.exe? Plugins for Visual Studio don't call devenv.exe, they are loaded by devenv.exe (VS).


    * My new blog about VSX: http://www.visualstudioextensibility.com * Twitter: https://twitter.com/VSExtensibility * MZ-Tools productivity extension for Visual Studio: http://www.mztools.com.

    Thursday, November 06, 2014 7:35 AM
  • I tried this on multiple machines same issue as you can see below. The tool we use requires a rebuild to happen via VS and then a translation of the project occurs so the tool can do what it needs to. Can you think of a reason as to why devenv won't respond even when running the VS command prompt as administrator. Thanks for your help.


    C:\Windows\system32>e:

    E:\>cd dev\abcdefgh\Development\Development\Source\abcdefgh\

    E:\Dev\abcdefgh\Development\Development\Source\abcdefgh>devenv abcdefgh.sln /REBUILD DEBUG

    Microsoft Visual Studio 2013 Version 12.0.30723.0.
    Copyright (C) Microsoft Corp. All rights reserved.
    1>------ Rebuild All started: Project:abcdefgh, Configuration: D
    ebug Any CPU ------
    2>------ Rebuild All started: Project: abcdefgh, Configuration: De
    bug Any CPU ------

     

    Thursday, November 06, 2014 2:51 PM
  • We have tried multiple solutions and they all hang 95% of the time.  This has happened after upgrading to Visual Studio 2013 from 2012.  We also tried a different machine with no plugins installed and it still hangs for multiple solutions when building via command line.

    Friday, January 09, 2015 7:13 PM