SharePoint Dragons

Nikander & Margriet on SharePoint

Tag Archives: sharepoint

The SharePoint Dialog Framework Wiki page

Check out and improve the following Wiki page containing the top resources about the SharePoint Dialog Framework:
http://social.technet.microsoft.com/wiki/contents/articles/7885.sharepoint-2010-resources-about-the-sharepoint-dialog-framework.aspx

The MVP pattern in web parts

Check out and improve the following Wiki page containing the top resources about implementing the MVP pattern in web parts: http://social.technet.microsoft.com/wiki/contents/articles/7884.sharepoint-2010-building-a-web-part-that-implements-the-mvp-pattern.aspx

SharePoint 2010 Dialog Framework

The SharePoint 2010 is quite a hot topic, and this is a nice blog post explaining the essential stuff you need to know: http://blogs.msdn.com/b/vesku/archive/2010/02/25/how-to-sharepoint-2010-js-client-object-model-and-ui-advancements.aspx

Setting the SharePoint context to null

We came across an interesting, what shall we call it, hack we guess. Suppose you have a scenario where you execute an HTTP POST and try to change something in the SharePoint content database. If you don’t have a valid FormDigest control, you’re in trouble. Apparently, there’s a hack available. If you set the HTTP context to null, the code will be treated as running from outside the Sharepoint context (e.g. from a timer job or a console application) which makes SharePoint refrain from doing a FormDigest check (http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.webcontrols.formdigest.aspx).

var ctx = HttpContext.Current;

try { HttpContext.Current = null; siteCollection.Add(…); }

finally { HttpContext.Current = ctx; }

The hack is described here: http://social.technet.microsoft.com/Forums/en-US/sharepoint2010programming/thread/4f710dda-e5a4-4a56-8570-267aceff8d11

Adding items to SharePoint 2010 thru REST

We’ve found that it’s a common request that people want to add items thru REST. And may we add that REST in SharePoint turns out to be a lot more popular than we expected. Here’s a cool blog post that shows how to add items to SharePoint 2010 via REST: http://blog.tedpattison.net/Lists/Posts/Post.aspx?ID=12

SharePoint Foundation Help Search

Ever noticed a crazy little thing called the SharePoint Foundation Help Search feature? If you activate it, the Help button next to the search input box will navigate your custom help content instead of MS online help. Here’s how you set it up: http://office.microsoft.com/en-us/sharepoint-foundation-help/add-custom-help-to-a-site-collection-HA101833141.aspx

Migrate IManage to SharePoint 2010

In case someone was looking. Now there is an option to migrate iManage WorkSite to SharePoint via OrbitMigrate from Galaxy9:

http://www.galaxy9.com.au/attachments/article/45/ILTA%20OrbitMigrate%20Flyer.pdf

SharePoint 2010: resources for claims authentication

Just started a Wiki page about resources for claims authentication:

http://social.technet.microsoft.com/wiki/contents/articles/7837.sharepoint-2010-resources-about-claims-authentication.aspx 

You sure are welcome to take a look at it because it sure needs some filling!

SharePoint 2010 testing

SSRS infrastructure in SharePoint 2010 integrated mode

We get asked regularly what the SSRS infrastructure looks like in SharePoint integrated mode. Well, like this:

– On the clients: rich clients optionally leverage the ReportViewer Windows Forms control, ASP.NET pages use the ASP.NET ReportViewer Web control.

– On each SharePoint WFE, you need to install the Reporting Services add-in. Every WFE also contains a report viewer web part, reporting pages to manage SSRS, and a proxy that communicates with the report server.

– On the middle-tier: SSRS can run as a true middle-tier application that doesn’t have to (but can) be hosted on a WFE. The middle tier contains the report server itself.

– Data tier: the report catalog, report data, report server config files and registry, entries in the SharePoint config database, reports stored in the SharePoint content database.

In other words, in production you do need to be able to access reports in a reports library,

None of the above options. If you’d take a look at the SharePoint 2010 Administration’s Companion by MS Press, it contains a truly awesome chapter about SSRS and PPS (just bragging, ’cause I wrote it myself :-), and it clarifies the point:

– On the clients: rich clients optionally leverage the ReportViewer Windows Forms control, ASP.NET pages use the ASP.NET ReportViewer Web control.

– On each SharePoint WFE, you need to install the Reporting Services add-in. Every WFE also contains a report viewer web part, reporting pages to manage SSRS, and a proxy that communicates with the report server.

– On the middle-tier: SSRS can run as a true middle-tier application that doesn’t have to (but can) be hosted on a WFE. The middle tier contains the report server itself.

– Data tier: the report catalog, report data, report server config files and registry, entries in the SharePoint config database, reports stored in the SharePoint content database.

Details can be found in the SharePoint 2010 Administration’s Companion by MS Press, it contains a chapter about this topic which is truly amazing (just bragging, cuz we wrote it ourselves).

 

We get asked regularly what the SSRS infrastructure looks like in SharePoint integrated mode. Well, like this:

– On the clients: rich clients optionally leverage the ReportViewer Windows Forms control, ASP.NET pages use the ASP.NET ReportViewer Web control.

– On each SharePoint WFE, you need to install the Reporting Services add-in. Every WFE also contains a report viewer web part, reporting pages to manage SSRS, and a proxy that communicates with the report server.

– On the middle-tier: SSRS can run as a true middle-tier application that doesn’t have to (but can) be hosted on a WFE. The middle tier contains the report server itself.

– Data tier: the report catalog, report data, report server config files and registry, entries in the SharePoint config database, reports stored in the SharePoint content database.

In other words, in production you do need to be able to access reports in a reports library,

None of the above options. If you’d take a look at the SharePoint 2010 Administration’s Companion by MS Press, it contains a truly awesome chapter about SSRS and PPS (just bragging, ’cause I wrote it myself :-), and it clarifies the point:

– On the clients: rich clients optionally leverage the ReportViewer Windows Forms control, ASP.NET pages use the ASP.NET ReportViewer Web control.

– On each SharePoint WFE, you need to install the Reporting Services add-in. Every WFE also contains a report viewer web part, reporting pages to manage SSRS, and a proxy that communicates with the report server.

– On the middle-tier: SSRS can run as a true middle-tier application that doesn’t have to (but can) be hosted on a WFE. The middle tier contains the report server itself.

– Data tier: the report catalog, report data, report server config files and registry, entries in the SharePoint config database, reports stored in the SharePoint content database.

Details can be found in the SharePoint 2010 Administration’s Companion by MS Press, it contains a chapter about this topic which is truly amazing (just bragging, cuz we wrote it ourselves).

 

Follow the WIKI page at: http://social.technet.microsoft.com/wiki/contents/articles/7825.sharepoint-2010-ssrs-infrastructure-reporting-services-integrated-mode.aspx