by Jesper Persson
20. March 2009 10:36
When you create a new view for a list you can specify different Styles, but you can extend those styles too heres how to: The file are located under C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\GLOBAL\XML\VWSTYLES.XML
0ed640dd-fafd-4573-ad84-4abf775bab34|0|.0
Tags:
by Jesper Persson
17. March 2009 21:04
|
Today I saw a strange error when creating a feature with a custom contenttype, I had no special field type pretty basic stuff but when the feature was activated this exception was thrown:
|
 |
 |
Value does not fall within the expected range. at Microsoft.SharePoint.SPContentTypeId..ctor(String id)
at Microsoft.SharePoint.SPContentTypeElement.ElementActivated(SPFeaturePropertyCollection props, SPSqlCommand sqlcmdAppendOnly, SPWebApplication webApp, SPSite site, SPWeb webNull, Boolean fForce)
at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionFieldsAndContentTypes(SPFeaturePropertyCollection props, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionElements(SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.SPFeature.ProvisionElements(SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce)
at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
at Microsoft.SharePoint.WebControls.FeatureActivator.BtnActivateFeature_Click(Object objSender, EventArgs evtargs)
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) |
|
First I thought it was some sort of error due to the fact that im inheriting from the picture contenttype, the ULS and eventlog did not help much.
The contentype element:
<ContentType Name="MYcType" ID="0X010102008A0F43E3F6A74b968501DFB9F2DBBA59">
After some investigation I realised that the problem was with the ID attribute, don't use capital X in the ID attributes value like above use this instead:
<ContentType Name="MYcType" ID="0x010102008A0F43E3F6A74b968501DFB9F2DBBA59">
by Jesper Persson
12. March 2009 13:07
After installing the CAML.NET IntelliSense the intellisense stopped to work but only in XML files my normal C# code was working just fine.
What the h... the xmlns is set to Sharepoint but it does not work in any of my projects????
Just to be sure I started all over with a blank Solution and en empty Project, then I added a XML file
Look I can choose the right namespace
This is a start but wait no intellisense, how about that.
As it turns out VS had added all the XSD's and that did not work well, if they share the same namespaces and element declarations.
To solve the issue I selected the Schema property on the document and pressed the ... button
As you can see all the sharepoint schemas has been selected
Change it like this
And Voila intellisense is back
by Jesper Persson
11. March 2009 18:41
Once upon a time
I was listening to my favorite Sharepoint podcast I think it was this show. They were talking about the different tools you have to have in your bag as a Sharepoint developer, most of them was not new to me but I think it was Andrew Connell who were talking about a tool/utility that extended the Windows Explorer context menu, so you can install a Solution file (wsp) from the menu.
Let me get one
That sounds like a great utility, so I immediately googled for a tool like that, but I was unable to find anyone else who had done that, might be because I can't find the right search terms but anyhow, I'm not giving up so easily so I made the utility myself.
My primary goal was that no assemblies or code should be deployed so the solution is only a modification to the registry.
Download the registry file here, it's tested on Windows 2003 Server R2 and Windows 2008 Server.
wsp solutions.reg (832,00 bytes)
The result
by Jesper Persson
4. March 2009 18:49
Jacob Nielsen has awarded the 10 best Intranets for 2008 but one of the most interesting things about the list is, besides that the danish company COWI is on the list, are that 5 of the 10 intranets are based on Sharepoint.
This is from the UseIt Site: In total, the 10 winners were built on 26 different products — substantially fewer than the 41 used in 2008 or the 49 used in 2007. Most impressively, fully half of the winning intranets used SharePoint, especially the recent MOSS platform (Microsoft Office SharePoint Server 2007). As the following chart shows, SharePoint use has grown dramatically in recent years. This is particularly impressive given that, from 2003–2006, the winning intranets didn't use earlier versions of SharePoint at all.
Microsoft SharePoint has seen substantially increased use among well-designed intranets in recent years.
by Jesper Persson
4. March 2009 17:00
I was just browsing the Pattterns & Practice web site the other day and noticed that they have released a Sharepoint Guidance in November, ít has escaped me completely, and I dont think many other people have seen it at least not people I meet. It is very comprehensive give it a try
http://www.microsoft.com/downloads/details.aspx?FamilyId=C3722DBA-6EE7-4E0E-82B5-FDAF3C5EC927&displaylang=en
by Jesper Persson
2. March 2009 18:27
Finally after a long long time with out any blog, im back, time will tell how many entries i'll make but you have to start some where, right