As seen in the post CAML and Querying Boolean Fields, if you need to query a boolean field, don't cast it as boolean
but insted cast it as integer:
If you need help in creating CAML queries, you can use the tool CAML.NET, that helps creating CAML queries in a type-safe way.
If you have an html field that the user can edit from user interface, SharePoint encloses its content in div tags.
Then, if you want to show its content in a SPGrid, the div tags appears, unless you set the HTMLEncoding property of the bound column to false.
I've taken this trick from How to stop gridview column from automatically encoding html entities.
Working with SharePoint, I've needed to create a calendar view on a Tasks list programmatically (i.e. from a feature).
I've done some research on the web, and I've found the great article Creating calendar view from tasks list programmatically.
From here you can see how to add a view and (very important) how to set the ViewData property of the view, but above all you can see the owssvr.dll service explained (even if you can use the more intuitive SharePoint Manager.
Only a note: from the initial link, you have to remove the "<Query>" enclosing tags from the query property.
Steve Jobs is dead. Long life to his ideas!
What to do when creating a new wsp in a Visual Studio 2010 SharePoint 2010 solution
- delete the created snk and add a reference to your global snk file (add existing item, Add As Link)
- from project properties, sign the assembly using the previously referenced strong name key file
- from project properties, choose the deployment configuration between Default and No Activation
- from project properties, disable the Auto-retract after deploying flag
- if not done during creation time, from the project properties set the site url
- add the needed references to the other assemblies in the solution
- unload the project file and add the tag needed to create the wsp file automatically, as described in my post Visual Studio 2010: how automatically build wsp packages after SharePoint 2010 build
- from package, advanced, add the assemblies you want to include in the wsp and deploy in GAC
- write one or more web-application scoped features, used to activate and deactivate the other features at site collection (SPSite) or site (SPWeb) scope
- if the wsp has not web-application scoped items, create an empy WebPart and a site collection scoped feature to be able to deploy the wsp to a single web-application, as described in my post SharePoint: how make your wsp deployable in a single web application