<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>studioshell Issue Tracker Rss Feed</title><link>http://studioshell.codeplex.com/workitem/list/basic</link><description>studioshell Issue Tracker Rss Description</description><item><title>Created Unassigned: Error upgrading the chocolatey package [62]</title><link>http://studioshell.codeplex.com/workitem/62</link><description>I was doing a cup all from UAC elevated command prompt.&lt;br /&gt;&lt;br /&gt;I got the following. I&amp;#39;ll try to troubleshoot some more this week.&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;Finished installing &amp;#39;skype&amp;#39; and dependencies - if errors not shown in console, none detected. Check log for errors if unsure.                                          &lt;br /&gt;Chocolatey &amp;#40;v0.9.8.20&amp;#41; is installing StudioShell and dependencies. By installing you accept the license for StudioShell and each dependency you are installing.        &lt;br /&gt;______ StudioShell v1.5.1.2 ______                                                                                                                                     &lt;br /&gt;Write-Error &amp;#58; studioshell did not finish successfully. Boo to the chocolatey gods&amp;#33;                                                                                     &lt;br /&gt;-----------------------                                                                                                                                                &lt;br /&gt;&amp;#91;ERROR&amp;#93; Cannot bind argument to parameter &amp;#39;Path&amp;#39; because it is null.                                                                                                   &lt;br /&gt;-----------------------                                                                                                                                                &lt;br /&gt;At C&amp;#58;&amp;#92;Chocolatey&amp;#92;chocolateyInstall&amp;#92;helpers&amp;#92;functions&amp;#92;Write-ChocolateyFailure.ps1&amp;#58;30 char&amp;#58;2                                                                             &lt;br /&gt;&amp;#43;     Write-Error &amp;#36;errorMessage                                                                                                                                        &lt;br /&gt;&amp;#43;     &amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;                                                                                                                                        &lt;br /&gt;    &amp;#43; CategoryInfo          &amp;#58; NotSpecified&amp;#58; &amp;#40;&amp;#58;&amp;#41; &amp;#91;Write-Error&amp;#93;, WriteErrorException                                                                                     &lt;br /&gt;    &amp;#43; FullyQualifiedErrorId &amp;#58; Microsoft.PowerShell.Commands.WriteErrorException,Write-Error                                                                            &lt;br /&gt;                                                                                                                                                                       &lt;br /&gt;Join-Path &amp;#58; Cannot bind argument to parameter &amp;#39;Path&amp;#39; because it is null.                                                                                               &lt;br /&gt;At C&amp;#58;&amp;#92;Chocolatey&amp;#92;lib&amp;#92;StudioShell.1.5.1.2&amp;#92;tools&amp;#92;chocolateyInstall.ps1&amp;#58;34 char&amp;#58;28                                                                                        &lt;br /&gt;&amp;#43;     &amp;#36;settingsSpec &amp;#61; join-path &amp;#36;addInInstallPath -child &amp;#34;UserProfile&amp;#47;settings.txt&amp;#34;&amp;#59;                                                                                   &lt;br /&gt;&amp;#43;                               &amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;&amp;#126;                                                                                                                      &lt;br /&gt;    &amp;#43; CategoryInfo          &amp;#58; InvalidData&amp;#58; &amp;#40;&amp;#58;&amp;#41; &amp;#91;Join-Path&amp;#93;, ParentContainsErrorRecordException                                                                         &lt;br /&gt;    &amp;#43; FullyQualifiedErrorId &amp;#58; ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand                                             &lt;br /&gt;                                                                                                                                                                       &lt;br /&gt;                                                                                                                                                                       &lt;br /&gt;                                                                                                                                                                       &lt;br /&gt;Press Enter or Esc to close console...                                                                                                                                 &lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;</description><author>zippy1981</author><pubDate>Sun, 09 Jun 2013 22:01:28 GMT</pubDate><guid isPermaLink="false">Created Unassigned: Error upgrading the chocolatey package [62] 20130609100128P</guid></item><item><title>Commented Issue: Variable names don't autocomplete [60]</title><link>http://studioshell.codeplex.com/workitem/60</link><description>Subject says all &amp;#36;psver&amp;#43;TAB doesn&amp;#39;t work, but &amp;#36;psversiontable&amp;#43;Enter returns something. Also applies to variables I define myself.&lt;br /&gt;Comments: I tested on VS2010 and V2012, win8&amp;#43;PS3&amp;#10;&amp;#10;What modules do you have installed&amp;#63;</description><author>beefarino</author><pubDate>Sat, 08 Jun 2013 02:47:49 GMT</pubDate><guid isPermaLink="false">Commented Issue: Variable names don't autocomplete [60] 20130608024749A</guid></item><item><title>Commented Issue: Variable names don't autocomplete [60]</title><link>http://studioshell.codeplex.com/workitem/60</link><description>Subject says all &amp;#36;psver&amp;#43;TAB doesn&amp;#39;t work, but &amp;#36;psversiontable&amp;#43;Enter returns something. Also applies to variables I define myself.&lt;br /&gt;Comments: I waited 3&amp;#43; minutes on Windows 7 &amp;#43; PS v3 &amp;#43; Visual Studio 2012 and it didn&amp;#39;t work.&amp;#10;&amp;#10;I&amp;#39;ll try windows 8 later What particular VS version did you test on&amp;#63;</description><author>zippy1981</author><pubDate>Fri, 07 Jun 2013 09:12:58 GMT</pubDate><guid isPermaLink="false">Commented Issue: Variable names don't autocomplete [60] 20130607091258A</guid></item><item><title>Commented Issue: Ctrl-C closes Visual Studio [35]</title><link>http://studioshell.codeplex.com/workitem/35</link><description>When I press Ctrl-C, Visual Studio is immediately closed. Does not seem to happen after closing &amp;#40;using exit&amp;#41; and re-opening the StudioShell console, but then Ctrl-C does not work at all.&lt;br /&gt;Comments: Is this issue still active for you&amp;#63;  I have not been able to replicate this behavior &amp;#40;nor has anyone else I&amp;#39;ve asked&amp;#41;...</description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 23:37:15 GMT</pubDate><guid isPermaLink="false">Commented Issue: Ctrl-C closes Visual Studio [35] 20130606113715P</guid></item><item><title>Closed Issue: Studio Shell 1.2 (SSMS) - SSMS Application Crashed when exiting 'Old School' console. [30]</title><link>http://studioshell.codeplex.com/workitem/30</link><description>I got surpised that you close this issue.  So, the feedback is&amp;#58; I would suggest to remove the &amp;#34;Old School&amp;#34; option until you figured out that it can be fix.  StudioShell is pretty stable without it, and should be enough for a DBA and&amp;#47;or SQL Developer to work with it.  I got my issue resolved with my Start-Demo function, and I looking forward to us it next week.  &lt;br /&gt;&lt;br /&gt;I go it installed in SSMS 2012 RC0,and I&amp;#39;m loving it&amp;#33;&amp;#33; I have to admit this application does have potential.&lt;br /&gt;&lt;br /&gt;Thanks,&lt;br /&gt;Max&lt;br /&gt;Comments: The old school console remains as a &amp;#34;use at your own risk&amp;#34; feature.  </description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 23:35:40 GMT</pubDate><guid isPermaLink="false">Closed Issue: Studio Shell 1.2 (SSMS) - SSMS Application Crashed when exiting 'Old School' console. [30] 20130606113540P</guid></item><item><title>Edited Issue: Running an interactive cmd.exe shell from inside StudioShell breaks StudioShell [34]</title><link>http://studioshell.codeplex.com/workitem/34</link><description>If I type cmd.exe in StudioShell I don&amp;#39;t get a cmd prompt. I can&amp;#39;t kill it, even via a pipeline reset or killing the cmd.exe instance from task manager. Couple this with Work item 32, and I have to restart Visual Studio&lt;br /&gt;</description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 23:34:19 GMT</pubDate><guid isPermaLink="false">Edited Issue: Running an interactive cmd.exe shell from inside StudioShell breaks StudioShell [34] 20130606113419P</guid></item><item><title>Closed Issue: Running an interactive cmd.exe shell from inside StudioShell breaks StudioShell [34]</title><link>http://studioshell.codeplex.com/workitem/34</link><description>If I type cmd.exe in StudioShell I don&amp;#39;t get a cmd prompt. I can&amp;#39;t kill it, even via a pipeline reset or killing the cmd.exe instance from task manager. Couple this with Work item 32, and I have to restart Visual Studio&lt;br /&gt;Comments: This should be covered in the blacklisting feature of 1.5.1</description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 23:34:19 GMT</pubDate><guid isPermaLink="false">Closed Issue: Running an interactive cmd.exe shell from inside StudioShell breaks StudioShell [34] 20130606113419P</guid></item><item><title>Commented Issue: DTE PSdrive and $dte variable not available [46]</title><link>http://studioshell.codeplex.com/workitem/46</link><description>I have isntalled StudioShell 1.5.0.1 on win8 &amp;#43; VS2012.&lt;br /&gt;I have set the execution policy to RemoteSigned and I&amp;#39;m running VS as admnistrator.&lt;br /&gt;I having an issue accesing the &amp;#36;dte variable and the DTE PSDrive. &lt;br /&gt;They are not available, &amp;#36;dte is empty and the PSDRIVE is not listed &amp;#40;No PSPRovider as well&amp;#41;&lt;br /&gt;I tried to install it on a win7 &amp;#43; VS2012 and vs2010.&lt;br /&gt;I ahve access to DTE and &amp;#36;dte on VS2010 but not on VS2012.&lt;br /&gt;&lt;br /&gt;Anyone else has the same issue&amp;#63;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Comments: The 1.5.1 release is much more stable with regards to the nuget install.  Please give it a shot and let me know if I can close this issue.</description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 23:32:47 GMT</pubDate><guid isPermaLink="false">Commented Issue: DTE PSdrive and $dte variable not available [46] 20130606113247P</guid></item><item><title>Commented Feature: Make the NuGet package install with Chocolatey [41]</title><link>http://studioshell.codeplex.com/workitem/41</link><description>It took me a while to realize the reason why cinst StudioShell was not working was that this was actually a vanilla nuget package. It should also have a tools&amp;#92;chocolateyInstall.ps1&lt;br /&gt;Comments: feature added in changeset 2d3ecc54157e</description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 23:31:17 GMT</pubDate><guid isPermaLink="false">Commented Feature: Make the NuGet package install with Chocolatey [41] 20130606113117P</guid></item><item><title>Edited Feature: Make the NuGet package install with Chocolatey [41]</title><link>http://studioshell.codeplex.com/workitem/41</link><description>It took me a while to realize the reason why cinst StudioShell was not working was that this was actually a vanilla nuget package. It should also have a tools&amp;#92;chocolateyInstall.ps1&lt;br /&gt;</description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 23:31:17 GMT</pubDate><guid isPermaLink="false">Edited Feature: Make the NuGet package install with Chocolatey [41] 20130606113117P</guid></item><item><title>Edited Issue: Autocomplete should un-highlight after it fails to match [59]</title><link>http://studioshell.codeplex.com/workitem/59</link><description>When you invoke autocomplete with a tab it highlights what it is auto completing. As a visual clue that autocomplete has finished with a failure, the highlighting should be removed.&lt;br /&gt;</description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 23:22:58 GMT</pubDate><guid isPermaLink="false">Edited Issue: Autocomplete should un-highlight after it fails to match [59] 20130606112258P</guid></item><item><title>Commented Issue: Autocomplete should un-highlight after it fails to match [59]</title><link>http://studioshell.codeplex.com/workitem/59</link><description>When you invoke autocomplete with a tab it highlights what it is auto completing. As a visual clue that autocomplete has finished with a failure, the highlighting should be removed.&lt;br /&gt;Comments: fixed in changeset 8ceae56276a1.</description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 23:22:20 GMT</pubDate><guid isPermaLink="false">Commented Issue: Autocomplete should un-highlight after it fails to match [59] 20130606112220P</guid></item><item><title>Commented Issue: Autocomplete should un-highlight after it fails to match [59]</title><link>http://studioshell.codeplex.com/workitem/59</link><description>When you invoke autocomplete with a tab it highlights what it is auto completing. As a visual clue that autocomplete has finished with a failure, the highlighting should be removed.&lt;br /&gt;Comments: Confirmed.  Added to 1.6 release plan</description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 22:53:36 GMT</pubDate><guid isPermaLink="false">Commented Issue: Autocomplete should un-highlight after it fails to match [59] 20130606105336P</guid></item><item><title>Edited Issue: Autocomplete should un-highlight after it fails to match [59]</title><link>http://studioshell.codeplex.com/workitem/59</link><description>When you invoke autocomplete with a tab it highlights what it is auto completing. As a visual clue that autocomplete has finished with a failure, the highlighting should be removed.&lt;br /&gt;</description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 22:53:35 GMT</pubDate><guid isPermaLink="false">Edited Issue: Autocomplete should un-highlight after it fails to match [59] 20130606105335P</guid></item><item><title>Commented Issue: Variable names don't autocomplete [60]</title><link>http://studioshell.codeplex.com/workitem/60</link><description>Subject says all &amp;#36;psver&amp;#43;TAB doesn&amp;#39;t work, but &amp;#36;psversiontable&amp;#43;Enter returns something. Also applies to variables I define myself.&lt;br /&gt;Comments: I&amp;#39;m trying to replicate this on my win8 box with PS3, but variable completion works.  One thing to note about V3 is that the autoloading &amp;#34;feature&amp;#34; causes a big slowdown in completion, especially at startup.&amp;#10;&amp;#10;Can you try typing &amp;#36;ps &amp;#43; TAB and then leave it for a few minutes&amp;#63;  I know I know, but give it a shot and let me know...</description><author>beefarino</author><pubDate>Thu, 06 Jun 2013 22:44:54 GMT</pubDate><guid isPermaLink="false">Commented Issue: Variable names don't autocomplete [60] 20130606104454P</guid></item><item><title>Edited Feature: Add an option to start StudioShell on Visual Studio Startup [58]</title><link>http://studioshell.codeplex.com/workitem/58</link><description>It takes a while to start StudioShell. It would be preferable if I could chose to make that happen at Visual Studio Startup.&lt;br /&gt;</description><author>beefarino</author><pubDate>Sat, 01 Jun 2013 13:19:34 GMT</pubDate><guid isPermaLink="false">Edited Feature: Add an option to start StudioShell on Visual Studio Startup [58] 20130601011934P</guid></item><item><title>Commented Feature: Add an option to start StudioShell on Visual Studio Startup [58]</title><link>http://studioshell.codeplex.com/workitem/58</link><description>It takes a while to start StudioShell. It would be preferable if I could chose to make that happen at Visual Studio Startup.&lt;br /&gt;Comments: Just pushed changeset 51ec9b2f5c91 with this added feature.  Will fold into the next release cycle.</description><author>beefarino</author><pubDate>Sat, 01 Jun 2013 13:19:34 GMT</pubDate><guid isPermaLink="false">Commented Feature: Add an option to start StudioShell on Visual Studio Startup [58] 20130601011934P</guid></item><item><title>Closed Unassigned: Plugin does not load on visual studio 2008 [61]</title><link>http://studioshell.codeplex.com/workitem/61</link><description>Verified on two separate machines. One has a working Visual Studip 2008 install with ReSharper. The other  is a Spartan WIndows 8 VM. Let me know if there are logs anywhere or if you&amp;#39;d just like me to launch devenv.exe from a debugger to test some more.&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;---------------------------&lt;br /&gt;Microsoft Visual Studio&lt;br /&gt;---------------------------&lt;br /&gt;The Add-in &amp;#39;StudioShell&amp;#39; failed to load or caused an exception.&lt;br /&gt;Would you like to remove this Add-in&amp;#63;&lt;br /&gt;If you choose yes, the file it was loaded from, &amp;#39;C&amp;#58;&amp;#92;Program Files &amp;#40;x86&amp;#41;&amp;#92;Code Owls LLC&amp;#92;StudioShell&amp;#92;bin&amp;#92;StudioShell.VS2008.AddIn&amp;#39;, will be renamed.&lt;br /&gt;&lt;br /&gt;Error Message&amp;#58; &amp;#60;Unknown Error&amp;#62;&lt;br /&gt;Error number&amp;#58; 8013101b&lt;br /&gt;---------------------------&lt;br /&gt;Yes   No   &lt;br /&gt;---------------------------&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;Comments: &amp;#34;WOMM&amp;#34;</description><author>beefarino</author><pubDate>Sat, 01 Jun 2013 12:04:34 GMT</pubDate><guid isPermaLink="false">Closed Unassigned: Plugin does not load on visual studio 2008 [61] 20130601120434P</guid></item><item><title>Commented Unassigned: Plugin does not load on visual studio 2008 [61]</title><link>http://studioshell.codeplex.com/workitem/61</link><description>Verified on two separate machines. One has a working Visual Studip 2008 install with ReSharper. The other  is a Spartan WIndows 8 VM. Let me know if there are logs anywhere or if you&amp;#39;d just like me to launch devenv.exe from a debugger to test some more.&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;---------------------------&lt;br /&gt;Microsoft Visual Studio&lt;br /&gt;---------------------------&lt;br /&gt;The Add-in &amp;#39;StudioShell&amp;#39; failed to load or caused an exception.&lt;br /&gt;Would you like to remove this Add-in&amp;#63;&lt;br /&gt;If you choose yes, the file it was loaded from, &amp;#39;C&amp;#58;&amp;#92;Program Files &amp;#40;x86&amp;#41;&amp;#92;Code Owls LLC&amp;#92;StudioShell&amp;#92;bin&amp;#92;StudioShell.VS2008.AddIn&amp;#39;, will be renamed.&lt;br /&gt;&lt;br /&gt;Error Message&amp;#58; &amp;#60;Unknown Error&amp;#62;&lt;br /&gt;Error number&amp;#58; 8013101b&lt;br /&gt;---------------------------&lt;br /&gt;Yes   No   &lt;br /&gt;---------------------------&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;Comments: &amp;#33;&amp;#91;Works On My Machine&amp;#93;&amp;#40;http&amp;#58;&amp;#47;&amp;#47;codinghorror.typepad.com&amp;#47;.a&amp;#47;6a0120a85dcdae970b0128776ff992970c-pi&amp;#41;&amp;#10;&amp;#10;Tested. Please close&amp;#33;</description><author>zippy1981</author><pubDate>Sat, 01 Jun 2013 02:30:38 GMT</pubDate><guid isPermaLink="false">Commented Unassigned: Plugin does not load on visual studio 2008 [61] 20130601023038A</guid></item><item><title>Edited Issue: open-solution does not update the recent solutions or jump list [57]</title><link>http://studioshell.codeplex.com/workitem/57</link><description>If I open a solution  I expect the jump lists and recent solutions to be updated. I find it really weird its possible to open a solution without the jump list being updated.&lt;br /&gt;</description><author>beefarino</author><pubDate>Fri, 31 May 2013 23:24:33 GMT</pubDate><guid isPermaLink="false">Edited Issue: open-solution does not update the recent solutions or jump list [57] 20130531112433P</guid></item></channel></rss>