Tag Info

New answers tagged

2

The debug tips from Nk SP and Hardik me helped me find the problem. The hive process was already in use so at the second attempt the debugger showed that the process was already in use. I changed the code to this and it worked using (SPWeb web = site.OpenWeb()) { string hive = ...


0

To debug your application you have to attach VS to the process w3wp.exe You can also use the event log, to log some messages. Instead of catching the exception when the file exists, try to use: string fileUrl = string.Format("{0}/{1}/{2}", web.Url, "SitePages", newFileName); SPFile file = web.GetFile(fileUrl); if (!file.Exists) //add Debug WSP ...


0

You can create your own permission levels which do not allow the document to be opened up from SharePoint. This will force them to have to open it outside, or download the record. If you set your permissions so people cannot delete items, the worst thing that can happen is they can save it back to the list item, but it will not overwrite the original file. ...


2

I guess it depends on the scope of your feature. If farm: You could use a custom service application (data gets saved to own database). It is not the easiest implementation, but it gives you lots of control http://msdn.microsoft.com/en-us/library/gg193964.aspx For site or web scope, you could use the corresponding property bags of SPSite or SPWeb ...



Top 50 recent answers are included