For the last couple of weeks we’ve been thinking here at Imtech ICT Velocity about how we could improve our SharePoint development process. During the last year we have gathered a lot of different tools which help us to automate the routine. And while they all are definitely very useful, they make the development environment quite complex. Maybe even too complex. One of the improvements we thought about was integrating all these different tools we have made into Visual Studio. Imtech Fields Explorer is the first one to go.
Recently, while working on a new tool for converting XML files using XSLT I have noticed something odd: Visual Studio (VS) 2008 wouldn’t display the contents of the converted XML files!
While working with Control Adapters in either ASP.NET or SharePoint 2007 you will quite often want to intercept the output of the parent control and modify it before rendering. As retrieving the output is the same for each and every control I have created the following code snippet:
Recently I've been looking at various extensibility possibilities of Visual Studio 2008. After having successfully done a proof of concept I have thought, that ideally, I would never want to have to leave my development IDE while working on a SharePoint solution. Preferably I would like to have all the tools I need and all the shortcuts inside Visual Studio and run them with one single click. Wouldn't the life be great?
I create very often little projects to try things out: either based on the Console Application or the Class Library template. As it's SharePoint development we're speaking of the first thing you need to do is to add references to the Microsoft.SharePoint assembly. Depending on what you're doing you might need to add the references to System.Web and Microsoft.SharePoint.Publishing as well or maybe even more. You can do it just the regular way by clicking with right button on the project References and adding new reference but there is a faster way.