Peter

167 reputation

bio	website
	location	Idaho
	age	27
visits	member for	1 year, 11 months
	seen	Feb 1 at 15:19
stats	profile views	4

I am a ASP.Net/VB.Net/C# developer. I work on and develop custom web based solutions and interfaces.

	167 reputation	bio	website		visits	member for	1 year, 11 months
7 badges		location	Idaho		seen	Feb 1 at 15:19

summary answers questions tags badges favorites bounties reputation activity

28 Actions

suggestions reviews revisions comments badges posts accepts all

Nov 9	comment	SPItemEventReceiver ItemAdding - Differentiate between a file and a folder Jon, we found that with SP2010 that what you are saying is the case, but that in SP2007 both files and folders showed a zero file size in Explorer view. Sp2007 at the time was what we were working with.
Oct 11	awarded	Popular Question
Aug 14	awarded	Popular Question
Nov 29	comment	SPItemEventReceiver ItemAdding - Differentiate between a file and a folder This looks like a great option. When we upgrade to 2010 I'll switch my code to work this way.
Nov 16	accepted	SPItemEventReceiver ItemAdding - Differentiate between a file and a folder
Nov 16	comment	SPItemEventReceiver ItemAdding - Differentiate between a file and a folder Two issues with this approach. One, we dont want to block pdf, we want to block everything BUT pdf. Two, this setting is at the Web application level. We have a ton of sites with lists where we put no restrictions on the file type.
Nov 16	awarded	Commentator
Nov 16	comment	SPItemEventReceiver ItemAdding - Differentiate between a file and a folder Curious if SharePoint will cancel the uploading of a file through explorer view if I say properties.Cancel=true? If thats your question then the answer is yes, it does cancel it (already tested that part).
Nov 16	comment	SPItemEventReceiver ItemAdding - Differentiate between a file and a folder When adding a folder using Explorer view there are no after properties (which is odd). When adding a file through explorer view I have "vti_filesize", which seems to equal zero even if the file has size, and "vti_parserversion" which is "12.0.0.6562".
Nov 16	comment	SPItemEventReceiver ItemAdding - Differentiate between a file and a folder Just saw your update. I do think that throught the web interface this would solve the issue, now I'm just worried about people going through Explorer view.
Nov 16	comment	SPItemEventReceiver ItemAdding - Differentiate between a file and a folder ContentType is not present. ContenTypeId is present when I use the web interface (properties.AfterProperties["ContentTypeId"]) but not when I use the Windows Explorer interface. ContentTypeId appears to be a guid.
Nov 16	awarded	Editor
Nov 16	revised	SPItemEventReceiver ItemAdding - Differentiate between a file and a folder added 202 characters in body
Nov 16	comment	SPItemEventReceiver ItemAdding - Differentiate between a file and a folder Thanks for the suggestion. Unfortunately properties.ListItem is always null during the ItemAdding event because the ListItem does not exist yet.
Nov 16	asked	SPItemEventReceiver ItemAdding - Differentiate between a file and a folder
Nov 15	comment	Moving large document libraries to new site collections I did some more research, what about using Microsoft.SharePoint.Deployment.SPExport / SPImport? This appears to be able handle SPList objects.
Nov 15	accepted	Make a folder in a document library read only without using security
Nov 14	asked	Moving large document libraries to new site collections
Nov 13	comment	Make a folder in a document library read only without using security This sounds like it could work. Per @Sig Weber I'll also need to disable viewing in windows explorer and DataSheet view, but putting in a custom event receiver sounds plausible.
Nov 13	comment	Make a folder in a document library read only without using security @Kit - We've considered the idea of putting the closed items into separate folders/separate document libraries. The problem is that there is a vendor provided interface which connects our task management system with SharePoint and it expects all the folders to be in the root of a single document library. Because of this people would no longer be able to launch the folders from the task system if the task was closed.