Web User

67 reputation

bio	website
	location	Chicago, IL
	age
visits	member for	1 year, 4 months
	seen	May 19 at 0:59
stats	profile views	7

	67 reputation	bio	website		visits	member for	1 year, 4 months
7 badges		location	Chicago, IL		seen	May 19 at 0:59

summary answers questions tags badges favorites bounties reputation activity

37 Actions

suggestions reviews revisions comments badges posts accepts all

May 16	comment	SharePoint Site Content Types and Site Columns Galleries are empty I added a code snippet and also an update to the details of the issue/behavior. Thanks.
May 16	revised	SharePoint Site Content Types and Site Columns Galleries are empty Added code snipppet and update to details
May 15	asked	SharePoint Site Content Types and Site Columns Galleries are empty
Feb 19	revised	Content type issue when migrating from SharePoint 2003 to 2007 added 1199 characters in body
Feb 19	comment	Content type issue when migrating from SharePoint 2003 to 2007 Thanks for the suggestion, I will do that.
Feb 19	asked	Content type issue when migrating from SharePoint 2003 to 2007
Nov 25	comment	All columns getting added to Document content type in migrated site PowerShell 2.0 (on Windows Server 2003 R2 with SP2)
Nov 23	comment	All columns getting added to Document content type in migrated site @FalakMahmood I have support to run PowerShell.
Nov 19	comment	All columns getting added to Document content type in migrated site I tried to replicate this problem with a new library created in MOSS 2007. Actually I don't see this behavior. Maybe user created columns get added to the Document content type, but not fields like Created By, Modified By and Checked Out To. In my case, even those fields are getting added to the Document content type. I can provide the list template based on the migrated library, and you will be able to replicate this problem.
Nov 19	awarded	Commentator
Nov 19	comment	All columns getting added to Document content type in migrated site I may not have understood this problem as well as I should have, from your response. Before migration, there were about 15 columns in the library. Since 2003 lacked content types, I used an external tool to populate the appropriate columns, depending on whether the item was a document or email. In 2007, this translates to having two content types - Document and Email. So after migration, I wanted to enable content types and add the Email content type (Document is auto added). Problem is, I wanted to selectively link some columns to Document and some to Email.
Nov 17	comment	All columns getting added to Document content type in migrated site In an attempt to try every possibility, I deleted the implicit Document content type (that's right, even if content type management was never enabled on a document library, there is a Document and Folder content type), enabled content type management and [had to] explicitly add the Document content type from the site content types. This seemed to resolve the problem, but I feel this is a hack more than a resolution. Thinking of opening a ticket with Microsoft.
Nov 16	asked	All columns getting added to Document content type in migrated site
Sep 4	comment	How do you “stop” activating a feature within the feature receiver? My console application adds a feature to a SPWeb with something like this `web.Features.Add(featureGuid, true);`. This works fine, but when an exception is thrown in that feature's FeatureActivated event receiver, my console application has no clue of the error. Is there any way I can catch and process the error?
Aug 22	awarded	Benefactor
Aug 22	accepted	Build with SP Designer 2007, package with VStudio 2008
Aug 20	comment	Build with SP Designer 2007, package with VStudio 2008 So I can create this page in say, a dev/staging environment first? Does the page get saved in the content database and not the file system? In that case, how do I copy the file to package it in a feature based WSP?
Aug 15	awarded	Promoter
Aug 13	asked	Build with SP Designer 2007, package with VStudio 2008
Aug 2	comment	Copy the whole production environment to staging How does stsadm handle the difference in URL (e.g. production is portal.company.com and staging is stagedportal.company.com)?