Helps to setup Appveyor for continuous integration and to publish your NuGet.

Why should I use this template?

• Contains well documented instructions about the setup process.
• Contains scripts for building your project, auto incrementing version and publishing your created NuGet to private and/or public hosting server.
• After setup is done you get:
  • the state of your build.
  • automatically published NuGet packages.
  • possibility to automate test runs before each build and much more.

1. Create “Class Library” in Visual Studio and add the code you want to be in your library.

2. Copy the following from Template folder to root folder of your project:

• Folder: "Scripts"
• Files: ”.gitignore”, “appveyor.yml” , “LICENCE”, “README.md”

3. Create new empty repository on github. Note repository’s URL for the next couple steps.

4. Create YourProjectName.nuspec file in the root folder and add the following:

<?xml version="1.0"?>
<package>
    <metadata>
        <!-- The unique identifier for the package. This is the package name that is shown when packages are listed using the Package Manager Console. These are also used when installing a package using the Install-Package command within the Package Manager Console. Package IDs may not contain any spaces or characters that are invalid in an URL. In general, they follow the same rules as .NET namespaces do. So Foo.Bar is a valid ID, Foo! and Foo Bar are not. -->
        <id>ProjectName</id>
        <version></version>
        <title>Project Name</title>
        <authors>First name Last name</authors>
        <owners>Intergen Ltd</owners>
        <licenseUrl>http://www.apache.org/licenses/LICENSE-2.0</licenseUrl>
        <projectUrl>GitHubURL</projectUrl>
        <iconUrl>https://avatars2.githubusercontent.com/u/17167744</iconUrl>
        <requireLicenseAcceptance>false</requireLicenseAcceptance>
        <description>Description</description>
        <releaseNotes>Notes</releaseNotes>
        <copyright>Copyright 2016</copyright>
        <tags>Tag Tag2</tags>
        <dependencies>
            <dependency id="DependencyProjectName" version="1.0.0.0" />
        </dependencies> 
    </metadata>
    <files>
        <file src="ProjectName\bin\Release\ProjectName.dll" target="lib" /> 
        <file src="ProjectName\bin\Release\ProjectName.pdb" target="lib" /> 
    </files>
</package>

5. Replace information in tags with project specific one.

• Add dependencies if your project requires them, otherwise comment out dependency tag. You can find dependencies in “packages.config”.
• Make sure to read Licence file and sign it at the end (line 189) or pick a licence that suits your needs.
• Intergen use: Do not modify Owners, LicenseUrl, IconUrl, Copyright. Licence is already signed.

6. Follow these GitHub Instructions to push local repository to git repository or execute the following commands:

git init
git add .
git commit -m "Created project"
git remote add origin YourGithubURL
git push origin master

7. Login in AppVeyor with GitHub credentials. (allow it to access your repositories)

8. Add Repository to AppVeyor.

9. Using AppVeyor's encryption tool encrypt all your private variables in your appveyor.yml file. Also set public variables and set your solution file name in build section.

10. Push updated files to repository and that should start a new build.

11. If everything has been setup correctly your build succeeds and your NuGet gets published. Congratulations!

Note: If your build fails look through the generated log file. Usually errors are self-explanatory.

Victor Usoltsev, 2016