Prep for 0.2.0 release

Author: daveaglick

Readme.md

@@ -4,7 +4,7 @@ Tools to let you use Roslyn-powered C# scripts for code generation. You can thin
 
 ## Quick Start
 
-The easiest way to get up and running is to install the `Scripty.MsBuild` NuGet package into an existing project (it's currently pre-release so you'll have to specify to allow pre-release packages). Then just create a script file with a `.csx` extension, add it to your project, and watch the magic happen on your next build.
+The easiest way to get up and running is to install the `Scripty.MsBuild` NuGet package into an existing project. Then just create a script file with a `.csx` extension, add it to your project, and watch the magic happen on your next build. Alternativly, you can install the Scripty Visual Studio extension to add custom tool support for code generation outside the build process.
 
 ## Scripts
 
@@ -102,10 +102,12 @@ By default, all files in the project with the `.csx` extension are evaluated. Yo
 
 Files that get generated using the MsBuild task are included during compilation (as long as their `Compile` flag is set in the script), but not in the project (unless your script modifies the project to include them). If you'd like to have them in the project as well (for example, to enable Intellisense) just include them manually after the first generation. You may want to also commit an empty placeholder file to any shared repository if you do include generated files in the project so that people obtaining the project won't get a missing file prior to their first build.
 
-### Scripty.CustomTool (Planned)
+### Scripty.CustomTool
 
 This library provides a single file generator (otherwise known as a custom tool) in Visual Studio that can be used to evaluate Scripty scripts whenever the underlying script file changes. Unlike `Scripty.MsBuild`, generated output from the scripts will get automatically included in the project. This library and `Scripty.MsBuild` can be used together to provide script evaluation on changes *and* on build.
 
+The generator is provided as a Visual Studio extension and you can install it from the gallery (just search for "Scripty"). To use it, set the "Custom Tool" property for any `.csx` file to "ScriptyGenerator". After setting the custom tool. Scripty will automatically run whenever the underlying script is saved or when you right-click the script and select "Run Custom Tool."
+
 ### Scripty
 
 A console application that can evaluate Scripty scripts. This can be used to integrate Scripty into alternate build systems. It's also used by Scripty.MsBuild to evaluate scripts outside the process space of the currently running build.

ReleaseNotes.md

@@ -1,3 +1,7 @@
+# 0.2.0
+
+- Added a Visual Studio single file generator (a.k.a "custom tool")
+
 # 0.1.0
 
 - Initial public release!

build.cake

@@ -4,9 +4,11 @@
 
 // Publishing workflow:
 // - Update ReleaseNotes.md
+// - Update the version in Scripty.CustomTool/source.extension.vsixmanifest
 // - Run a normal build with Cake to set SolutionInfo.cs in the repo ("build.cmd")
 // - Run a Publish build with Cake ("build.cmd --target Publish")
 // - No need to add a version tag to the repo - added by GitHub on publish
+// - Manually upload the .vsix in src\artifacts to the Visual Studio Gallery
 
 #addin "Cake.FileHelpers"
 #addin "Octokit"
@@ -31,7 +33,7 @@ var buildNumber = AppVeyor.Environment.Build.Number;
 var releaseNotes = ParseReleaseNotes("./ReleaseNotes.md");
 
 var version = releaseNotes.Version.ToString();
-var semVersion = version + (isLocal ? "-beta" : string.Concat("-build-", buildNumber));
+var semVersion = version + (isLocal ? string.Empty : string.Concat("-build-", buildNumber));
 
 var buildDir = Directory("./src/Scripty/bin") + Directory(configuration);
 var buildResultDir = Directory("./build") + Directory(semVersion);
@@ -87,6 +89,7 @@ Task("Build")
         MSBuild("./src/Scripty.sln", new MSBuildSettings()
             .SetConfiguration(configuration)
             .SetVerbosity(Verbosity.Minimal)
+            .SetMSBuildPlatform(MSBuildPlatform.x86)
         );
     });
 

src/Scripty.CustomTool/source.extension.vsixmanifest

@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="utf-8"?>
 <PackageManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011" xmlns:d="http://schemas.microsoft.com/developer/vsx-schema-design/2011">
   <Metadata>
-    <Identity Id="Scripty.CustomTool" Version="1.0.0.0" Language="en-US" Publisher="Dave Glick" />
+    <Identity Id="Scripty.CustomTool" Version="0.2.0.0" Language="en-US" Publisher="Dave Glick" />
     <DisplayName>Scripty</DisplayName>
     <Description xml:space="preserve">Runs Scripty as a custom tool.</Description>
     <MoreInfo>https://github.com/daveaglick/Scripty</MoreInfo>

src/SolutionInfo.cs

@@ -6,8 +6,8 @@
 using System.Reflection;
 
 [assembly: AssemblyProduct("Scripty")]
-[assembly: AssemblyVersion("0.1.0")]
-[assembly: AssemblyFileVersion("0.1.0")]
-[assembly: AssemblyInformationalVersion("0.1.0-beta")]
-[assembly: AssemblyCopyright("Copyright © Dave Glick")]
+[assembly: AssemblyVersion("0.2.0")]
+[assembly: AssemblyFileVersion("0.2.0")]
+[assembly: AssemblyInformationalVersion("0.2.0")]
+[assembly: AssemblyCopyright("Copyright © Scripty Contributors")]
 

src/artifacts/.gitignore

@@ -0,0 +1 @@
+*.vsix