This project will create two files in the named directory above: SPFServerModuleTraining.dll and SPFServerModuleTraining.pdb.
In some instances during the workshop we found that the .pdb file wasn't being compiled into the correct directory. This meant that subsequent attempts to debug the project weren't successful.
At the time of writing this, the only way of correcting/checking this is to manually edit the .vbproj file using a text editor. The lines in bold type need to be the same.
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' ==
'Debug|AnyCPU' ">
<DebugSymbols>true</DebugSymbols>
<DebugType>full</DebugType>
<DefineDebug>true</DefineDebug>
<DefineTrace>true</DefineTrace>
<OutputPath>..\..\Server
Projects\SPFServer\bin\</OutputPath>
<DocumentationFile>
</DocumentationFile>
<NoWarn>
</NoWarn>
<WarningLevel>0</WarningLevel>
<CodeAnalysisRules>
</CodeAnalysisRules>
<WarningsAsErrors>41999,42016,42017,42018,42019,42020,42021,42022,42032,42036</WarningsAsErrors>
<PlatformTarget>x86</PlatformTarget>
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' ==
'Release|AnyCPU' ">
<DebugType>pdbonly</DebugType>
<DefineDebug>false</DefineDebug>
<DefineTrace>true</DefineTrace>
<Optimize>true</Optimize>
<OutputPath>..\..\Server
Projects\SPFServer\bin\</OutputPath>
<DocumentationFile>
</DocumentationFile>
<NoWarn>
</NoWarn>
<WarningLevel>0</WarningLevel>
<WarningsAsErrors>41999,42016,42017,42018,42019,42020,42021,42022,42032,42036</WarningsAsErrors>
<PlatformTarget>x86</PlatformTarget>
</PropertyGroup>