Wrox Programmer Forums
BOOK: Professional SharePoint 2007 Development ISBN: 978-0-470-11756-9
This is the forum to discuss the Wrox book Professional SharePoint 2007 Development by John Holliday, John Alexander, Jeff Julian, Eli Robillard, Brendon Schwartz, Matt Ranlett, J. Dan Attis, Adam Buenz, Tom Rizzo; ISBN: 9780470117569
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional SharePoint 2007 Development ISBN: 978-0-470-11756-9 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old August 27th, 2009, 04:20 PM
Authorized User
Join Date: Jul 2009
Posts: 13
Thanks: 0
Thanked 0 Times in 0 Posts
Unhappy Chapter 11 - Undefined attributes in manifest.xml file

I am having some trouble getting the ProposalManager Chapter 11 sample code to work. It seems to have several undefined XML attributes in the manifest.xml file: itemaddedenabled, itemaddingenabled, etc. See XML snippet below. I can not find these attributes documented anyehere.

Where can I find documenation on the use of these attributes ? How are they defined?

<feature id="7b451019-6e9a-407e-8af9-b1fe9e8a5b1f" name="ProjectProposalItemEventReceiver" title="ProjectProposalItemEventReceiver" description="" version="" scope="Web" hidden="False" defaultresourcefile="core" >
<elementmanifest id="7b451019-6e9a-407e-8af9-b1fe9e8a5b1f" itemaddedenabled="True" itemaddingenabled="True" itemattachmentaddedenabled="False" itemattachmentaddingenabled="False" itemattachmentdeletedenabled="False" itemattachmentdeletingenabled="False" itemcheckedinenabled="True" itemcheckedoutenabled="True" itemcheckinginenabled="True" itemcheckingoutenabled="True" itemdeletedenabled="True" itemdeletingenabled="True" itemfileconvertedenabled="False" itemfilemovedenabled="False" itemfilemovingenabled="False" itemuncheckedoutenabled="True" itemuncheckingoutenabled="True" itemupdateddnabled="True" itemupdatingdnabled="True" />
Old September 4th, 2009, 07:50 AM
Wrox Author
Join Date: Jun 2007
Posts: 10
Thanks: 0
Thanked 2 Times in 2 Posts
Send a message via MSN to jholliday

You should ignore this file (solution.xml). It is only used internally by the VSeWSS tool. Here are more details:

1) The source code for the project was created using a tool called the Visual Studio Extensions for Windows SharePoint Services version 1.0, sometimes referred to as VSeWSS 1.0. This tool was created by Microsoft and at the time of the writing of the book, it was the recommended best practice for creating SharePoint solutions. Since that time, the tool has undergone many revisions and works quite differently now than it did then. One of the reasons for the revisions is that many developers did not like the way it worked. Specifically, they did not like the fact that it generated several "hidden" files that contain literal values which are needed by SharePoint in order to deploy the solution. Also, they did not like the fact that once you created a project using the tool, it was difficult to move the project to another system that did not also have the same version of the tool installed.

2) The file you are looking at is not part of the Visual Studio project itself. It is just an internal file that is created by VSeWSS 1.0 to control how it generates the code files which ARE included in the project. The fact that the solution.xml file contains elements that appear to be related to SharePoint is only a coincidence. It is not based on any SharePoint schema. It is essentially a settings file that is used only by VSeWSS. You should not even try to decipher the contents of this file, because it is irrelevant to the source code itself. It is generated on the fly by VSeWSS and is rewritten every time you make changes to the project properties and save the solution.

3) The reason the file is included in the code download is because it is needed by VSeWSS. When the book was written, there were no published plans to extend the VSeWSS tool. The assumption was that readers would download and install the tool themselves before attempting to build the code on their own machines. Microsoft has since changed their strategy, and has released several new versions of the tool. However, projects created using the previous version are not compatible with the newer versions. If you want to build the project today, and especially since you are trying to build it using Visual Studio 2008, then I suggest that instead of trying to import and build the project directly in VS2008, you first extract the essential code components and create a brand new project of your own. These elements are the "feature.xml" and other code files, which are located in the "ProposalManager\bin\Debug\solution" folder.
John F. Holliday, Author, MOSS MVP

Similar Threads
Thread Thread Starter Forum Replies Last Post
I can't modify the manifest file per the book! Webtechie BOOK: Expert Access 2007 Programming ISBN 978-0-470-17402-9 8 February 22nd, 2013 05:19 PM
Chapter 11 - DDF file missing from ProposalManager Solution dbaechtel BOOK: Professional SharePoint 2007 Development ISBN: 978-0-470-11756-9 1 September 3rd, 2009 09:58 PM
Getting a C# program with a manifest file to run i Bill_Thompson C# 2005 0 January 21st, 2008 06:27 PM
chapter 11 figure 11-7 relative positioning pelopito BOOK: Beginning CSS: Cascading Style Sheets for Web Design ISBN: 978-0-7645-7642-3 2 November 29th, 2007 06:11 AM
XML to XML, checking attributes raoulvb XSLT 4 December 9th, 2004 10:15 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.