CS-Script Tools (VS2012-15)


CS-Script tools for VS2012-15

(2) Review
Visual Studio
2015, 2013, 2012
Download (4,648)
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Reviews (2)
Q and A (4)
Sign in to write a review
Sort by:

by George I. Birbilis | March 24 2015

this version isn't listed at http://www.csscript.net/CSScriptVSX.html (only VS2010 version is listed there)

Oleg Shilo March 24 2015
| Edit |

Txs. Fixed.

by Dzmuh | February 01 2013

Sign in to start a discussion

  • Missing framework for Visual Studio 2013
    3 Posts | Last post November 09, 2015
    • Hi 
      When I try install I get a message about a missing framework in Visual Studio 2013 as follows:
      04/11/2015 11:10:01 - The following target products have been selected...
      04/11/2015 11:10:01 - 	Microsoft Visual Studio Professional 2013
      04/11/2015 11:10:01 - 
      04/11/2015 11:10:02 - Beginning to install extension to Microsoft Visual Studio Professional 2013...
      04/11/2015 11:10:02 - Install Error : Microsoft.VisualStudio.ExtensionManager.MissingTargetFrameworkException: The extension 'CS-Script Tools (VS2012-15)' requires a version of the .NET Framework that is not installed.
         at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.CheckForValidDotNetFramework(IExtension extension)
    • It is a bit strange as the extension is built against .NET v4.5, which is installed with VS2013.
      I just installed it on my copy of VS2013 and it is OK. Though in my case I had VS2015 installed as well. 
      I will need to re-test it on the PC with VS2013 only. Will let you know the outcome.
    • I managed to reproduce the problem. Indeed the extension fails to be installed on the PC with VS2013 only (at least on Win10). 
      I found that having the .NET dependency set to v4.5 in the manifest file triggers this behavior. This is extremely strange as .NET v4.5 is a part of the VS2013 deployment. The extension itself is built in VS2013. And yet it fails to install on the very same system that it has been just built on. 
      I can only blame the fact that it was built on Win10 with .NET v4.6 present. Possibly the compiler accidentally injected the wrong dependency. BTW I found that all my extensions on VS Gallery are affected.
      I also found that lowering .NET version in the manifest file tricks the extension manager and the extension seems to install and work as expected. 
      Can you do me a favor? Can you please install my simplest VS2013-2015 extension with the fix and see if the fix works: https://movetypetofilevsx.codeplex.com/releases/view/618353. 
      If it does I will extend the fix for the all extensions in the gallery. 
      Thank you.
  • Doesn't work for me
    3 Posts | Last post August 30, 2015
    • Hello, I tried installing this extension but was unable to get it working. I can see the "CS-Script tools" icon in my menu, but when I click it it doesn't do anything (I clicked not to show error messages anymore by mistake) and in ActivityLog.xml I can see this:
          <time>2015/08/29 16:48:06.201</time>
          <description>Begin package load [CSScriptPackage]</description>
          <time>2015/08/29 16:48:06.201</time>
          <description>CreateInstance failed for package [CSScriptPackage]</description>
          <errorinfo>Could not load Microsoft.VisualStudio.Shell.11.0, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a or one of its dependencies. System couldn't find the file.</errorinfo>
          <time>2015/08/29 16:48:06.201</time>
          <description>End package load [CSScriptPackage]</description>
          <hr>80004005 - E_FAIL</hr>
          <errorinfo>Could not load Microsoft.VisualStudio.Shell.11.0, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a or one of its dependencies. System couldn't find the file.</errorinfo>
      (BTW: sorry, but the error messages aren't exact, because I had to translate them since they weren't in English).
      Any idea how to resolve this? Thanks.
      I am using VS 2013 community edition on 64bit windows 8.
    • Most likely it si a dependency problem that is similar to the one that I had to fix recently for MoveTypeToFile extension.
      I just applied the same fix to the CS-Script extension and rebuilt. Can you do me a favor and test if it works for you. The build is here:  
    • Yes, this one works. Thank you very much :-)
  • VS 2015 Support?
    1 Posts | Last post July 06, 2015
    • When can we expect VS 2015 support?
  • Shell Extension Script
    2 Posts | Last post December 14, 2012
    • Has anybody cooked up a script to open .cs files in debug mode in VS2012 via the shell extension? The built-in equivalent script for VS2010 appears to be debugVS10.0.cs.
    • I am sorry for the delay but the new CS-Script release with the full VS2012 support is practically ready. There is a small issue to resolve with the shell extensions on Windows 8 and it is the only reason for the delay with publishing the release. However if you wish you can get it from the private repository: https://dl.dropbox.com/u/2192462/CS-S/cs-script.3.4.0.zip.