Upgrade for VS 2013

Nov 19, 2013 at 3:31 PM
Hi,

Studioshell has been very useful for automating a lot of actions in Visual Studio. Coupled with Nuget powershell script it is really a must.
Unfortunately the latest version is not working with VS 2013. Do you have any plans to add support?

Cheers

Avi
Dec 31, 2013 at 2:31 PM
Hi,

Any news on the update for VS2013 ?

Cheers

Avi
Coordinator
Jan 29 at 4:43 PM
VS2013 support is now available as of the 1.6 release: https://studioshell.codeplex.com/releases/view/117845

And thanks again for all of your help and effort on this Avi!
Jan 29 at 5:49 PM
I have VS2013 Update 1, and StudioShell could NOT be installed due to incompatibility.
Apr 22 at 6:28 PM
Edited Apr 22 at 6:39 PM
I am having the same problem with VS2013 Update 1, Win7x32.

The .msi installer says, "No compatible version of Visual Studio...".
Installed via nuGet w/i VS2013, it shows up in the list of Installed Packages, but I can't find a way to open the StudioShell window.
Coordinator
Apr 23 at 11:24 AM
The installer searches the registry for specific keys to determine which versions are installed. Can you check if the following registry key exists on your system?

HKEY_CLASSES_ROOT/VisualStudio.DTE.12.0

With regard to the nuget install - did you install the StudioShell package, or the StudioShell.Provider package? The former is ripe with install issues, and the latter is more install-stable but only works inside of the PM console.
Apr 23 at 5:56 PM
HKEY_CLASSES_ROOT/VisualStudio.DTE.12.0 is present.
By "PM Console", you mean the Package Manager console?
Apr 23 at 6:12 PM
PM> install-Package StudioShell.Provider
Installing 'StudioShell.Provider 1.6.4.0'.
You are downloading StudioShell.Provider from Code Owls LLC, the license agreement to which is available at http://studioshell.codeplex.com/license. Check the package for additional dependencies, which may come with their own license agreement(s). Your use of the package and dependencies constitutes your acceptance of their license agreements. If you do not accept the license agreement(s), then delete the relevant components from your device.
Successfully installed 'StudioShell.Provider 1.6.4.0'.
import-module : Could not load type 'CodeOwls.StudioShell.Common.Utility.SessionStateExtensions' from assembly 'CodeOwls.StudioShell.Common, Version=1.6.0.0,
Culture=neutral, PublicKeyToken=null'.
At C:\work\BitBucket\cbpomometro\packages\StudioShell.Provider.1.6.4.0\tools\Init.ps1:40 char:1
  • import-module $modulePath;
  • ~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : InvalidOperation: (:) [Import-Module], TypeLoadException
    • FullyQualifiedErrorId : ProviderStartException,Microsoft.PowerShell.Commands.ImportModuleCommand
Register-ObjectEvent : Cannot bind argument to parameter 'InputObject' because it is null.
At C:\work\BitBucket\cbpomometro\packages\StudioShell.Provider.1.6.4.0\tools\StudioShell.Provider\InitializationScripts\register-solutionevents.ps1:281 char:23
  • register-objectEvent $_.source -eventname $_.event -action $_.action | out-null ...
  • ~~~~~~~~~
    • CategoryInfo : InvalidData: (:) [Register-ObjectEvent], ParameterBindingValidationException
    • FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.RegisterObjectEventCommand
Register-ObjectEvent : Cannot bind argument to parameter 'InputObject' because it is null.
At C:\work\BitBucket\cbpomometro\packages\StudioShell.Provider.1.6.4.0\tools\StudioShell.Provider\InitializationScripts\register-solutionevents.ps1:281 char:23
  • register-objectEvent $_.source -eventname $_.event -action $_.action | out-null ...
  • ~~~~~~~~~
    • CategoryInfo : InvalidData: (:) [Register-ObjectEvent], ParameterBindingValidationException
    • FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.RegisterObjectEventCommand
get-item : Cannot find drive. A drive with the name 'dte' does not exist.
At C:\work\BitBucket\cbpomometro\packages\StudioShell.Provider.1.6.4.0\tools\StudioShell.Provider\InitializationScripts\register-solutionevents.ps1:25 char:17
  • $script:sln = get-item dte:/solution;
  • ~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : ObjectNotFound: (dte:String) [Get-Item], DriveNotFoundException
    • FullyQualifiedErrorId : DriveNotFound,Microsoft.PowerShell.Commands.GetItemCommand
get-item : Cannot find drive. A drive with the name 'dte' does not exist.
At C:\work\BitBucket\cbpomometro\packages\StudioShell.Provider.1.6.4.0\tools\StudioShell.Provider\InitializationScripts\register-solutionevents.ps1:50 char:28
  • $local:solutionFilePath = get-item dte:/solution;
  • ~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : ObjectNotFound: (dte:String) [Get-Item], DriveNotFoundException
    • FullyQualifiedErrorId : DriveNotFound,Microsoft.PowerShell.Commands.GetItemCommand
PM>
Coordinator
May 2 at 6:48 PM
For those of you having issues installing for VS2013, please see this beta release: http://studioshell.codeplex.com/releases/view/121609

It contains a fix for the installer for VS2013.