Could not find file xxx DocSiteContents.xml

Topics: Bugs, DocSites, General Discussion
Jun 7, 2007 at 2:46 PM
I just installed the 1.5.0 version of DocProject on a Windows XP SP2 machine. I created a DocSite and pointed it to the proper assembly. The site built successfully, however, when the web page was rendered it produced the following error:

Could not find file xxx\DocSiteContents.xml.
Source Error:

Line 35: {
Line 36: if (docSiteContentsDocument == null)
Line 37: docSiteContentsDocument = new XPathDocument(HttpContext.Current.Server.MapPath(
Line 38: Properties.Settings.Default.DocSiteContentsXmlSource));
Line 39: }

Source File: C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisCommonDocSiteHelp\DocSiteNavigator.cs Line: 37

This file was not generated by the build. I used all the project defaults in the wizard when creating the project.
Any help is greatly appreciated.

Thanks
Paul
Coordinator
Jun 7, 2007 at 3:53 PM
Edited Jun 7, 2007 at 3:55 PM
Hi,

Thanks for using DocProject.

Did the build output actually state that the build succeeded? 1.5.0 and earlier versions of DocProject might run the DocSite if you pressed F5 even if the build actually failed (this is not the case in 1.6.0, however).

Was the DocSiteIndex.xml file built? Scroll up a bit and see if it even tried to build the contents and index files for the DocSite, which occurs after Verifying Output...

Are there any errors about this in the Application event log? (Look for DocProject as the source.)

- Thanks
Jun 7, 2007 at 6:16 PM
Hi,
It did say that the build was successful. When going through the build output I did a search for the DocSiteIndex.xml file but it was not found.

Here's the final couple of lines of the output:

Successful Steps: 9 of 9
Failed Steps: 0

xxxDocSiteHelp help build complete.


Would it be useful to send you the build output(It's too large to paste here)?

Thanks
Jun 7, 2007 at 6:36 PM
Hi,
I ran it against a much smaller class and got the same results. Here is the full build output:

------ Build started: Project: PicisHelper, Configuration: Release Any CPU ------
PicisHelper -> C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelper\bin\Release\PicisHelper.dll
------ Build started: Project: PicisHelperDocSite, Configuration: Release Any CPU ------
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig /nowarn:1701,1702 /errorreport:prompt /warn:4 /define:TRACE /reference:C:\WINDOWS\assembly\GACMSIL\DaveSexton.DocProjectAddin\1.5.0.0_af1a4bab65cc4ece\DaveSexton.DocProjectAddin.dll /reference:"C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelper\bin\Release\PicisHelper.dll" /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Configuration.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.dll /reference:"C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025\System.Web.Extensions.dll" /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /debug:pdbonly /optimize+ /out:obj\Release\PicisHelperDocSite.dll /target:library Properties\AssemblyInfo.cs BuildProcess.cs DocSiteContents.ascx.cs DocSiteContents.ascx.designer.cs Default.aspx.cs Default.aspx.designer.cs DocSite.Master.cs DocSite.Master.designer.cs DocSiteContentsSiteMapProvider.cs DocSiteIndex.ascx.cs DocSiteIndex.ascx.designer.cs DocSiteNavigator.cs DocSiteSidebar.ascx.cs DocSiteSidebar.ascx.designer.cs Properties\Settings.Designer.cs

Compile complete -- 0 errors, 0 warnings
PicisHelperDocSite -> C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\bin\PicisHelperDocSite.dll

Starting help build for PicisHelperDocSite...
Preparing target directory...
Building documentation for PicisHelperDocSite...

Step 1 of 9: Change Directory

Changing current directory from "C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite" to "C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\buildhelp"

Step 1 Time Elapsed: 00:00:00

Step 2 of 9: Execute MRefBuilder

C:\Program Files\Sandcastle\ProductionTools\MRefBuilder /config:"C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\Presentation\Configuration\MRefBuilder.config" /out:reflection.org /internal- /dep:"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll","C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll","C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll","C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll","C:\WINDOWS\assembly\GACMSIL\System.Configuration\2.0.0.0_b03f5f7f11d50a3a\System.Configuration.dll","C:\WINDOWS\assembly\GACMSIL\Microsoft.VisualC\8.0.0.0_b03f5f7f11d50a3a\Microsoft.VisualC.dll","C:\WINDOWS\assembly\GAC32\System.Transactions\2.0.0.0_b77a5c561934e089\System.Transactions.dll","C:\WINDOWS\assembly\GAC32\System.EnterpriseServices\2.0.0.0_b03f5f7f11d50a3a\System.EnterpriseServices.dll" "C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelper\bin\Release\PicisHelper.dll"

MrefBuilder (v2.2.63000.2)
Copyright c Microsoft 2006
Info: Loaded 1 assemblies for reflection and 8 dependency assemblies.
Info: Wrote information on 1 namespaces, 2 types, and 4 members

Step 2 Time Elapsed: 00:00:01.6875000

Step 3 of 9: Execute XslTransform

C:\Program Files\Sandcastle\ProductionTools\XslTransform /xsl:"C:\Program Files\Sandcastle\ProductionTransforms\ApplyVSDocModel.xsl" reflection.org /xsl:"C:\Program Files\Sandcastle\ProductionTransforms\AddFriendlyFilenames.xsl" /out:"reflection.xml"

XslTransform (v2.2.63000.2)
Copyright c Microsoft 2005-2006
Info: Applying XSL transformation 'C:\Program Files\Sandcastle\ProductionTransforms\ApplyVSDocModel.xsl'.
Info: Applying XSL transformation 'C:\Program Files\Sandcastle\ProductionTransforms\AddFriendlyFilenames.xsl'.

Step 3 Time Elapsed: 00:00:01.2343750

Step 4 of 9: Execute XslTransform

C:\Program Files\Sandcastle\ProductionTools\XslTransform /xsl:"C:\Program Files\Sandcastle\ProductionTransforms\ReflectionToManifest.xsl" "reflection.xml" /out:manifest.xml

XslTransform (v2.2.63000.2)
Copyright c Microsoft 2005-2006
Info: Applying XSL transformation 'C:\Program Files\Sandcastle\ProductionTransforms\ReflectionToManifest.xsl'.

Step 4 Time Elapsed: 00:00:00.7031250

Step 5 of 9: Execute XslTransform

C:\Program Files\Sandcastle\ProductionTools\XslTransform /xsl:"C:\Program Files\Sandcastle\ProductionTransforms\CreateVSToc.xsl" "C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\buildhelp\reflection.xml" /out:"toc.xml"

XslTransform (v2.2.63000.2)
Copyright c Microsoft 2005-2006
Info: Applying XSL transformation 'C:\Program Files\Sandcastle\ProductionTransforms\CreateVSToc.xsl'.

Step 5 Time Elapsed: 00:00:01.3125000

Step 6 of 9: Copy File

Copy "C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\buildhelp\reflection.xml" to "C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\buildhelp\assembler\reflection.xml" and overwrite.

Step 6 Time Elapsed: 00:00:00.2031250

Step 7 of 9: Change Directory

Changing current directory from "C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\buildhelp" to "C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\buildhelp\assembler"

Step 7 Time Elapsed: 00:00:00.0156250

Step 8 of 9: Build Assembler {sandcastle.helpV1.config}

Info: Instantiating component.
Info: Loading data file '..\..\Presentation\Transforms\skeleton.xml'.
Info: Instantiating component.
Info: Searching for files that match 'reflection.xml'.
Info: Searching for files that match 'C:\Program Files\Sandcastle\\Data\cpref_reflection\*.xml'.
Info: Indexed 149254 elements in 105 files.
Info: Instantiating component.
Info: Instantiating component.
Info: Loading subcomponents.
Info: Instantiating component.
Info: Loaded 1 subcomponents.
Info: Instantiating component.
Info: Loading subcomponents.
Info: Instantiating component.
Info: Loaded 1 subcomponents.
Info: Instantiating component.
Info: Instantiating component.
Info: Loaded 3 syntax generators.
Info: Instantiating component.
Info: Searching for files that match 'comments*.xml'.
Info: Searching for files that match 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\*.xml'.
Info: Indexed 76755 elements in 67 files.
Info: Instantiating component.
Info: Loading subcomponents.
Info: Instantiating component.
Info: Instantiating component.
Info: Instantiating component.
Info: Loaded 2 subcomponents.
Info: Instantiating component.
Info: Instantiating component.
Info: Instantiating component.
Info: Loading shared content file '..\..\Presentation\content\shared_content.xml'.
Info: Loading shared content file '..\..\Presentation\content\reference_content.xml'.
Info: Overriding shared content item 'methodindexentry' with value in file '..\..\Presentation\content\reference_content.xml'.
Info: Overriding shared content item 'remarkstitle' with value in file '..\..\Presentation\content\reference_content.xml'.
Info: Overriding shared content item 'namespacenameheader' with value in file '..\..\Presentation\content\reference_content.xml'.
Info: Overriding shared content item 'runningheadertext' with value in file '..\..\Presentation\content\reference_content.xml'.
Info: Loading shared content file '..\..\Presentation\content\syntax_content.xml'.
Info: Loaded 375 shared content items.
Info: Instantiating component.
Info: Indexed 149254 reference link targets.
Info: Instantiating component.
Info: Building topic R:Project
Info: Building topic N:PicisHelper
Info: Building topic T:PicisHelper.PicisHelper
Info: Preparing to query MSDN topic URL web service.
Info: Building topic AllMembers.T:PicisHelper.PicisHelper
Info: Building topic Methods.T:PicisHelper.PicisHelper
Info: Building topic M:PicisHelper.PicisHelper.#ctor
Info: Building topic M:PicisHelper.PicisHelper.GetLeft(System.String,System.Int32)
Info: Building topic T:PicisHelper.ReturnType
Info: Building topic Fields.T:PicisHelper.ReturnType
Warn: Missing shared content item 'fieldsindexentry'.
Info: Building topic F:PicisHelper.ReturnType.Failed
Info: Building topic F:PicisHelper.ReturnType.Successful

Topics processed: 11

Step 8 Time Elapsed: 00:01:24.7812500

Step 9 of 9: Copy Directory

Deep move "C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\buildhelp\assembler\Output\html" to "C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\Html".

Step 9 Time Elapsed: 00:00:00.6093750

Verifying output...

Total Time Elapsed: 00:02:02.2187500

Successful Steps: 9 of 9
Failed Steps: 0

PicisHelperDocSite help build complete.

========== Build: 2 succeeded or up-to-date, 0 failed, 0 skipped ==========
Coordinator
Jun 7, 2007 at 10:03 PM
Hi,

I suspect that the ProjectInformation.IsWebApplication method is returning false. Would you mind testing this theory?

Open the build process component file BuildProcess.cs and make the following changes:

public override void BuildStarting(BuildContext context)
{
  // Adding the following line will help to making testing much faster - I haven't tested this in the 1.5.0 code base, 
  // so if it fails then remove it since it's not necessary for debugging this issue anyway.
  context.Steps.Clear();
}

public override void BuildCompleted(BuildContext context)
{
  // IsDocSite is checked to see if the contents and index must be generated immediately before this method is called.
  TraceLine("IsDocSite: {0}", context.IsDocSite);
}
Obviously, I'm expecting the output to be IsDocSite: false

Thanks.
Jun 8, 2007 at 1:02 PM
Hi Dave,
Your right...IsDocSite = False. Here's the build output:

------ Build started: Project: PicisHelper, Configuration: Release Any CPU ------
PicisHelper -> C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelper\bin\Release\PicisHelper.dll
------ Build started: Project: PicisHelperDocSite, Configuration: Release Any CPU ------
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig /nowarn:1701,1702 /errorreport:prompt /warn:4 /define:TRACE /reference:C:\WINDOWS\assembly\GACMSIL\DaveSexton.DocProjectAddin\1.5.0.0_af1a4bab65cc4ece\DaveSexton.DocProjectAddin.dll /reference:"C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelper\bin\Release\PicisHelper.dll" /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Configuration.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.dll /reference:"C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025\System.Web.Extensions.dll" /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /debug:pdbonly /optimize+ /out:obj\Release\PicisHelperDocSite.dll /target:library Properties\AssemblyInfo.cs BuildProcess.cs DocSiteContents.ascx.cs DocSiteContents.ascx.designer.cs Default.aspx.cs Default.aspx.designer.cs DocSite.Master.cs DocSite.Master.designer.cs DocSiteContentsSiteMapProvider.cs DocSiteIndex.ascx.cs DocSiteIndex.ascx.designer.cs DocSiteNavigator.cs DocSiteSidebar.ascx.cs DocSiteSidebar.ascx.designer.cs Properties\Settings.Designer.cs

Compile complete -- 0 errors, 0 warnings
PicisHelperDocSite -> C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\bin\PicisHelperDocSite.dll

Starting help build for PicisHelperDocSite...
Preparing target directory...
Building documentation for PicisHelperDocSite...

Verifying output...

Missing output: C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\Html\

Total Time Elapsed: 00:00:04.3125000
IsDocSite: False

No steps executed.

PicisHelperDocSite help build complete.

========== Build: 2 succeeded or up-to-date, 0 failed, 0 skipped ==========


Is there a resolution?

Thanks
Coordinator
Jun 8, 2007 at 2:39 PM
Hi,

Thanks for testing this out for me.

The resolution to this issue could be in 1.6.0, which I planned on deploying today as a matter of fact. But I can delay the deployment for another day or two if necessary to fix this show-stopper, with your help :)

First, I'd like to see what the value is for one particular project property, although seeing all of the project's properties would be useful.
Please add the following lines of code to the BuildCompleted method:

  string file = @"C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\Properties.txt";
  ProjectInformation.WriteProperties(context.Engine.Project.Project, file, false);
I'd like to the see the output file, of course.
Also, please provide me with information about your version of Visual Studio:
  1. Help > About Microsoft Visual Studio
  2. Click the Copy Info button
  3. Remove any personal or private information
  4. Paste the remaining information in your next post ;)
Thanks!
Jun 8, 2007 at 3:16 PM
Hi Dave,
Here you go. The VS info is at the bottom. Just an FYI, I am using the project in VS2005 Professional but also have VS ORCAS installed on the system.
Thanks for you help with this.

Project Name: PicisHelperDocSite

Property Type Value

1) ComVisible Boolean False
2) EnableSecurityDebugging Boolean True
3) OptionCompare Int32 0
4) StartupObject String
5) ManifestCertificateThumbprint String
6) Trademark String
7) Title String PicisHelperDocSite
8) VSPolicyExtenderProvider.TDLFileName String
9) AssemblyOriginatorKeyFileType UInt32 1
10) FileName String PicisHelperDocSite.csproj
11) WebServer Error: Exception occurred. (Exception from HRESULT: 0x80020009 (DISPEEXCEPTION))
12) AssemblyOriginatorKeyMode Int32 0
13) AssemblyKeyContainerName String
14) ProjectType Int32 0
15) ReferencePath String
16) PreBuildEvent String
17) Copyright String Copyright © 2007
18) ApplicationIcon String
19) ExcludedPermissions String
20) RunPostBuildEvent Int32 1
21) DefaultTargetSchema Int32 1
22) RootNamespace String PicisHelperDocSite
23) ManifestTimestampUrl String
24) ManifestKeyFile String
25) DebugSecurityZoneURL String
26) Product String PicisHelperDocSite
27) PostBuildEvent String
28) OptionStrict Int32 0
29) DefaultHTMLPageLayout Int32 1
30) DelaySign Boolean False
31) OutputType Int32 2
32) NeutralResourcesLanguage String
33) OptionExplicit Int32 1
34) OutputFileName String PicisHelperDocSite.dll
35) ServerExtensionsVersion Error: Exception occurred. (Exception from HRESULT: 0x80020009 (DISPEEXCEPTION))
36) AssemblyGuid String 6d0b2ad7-e1a7-46a9-b7ca-df245d238e99
37) GenerateManifests Boolean False
38) AssemblyVersion String 1.0.0.0
39) Win32ResourceFile String
40) Description String PicisHelperDocSite web help system.
41) URL String file:///C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\
42) DefaultClientScript Int32 0
43) SignManifests Boolean False
44) OfflineURL Error: Exception occurred. (Exception from HRESULT: 0x80020009 (DISPEEXCEPTION))
45) WebServerVersion Error: Exception occurred. (Exception from HRESULT: 0x80020009 (DISPEEXCEPTION))
46) Publish _ComObject System._ComObject
47) AssemblyType Int32 0
48) FullPath String C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\
49) WebAccessMethod Error: Exception occurred. (Exception from HRESULT: 0x80020009 (DISPEEXCEPTION))
50) AssemblyKeyProviderName String
51) TypeComplianceDiagnostics Boolean False
52) Company String
53) ActiveFileSharePath Error: Exception occurred. (Exception from HRESULT: 0x80020009 (DISPEEXCEPTION))
54) AssemblyOriginatorKeyFile String
55) AssemblyFileVersion String 1.0.0.0
56) AspnetVersion Error: Exception occurred. (Exception from HRESULT: 0x80020009 (DISPEEXCEPTION))
57) FileSharePath Error: Exception occurred. (Exception from HRESULT: 0x80020009 (DISPEEXCEPTION))
58) AssemblyName String PicisHelperDocSite
59) LocalPath String C:\TFS Web\CommonResources\Development\Sources\Picis.Common\PicisHelperDocSite\
60) DefaultNamespace String PicisHelperDocSite
61) LinkRepair Boolean False
62) TargetZone String
63) SignAssembly Boolean False


Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727

Installed Edition: Professional

Microsoft Visual Basic 2005
Microsoft Visual Basic 2005

Microsoft Visual C# 2005
Microsoft Visual C# 2005

Microsoft Visual J# 2005
Microsoft Visual J# 2005

Microsoft Visual Web Developer 2005
Microsoft Visual Web Developer 2005

Microsoft Web Deployment Projects 2005
Microsoft Web Deployment Projects 2005

Visual Studio 2005 Team Explorer
Microsoft Visual Studio 2005 Team Explorer
Version 8.0.50727.147

Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005


Dundas Chart for ASP.NET 5.5
Dundas Chart for ASP.NET Enterprise Edition v5.5

Dundas Gauge for ASP.NET 1.6
Dundas Gauge for ASP.NET v1.6

Enterprise Library Configuration Editor 3.0
Microsoft patterns & practices Enterprise Library Configuration Editor

Microsoft Recipe Framework Package 8.0
This package provides services to the guidance packages.

Orcas Technology Preview - .NET Framework 3.0 Development Tools 1.0
Microsoft Visual Studio Code Name Orcas Community Technology Preview - Development Tools for WinFX

Dave Sexton's DocProject
For more information, go to http://www.codeplex.com/DocProject
Copyright © 2006-2007 Dave Sexton
http://davesexton.com

Coordinator
Jun 8, 2007 at 4:06 PM
Hi,

Thanks for the data. It appears that a property required by DocProject doesn't exist in your project.

  • I assume that you used a DocSite template that came with DocProject without any custom modifications. Correct?
  • Which did you install - Visual Studio SP2 or the two updates for Web Application projects?
  • Have you tried creating a new DocSite in a different solution to see if that works?
I guess the next thing that I need to see is the project file itself. If it's missing a project type GUID then that would explain it; however, I can't imagine
that the project would work as a web application at all in that case. Anyway, if you could post the .csproj file that would be great, but you can remove
all of the <ItemGroup> elements and their child elements since I don't need to see them.

What I'm expecting to see is something like this:

  <ProjectGuid>{0E635652-D7F5-401C-9978-FBE15FBF4E6B}</ProjectGuid>
  <ProjectTypeGuids>{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
but I'd like to see the rest of the file as well, just in case.

Thanks.
Jun 8, 2007 at 5:41 PM
Hi,
1. I did use the DocSite template with no modifications.
2. I'm not really sure, I know an update was done for the Web Application project type but not sure if it was two.
3. Just tried a new solution and got the same results.

Here's the csproj file (I took out some of the <Item Group> elements....Thanks again!

<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
<Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
<ProductVersion>8.0.50727</ProductVersion>
<SchemaVersion>2.0</SchemaVersion>
<ProjectGuid>{12D95DD0-19CF-46B9-8A4F-212A6E825D32}</ProjectGuid>
<ProjectTypeGuids>{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
<OutputType>Library</OutputType>
<AppDesignerFolder>Properties</AppDesignerFolder>
<RootNamespace>PicisHelperDocSite</RootNamespace>
<AssemblyName>PicisHelperDocSite</AssemblyName>
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
<DebugSymbols>true</DebugSymbols>
<DebugType>full</DebugType>
<Optimize>false</Optimize>
<OutputPath>bin\</OutputPath>
<DefineConstants>DEBUG;TRACE</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
<DebugType>pdbonly</DebugType>
<Optimize>true</Optimize>
<OutputPath>bin\</OutputPath>
<DefineConstants>TRACE</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
</PropertyGroup>
<ItemGroup>
<Reference Include="System" />
<Reference Include="System.Data" />
<Reference Include="System.Configuration" />
<Reference Include="System.Drawing" />
<Reference Include="System.Web" />
<Reference Include="System.Xml" />
</ItemGroup>
<ItemGroup>
<Reference Include="DaveSexton.DocProjectAddin, Version=1.5.0.0, Culture=neutral, PublicKeyToken=af1a4bab65cc4ece, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
</Reference>
<Reference Include="EnvDTE, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
<SpecificVersion>False</SpecificVersion>
<HintPath>e:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies\EnvDTE.dll</HintPath>
</Reference>
<Reference Include="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
</Reference>
<Reference Include="VSLangProj, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\..\..\..\..\Program Files\Common Files\Microsoft Shared\MSEnv\PublicAssemblies\VSLangProj.dll</HintPath>
</Reference>
<Reference Include="VSLangProj80, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\..\..\..\..\Program Files\Common Files\Microsoft Shared\MSEnv\PublicAssemblies\VSLangProj80.dll</HintPath>
</Reference>
</ItemGroup>
<ItemGroup>
<Compile Include="Properties\AssemblyInfo.cs" />
<Compile Include="BuildProcess.cs" />
<Compile Include="DocSiteContents.ascx.cs">
<DependentUpon>DocSiteContents.ascx</DependentUpon>
<SubType>ASPXCodeBehind</SubType>
</Compile>
<Compile Include="DocSiteContents.ascx.designer.cs">
<DependentUpon>DocSiteContents.ascx</DependentUpon>
</Compile>
<Compile Include="Default.aspx.cs">
<SubType>ASPXCodeBehind</SubType>
<DependentUpon>Default.aspx</DependentUpon>
</Compile>
<Compile Include="Default.aspx.designer.cs">
<DependentUpon>Default.aspx</DependentUpon>
</Compile>
<Compile Include="DocSite.Master.cs">
<DependentUpon>DocSite.Master</DependentUpon>
<SubType>ASPXCodeBehind</SubType>
</Compile>
<Compile Include="DocSite.Master.designer.cs">
<DependentUpon>DocSite.Master</DependentUpon>
</Compile>
<Compile Include="DocSiteContentsSiteMapProvider.cs" />
<Compile Include="DocSiteIndex.ascx.cs">
<DependentUpon>DocSiteIndex.ascx</DependentUpon>
<SubType>ASPXCodeBehind</SubType>
</Compile>
<Compile Include="DocSiteIndex.ascx.designer.cs">
<DependentUpon>DocSiteIndex.ascx</DependentUpon>
</Compile>
<Compile Include="DocSiteNavigator.cs" />
<Compile Include="DocSiteSidebar.ascx.cs">
<DependentUpon>DocSiteSidebar.ascx</DependentUpon>
<SubType>ASPXCodeBehind</SubType>
</Compile>
<Compile Include="DocSiteSidebar.ascx.designer.cs">
<DependentUpon>DocSiteSidebar.ascx</DependentUpon>
</Compile>
<Compile Include="Properties\Settings.Designer.cs">
<AutoGen>True</AutoGen>
<DesignTimeSharedInput>True</DesignTimeSharedInput>
<DependentUpon>Settings.settings</DependentUpon>
</Compile>
</ItemGroup>
<ItemGroup>
<Content Include="Web.config" />
</ItemGroup>

<ItemGroup>
<ProjectReference Include="..\PicisHelper\PicisHelper.csproj">
<Project>{72E7E4A5-F094-423A-A8F2-9336A56D6594}</Project>
<Name>PicisHelper</Name>
</ProjectReference>
</ItemGroup>
<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />
<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v8.0\WebApplications\Microsoft.WebApplication.targets" />
<!-- To modify your build process, add your task inside one of the targets below and uncomment it.
Other similar extension points exist, see Microsoft.Common.targets.
<Target Name="BeforeBuild">
</Target>
<Target Name="AfterBuild">
</Target>
-->
<ProjectExtensions>
<VisualStudio>
<UserProperties IsDocProject="true" ProcessComponentTypeName="PicisHelperDocSite.BuildProcess" BuildEngineProviderName="Sandcastle" SandcastlePresentationType="vs2005" SandcastleProduceHelpVersion1="False" Sandcastle_ProduceHelpVersion2="False" DefaultApplyToAll="True" />
</VisualStudio>
</ProjectExtensions>
</Project>
Coordinator
Jun 8, 2007 at 8:02 PM
Ok, so none of the WebApplication.* properties are available through VS automation, but the project file looks fine.

Please verify whether you have installed both updates for Web Applications. I guess you could just try installing them again:

How To Configure Visual Studio 2005 For DocProject
http://www.codeplex.com/DocProject/Wiki/View.aspx?title=How+To+Configure+Visual+Studio+2005+for+DocProject

Actually, if it's not too much to ask, maybe you could try uninstalling the Web Application update that you have and try installing
Visual Studio 2005 SP1 instead? (I incorrectly referred to the update as SP2 in a previous post - sorry)

I have a feeling that this problem is not related to the version of Visual Studio that you are using, or any configuration settings,
but either missing updates or some sort of conflict with Orcas.

Thanks.

Coordinator
Jun 9, 2007 at 9:54 PM
Hi,

I looked over the version information that you provided again and I think that you are missing the update for Web Applications:

Microsoft Web Application Projects 2005
Version 8.0.50727.867

Apparently, you only installed one (or none) of the required updates; however, I just discovered that the Web Application Add-In is no longer available from Microsoft anyway.
The download page that I linked to now has a message stating that SP1 provides the same updates and should be installed instead. I tried to reproduce this issue with your
exact version of Visual Studio 2005 on a virtual machine but I was unsuccessful because I had to install SP1 just to support the templates.

Although, I was able to build a DocSite using VS 2005 Pro on Windows XP SP2, after installing VS 2005 SP1, although I didn't try installing an Orcas CTP too :)

I assume that your installation of Orcas CTPs inadvertently filled-in-the-blanks and actually got Web Applications working for you in VS 2005 when it really shouldn't have.

Please let me know if you can install SP1 and if so, whether it works for you. If it doesn't work I'll probably have to code DocProject so that it reads the project file
and looks for the appropriate project guid types (probably using the MSBuild project class) but I really don't want to have to do that! ;)

Thanks.
Jun 12, 2007 at 5:21 PM
Hi Dave,
Wanted to give you an update on this. I tried installing the VS2005 SP1 however, after a couple of hours it just hung(I ran it overnight).
I then uninstalled the 1.5.0 version and installed the new 1.6 version. This also did not create the DocSiteContents.xml file.

Next, I installed 1.6.0 on another machine with VS2005 Team Suite. This did not work either so I will try and install the
Team Suite SP1 tonight. and then see (if it will install) and if it will create the DocSiteContents.xml file.

Thanks
Coordinator
Jun 12, 2007 at 6:57 PM
Hi,

Thanks for the update.

BTW, does the machine with VS2005 Team Suite have (or has it ever had) an Orcas CTP installed by any chance?

- Dave
Jun 14, 2007 at 9:21 PM
Hi Dave,
I was finally able to get this to work. I uninstalled the WebDeploymentProject from the original box (with VS2005 and ORCAS). I then reinstalled it (I had kept the update files in storage from way back).
After that I was able to build the help files for both single and multiple projects.

It looks great!

Thanks for all your help with this and am looking forward to future releases.
Coordinator
Jun 15, 2007 at 12:06 AM
Cool, thanks for keeping me up to date with your progress.

The cause and solution are still a bit unclear though. So in your opinion, do you think that it was having Orcas on the same machine without SP1 that caused the problem?
It sounds like you couldn't get SP1 working so you just installed the old Web App update and that worked for you, correct?

This information may be useful to others as well.

Thanks.
Aug 29, 2008 at 2:57 PM
Hi,

I think I got what the problem is. Maybe this would help you.

  • Apparently, the DocSite template wizard is not adding the Project in the references, even if you selected to include it.
  • Added manually the project in the references and it's now building and filling up the DocSiteContents
Cheers ^_^v. Cool App btw Dave.
Coordinator
Aug 29, 2008 at 3:43 PM
Hi netxph,

Thanks for the suggestion, but this thread is over a year old and nobody else has reported the same problem since.

Anyway, I think the problem in the OP's case was most likely some incompatibility with Orcas/SP1 at the time.  From his build output I can tell that source projects
were definitely being referenced.

But if in your experience the New Project Wizard is not adding references from selected projects in the last step, then you've identified a different bug altogether even
though you're seeing the same error message.

If you can reproduce the issue and provide the steps for me so that I can reproduce it as well, then please start another thread so that we can discuss it.

Thanks, 
Dave