This tutorial will show you how to include your non-compilable items into a nuget package (nupkg). This steps apply to any type of file.

DISCLAIMER: You must have a nuspec file and a targets file. If you don’t have one yet, download one from somewhere and change the metadata accordingly.

Let’s start!

1. Open up your solution in Visual Studio
2. Open your solution’s nuspec file and look for <files> tag
3. You need to reference all folders and all files that you want to include in your nuget. Example below:

<files>
    <file src="lib\net452\your_compiled_assembly.dll" target="lib\net452" />
    <file src="Your_Folder\*.pp" target="content\Your_Folder"/>
    <file src="Your_Folder\Your_Sub_Folder\*.*" target="content" />
    <file src="*.xdt" target="content" />
 </files>

4.  After you added all files into nuspec config, now you can open your targets file. Don’t forget to import targets into your csproj file like the example below

<Import Project="your_targets_file.targets" Condition="Exists('your_targets_file.targets')" />

5. Now to targets file, you must index ALL files that you want to add to your nuget. This step is very important

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="14.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
 <TargetName="CreatePackage">
   <PropertyGroup>
   <Configuration>Release</Configuration>
   <PackageSource>bin\$(Configuration)\Package</PackageSource>
   <NuSpecPath>$(MSBuildProjectName).nuspec</NuSpecPath>
   </PropertyGroup>
   <RemoveDirDirectories="$(PackageSource)"/>
   <MSBuildProjects="$(MSBuildProjectFullPath)" Targets="Rebuild"Properties=" TargetFrameworkVersion=v4.0; OutputPath=bin\$(Configuration)\net40;Configuration=$(Configuration)" BuildInParallel="$(BuildInParallel)"/>


   <Copy SourceFiles="bin\$(Configuration)\net40\$(AssemblyName).dll" DestinationFolder="$(PackageSource)\lib\net40"/>
   <Copy SourceFiles="$(NuSpecPath)" DestinationFolder="$(PackageSource)"/>
   <Copy SourceFiles="Your_Folder\Your_Class_File.cs.pp" DestinationFolder="$(PackageSource)\Your_Folder"/>
   <Copy SourceFiles="Your_Folder\Yet_Another_Class.cs.pp" DestinationFolder="$(PackageSource)\Your_Folder"/>
   <Copy SourceFiles="Your_Folder\Your_Sub_Folder\A_Class.cs.pp" DestinationFolder="$(PackageSource)\Your_Folder\Your_Sub_Folder"/>
   <Copy SourceFiles="Your_Images_Folder\Your_Image.jpeg" DestinationFolder="$(PackageSource)\Your_Images_Folder"/>
   <Copy SourceFiles="Your_root_file.xml" DestinationFolder="$(PackageSource)"/>
 </Target>
</Project>

6. After you added all your source files into your targets file, you are ready to pack it!!

File extensions for Transformations and generated classes:

1. A pp file extension is a class that’s generated when a nuget is installed in any solution. Usually, the class namespace is replaced by “$rootnamespace$” (without quotes) and the extension is added (yourclass.cs.pp)
2. A xdt file extension is a XML Transformation procedure.

Example of a *.pp class ready to be packed into a nuget:

namespace $rootnamespace$.App_Start
{
 using System;
 using System.Collections.Generic;
 using System.Configuration;
 using System.Linq;
...
}

That’s all folks!

The post How to add your custom content files into a nuget package (for Visual Studio) appeared first on Blog IT.

Pic1. Exception: “Could not enlist Send Port – HRESULT: 0xC00CE557”

So, after some debugging, me and my teammate noticed an issue with some port filters inside a WCF Custom Send Port in the bindings XML, originally exported by BizTalk. Time to check the XML now!

Here’s how you can trace errors in XML:

• Open exported ports binding XML file:

Pic2. Origin of the exception selected

Notice this property, “Filter”. It has break lines and white spaces. BizTalk refuses to import bindings like this, and generates an exception. Worst part is that this exception is generic, and meaningless.

To fix this, you must remove all white spaces and all break lines inside this field. This problem appears because these filters have an “AND” relationship between them, and BizTalk can’t understand those mathematical relationships with all these white spaces and break lines among them.

The final and fixed XML property should look like this:

<SomePropertyName>all lines here without spaces or break lines</SomePropertyName>

If you run into some exceptions importing port bindings, you should analyze the bindings file and look for a XML property with spaces and break lines. Re-arrange and you should be OK importing bindings and enlisting ports now!

The post How to fix BizTalk Server Administration Exception 0xC00CE557: Could not enlist Send Port appeared first on Blog IT.