Solved: Finding assembly name. BE0067

Topics: User Forum
Jun 10, 2009 at 10:09 AM

Hi!

I have used SHFB on one library project and it worked fine.

When I use it on an xbap project, the Build Engine runs into trouble

SHFB: Error BE0067: Unable to obtain assembly name from project file '[projectFile]'' using Configuration 'Debug', Platform 'AnyCPU'

In the helpfile there is three issues to cover

* Check: misspelling of configuration and platfom.

* ??:  Configuration or Platform environment variable is defined. Not needed in the working project.

* Check: Visual Studio project to ensure that it contains a configuration and platform definition for the specified values

 

Do I need this environment variables? (they was'nt needed in the working project)

Below my projectfile, and I cant find any differense from the workin one.

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="3.5" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
    <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
    <ProjectGuid>{AE275CBC-4CEC-4298-94FF-67FF1B8A0191}</ProjectGuid>
    <ProjectTypeGuids>{60dc8134-eba5-43b8-bcc9-bb4bc16c2548};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
    <RootNamespace>EyeDocFP</RootNamespace>
    <AssemblyName>EyeDocFP</AssemblyName>

    .......

  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
    <DebugSymbols>true</DebugSymbols>
    <DebugType>full</DebugType>
    <Optimize>false</Optimize>
    <OutputPath>.\bin\Debug\</OutputPath>
    <DefineConstants>DEBUG;TRACE</DefineConstants>
    <DocumentationFile>bin\Debug\EyeDocFP.xml</DocumentationFile>
  </PropertyGroup>

    .......

</Project>

 

Best

/Jonas

Coordinator
Jun 10, 2009 at 7:50 PM

Are you using the latest release (1.8.0.2).  It fixed a similar issue caused by a difference in the casing of one of the property values used to determine the assembly type and name.  If you are using it and are still having the problem, can you e-mail me the Visual Studio project file so that I can try it out?  My e-mail address is in the About box and in the footer of the pages in the help file.  Thanks.

Eric

 

Aug 24, 2009 at 2:19 PM

Hi Eric, sorry for my late reply(holiday)

I downloaded the 1.802 version, uninstalled the 1.801 version, and it works.

Case solved.

Best

/Jonas

Nov 16, 2009 at 5:55 PM

 

Hello, i have the same problem with 1.8.02 VS2005 C++
SHFB: Error BE0067: Unable to obtain assembly name from project file
the name of the project and of the assembly dll is 
HeadController


thank you 
Steffen
<?xml version="1.0" encoding="Windows-1252"?>
<VisualStudioProject
	ProjectType="Visual C++"
	Version="8,00"
	Name="HeadController"
	ProjectGUID="{2CB3E19A-FC87-44E0-B2DF-915E393BA76A}"
	RootNamespace="HeadController"
	Keyword="ManagedCProj"
	>
	<Platforms>
		<Platform
			Name="Win32"
		/>
	</Platforms>
	<ToolFiles>
	</ToolFiles>
	<Configurations>
		<Configuration
			Name="Debug|Win32"
			OutputDirectory="$(SolutionDir)$(ConfigurationName)"
			IntermediateDirectory="$(ConfigurationName)"
			ConfigurationType="2"
			CharacterSet="1"
			ManagedExtensions="1"
			>
			<Tool
				Name="VCPreBuildEventTool"
			/>
			<Tool
				Name="VCCustomBuildTool"
			/>
			<Tool

 

 

Coordinator
Nov 16, 2009 at 6:56 PM

C++ projects are not supported as documentation sources yet as they do not use an MSBuild-compatible file structure.  Add the assembly and XML comments files from the project as documentation sources instead.

Eric