Here is a link to a SharePoint resource centre created by Rackspace. It has got some great tutorials by MVPs and other useful tid bits, enjoy!
SPCAF – SharePoint Code Analysis Framework, is in its first public release. It provides a number of options to analyse code against best practices from a number of perspectives and roles (Admins, developers, architects and quality managers) within a SharePoint environment. Here’s some more detail on the release.
Personally, coming from a developer background I always have leaned towards using ASPX as it has provided me with the flexibility to create custom forms when using SharePoint. I think the main reason is the familiarity and there is no learning curve as it is based on something that becomes second nature. But over recent years I have moved away from coding and focussed more on what SharePoint can provide out of the box. InfoPath provides a good alternative for users of all types to create forms quickly and has some rich features which can be utilised. I have always looked at this subject with my ‘developer hat’ on but now as a Consultant/Architect I think the best solution should always win …
Here is a breakdown of the key features and benefits of using each:
A good article on running BizTalk Unit tests using TFS:
As part of the current project I’m working on, I needed to create a data view which passed a querystring parameter into a data view web part to display filtered data. The idea was to export this data to Excel using the export feature on the office ribbon available on SharePoint 2010.
To create the the view and apply the filter was very simple. I used SharePoint designer 2010, created a new web part page and inserted a data view. I re-arranged my columns and then applied the Query string parameter filter to the view. When I tested the view, it worked nicely. So the next step was to export the data to excel. This didn’t seem to work… so I was left scratching my head…
<button onclick=”exportToExcel();”>Export to Excel File</button>
To find the table Id click here
So this worked, but there is a few gotchas:
Thanks to the guys on MS SharePoint forums!!
I came across this error when I was testing a workflow built using SharePoint 2010 Designer:
‘The workflow could not update the item, possibly because one or more columns for the items require a different type of information’
SharePoint Designer workflows (in my experience) don’t really provide any meaningful error messages. So I did a quick google (as you do 🙂 ) and found this article –
It described the problem I was having so I tried the resolution and hey presto, it worked!!
It basically suggests rather than using an Update List Item Action on the current list, use the Set Field in Current Item Action as it prevents Sequential workflow errors.
Thanks to Anthony Clegg and Happy workflowing!
I was looking around the web for news of the latest version of BizTalk (I know I’m a little late to the game) and came across this lovely article:
It highlights the three focal points for BizTalk Server 2010 R2 (I’m sure they will change the name to suit the actual release year…) listed below:
The first two are a common scenario as Micrsoft tend to build and improve on what already works well. The last option is an interesting development but not unexpected. I am looking forward to seeing how BizTalk will adapt to cloud computing. Watch this space for more news!
When adding web parts to a page (especially custom developed web parts), the page can stop working due to errors in the web part. I have expereinced this many times when you install a web part for the first time. Deleting or removing the web part can be difficult when this type of error occurs. Fear not, there is a back door, to removing this rogue web part. On the end of the URL of the page add “?contents=1”. This will bring up a maintenance page allowing you to close or delete the web part that has not worked as intended.
Happy SharePointing Y’all 🙂
Thanks to Raam’s Blog
So there I was, a project purely to be developed without code, a former coder’s worst nightmare! I came across a slight issue where I needed to allow certain users access to edit fields on a form and others to view. The following article helped a bundle:
It was written for SharePoint Designer 2007 but still applies for 2010 🙂
Thanks to Josh Gaffery …