Be the first to post a text review of .NET Shell. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• A little documentation

  I have been submitting short articles under the documentation tab, and will continue to do so until I can get a full project site together. So let me know if there is something in particular you would like explained... - Jeremy

  posted by jeremycowles 964 days ago

• Alpha 1 Available

  The Good ----------------- Here it is, Alpha 1, dings-and-dents edition. The Bad ----------------- I actually finished the alpha 1 code about 2 months ago, I just didn't want to release it without documentation and a walk through. However, school, work and planning a wedding are dominating my life, so I figured something is better than nothing. Feel free e-mail me if you have any questions, ideas or if you write a cool script you want added. The Very Ugly ----------------- Two major known issues: 1) "plumbing" does not work yet (it's coming) 2) There is a memory leak, well, kind of. Every time you run a script, it gets compiled into an assembly and loaded into memory; currently they don't get unloaded when the script terminates. Hooray! - Jeremy

  posted by jeremycowles 966 days ago

• File released: /nsh/Alpha 1/NSH-Alpha1-Source.zip

  posted 966 days ago

• File released: /nsh/Alpha 1/NSH-Alpha1-Bin.zip

  posted 966 days ago

• nsh Alpha 1 file released: NSH-Alpha1-Source.zip

  posted 966 days ago

• nsh Alpha 1 file released: NSH-Alpha1-Bin.zip

  posted 966 days ago

• Finals vs. Alpha

  Finals are this week, so I hope next weekend (12/9) will bring enough spare time to finish the alpha release of NSH. The main issue that needs to be addressed before alpha is the ability to add references into scripts. Currently, the only objects available in scripts are the most common System.XXX namespaces. I would like to give the developer the ability of adding additional .NET references, or references to custom assemblies. The other lingering issue is the way scripts are declared. Currently, any file with a .vb extension (or .vb.s) will be executed as a script. Like any .NET application, scripts must have an entry point. This is automatically created for short scripts (.vb.s), however for full scripts (.vb) the entry point is specified as a comment on the first line of the script, much like a bash script: '# NshScripts.Dev.TypeExplorer,Main Namespace NshScripts.Dev Public Class TypeExplorer ... End Class End Namespace The first line tells the script engine to load the object "NshScripts.Dev.TypeExplorer" and execute the "Main()" function via reflection. Although this method works fine, it seems a bit awkward. One alternate possibility is a <script> attribute: Namespace NshScripts.Dev <Nsh.Script> _ Public Class TypeExplorer ... End Class End Namespace The <Nsh.Script> attribute will flag the class as a script, and then execute the Main() function (entry point will not be variable). Another possibility would be via Inheritance / Interface combo: Namespace NshScripts.Dev Public Class TypeExplorer : Inherits Nsh.ScriptBase ... End Class End Namespace Namespace NshScripts.Dev Public Class TypeExplorer Implements Nsh.IScript ... End Class End Namespace The script developer could either choose to directly inherit from the Script class or implement the IScript interface manually. The inheritance / interface option is slightly more attractive since additional functionality could be provided to the script developer via the base class. The good news is that the profile system is complete, along with environment variables & aliases. I have moved much of the core functionality out of the NSH assembly and into individual scripts which are bound to commands as aliases. For example, here is the file operations bindings from the default profile (Nsh.Profile.vb): host.Aliases.Add("mv", GetScriptPath("core\mv.vb")) host.Aliases.Add("move", GetScriptPath("core\mv.vb")) host.Aliases.Add("cp", GetScriptPath("core\cp.vb")) host.Aliases.Add("copy", GetScriptPath("core\cp.vb")) host.Aliases.Add("touch", GetScriptPath("core\touch.vb")) host.Aliases.Add("del", GetScriptPath("core\del.vb"))

  posted by jeremycowles 1077 days ago

• .NET Shell Project Created

  The .NET Shell (NSH) project has been created on Source Forge! I'm working feverously on an official alpha release, so if you've stumbled across the project, please be patient and come back soon! - Jeremy

  posted by jeremycowles 1125 days ago

• Code committed

  Anonymous committed patchset 1 of module CVSROOT to the .NET Shell CVS repository, changing 11 files

  posted by nobody 1138 days ago

• Forum thread added

  Anonymous created the Welcome to Developers forum thread

  posted by nobody 1138 days ago