Packaging components

Package properties

.nuspec

Components that are solely declarative assets do not have any code associated with them, so you have to generate a .nuspec file to package it for NuGet. Create a NuSpec file with the following properties.

<?xml version="1.0"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
    <metadata>
        <id><!--Namespace and component name --></id>
        <version><!-- Version number --></version>
        <authors>Microsoft</authors>
        <owners>Microsoft</owners>
        <releaseNotes><!-- Release notes related to the current version--></releaseNotes>
        <description><!-- A description of the package for UI display --></description>
        <tags>bf-component preview</tags>
        <dependencies />
    </metadata>

    <files>
        <file src="exported\**\*.*" target="exported" />
    </files>
</package>

.csproj

If the component has a .csproj file, add the following property group.

  <PropertyGroup>
    <PackageId><!--Namespace and component name --></PackageId>
    <PackageVersion><!-- Version number --></PackageVersion>
    <Description><!-- A description of the package for UI display --></Description>
    <Summary><!-- A short description of the package for UI display. If omitted, a truncated version of description is used. --></Summary>
    <Company>Microsoft</Company>
    <Authors>Microsoft</Authors>
    <Product>Microsoft Bot Builder SDK</Product>
    <Copyright>© Microsoft Corporation. All rights reserved.</Copyright>
  </PropertyGroup>

package.json