Code Plex – SharePoint PowerShell Wizard
This project is intended to help with generating PowerShell scripts from your SharePoint environment. Often you have to generate PowerShell scripts to help script your environments, but getting started is sometimes tricky. This Farm Feature can be deployed to a development farm and be used to help generated some of the basic scripts needed.
http://sppowershellwizard.codeplex.com/
Code Plex - SharePoint Event Receiver Manager
This SharePoint feature allows you to add and remove event receivers to a list/document library using the SharePoint web interfaces. Check the download and documentation on Code Plex.
http://speventreceiver.codeplex.com
Code Plex – SharePoint Resource File Helper (Beta)
This application provides a simply mechanism to merge and manage resource files. This first version is very simple and I’ll be extending with more features!
http://spresourceshelper.codeplex.com/
Code Plex – SharePoint Url Shortener (Beta)
This Feature adds the ability to create short urls for use within your SharePoint site, making it easier to share urls!
Hi
Regarding your developer tools. Would your recommend using TypeMock for all SharePoint 2010 and 2012 development both client side and server – I had thought you had prviously listed it here. The reason is I’m putting a new developer rig together and I thought I should inital unit/mock test as opposed to psueodo uint/integration testing would be a good habit to adopt. I am having to write more code these days and I don’t want any nasty surprises down the line.
Hi Daniel,
If you’re keen to incorporate unit testing into your SharePoint code then I would say TypeMock is a good way to go. I’ve tried a number of other unit testing tools with SharePoint and whilst they offer some degree of testing, it always felt too abstracted from the SharePoint API. I found using TypeMock meant I could good get much more granular code coverage, testing my calls the API which is what I was looking for. You have to make sure any tests and mocks you setup are right, but that’s the same with any mocking based framework. The fact that TypeMock will generate the mocks for you is a big help. I know some people prefer to provide wrappers around the SharePoint API, and then only unit test those wrappers and assume that the SharePoint interaction works. Personally, I don’t like taking just that approach.
I hope that helps
Adam
Adam
Thanks for the follow up advice . I might bump into you next sat., either at the event or more likely in the pub afterwards!