Comments on Chris O'Brien: My favorite SharePoint 2007 development techniques...

@Bil, Yeah the tools in VS2010 are definitely bet...

2009-12-03T14:08:23.425Z

@Bil,

Yeah the tools in VS2010 are definitely better (note it's not badged as VSeWSS though as it's a completely different model/codebase). Be interesting to see how things play out with large scale 2010 dev though. Also interesting point about running from the command-line - I think this is possible by running dev.exe (VS2010) from the command-line and passing some switches.

Cheers,

Chris.

@Chris: I totally go with the WSPBuilder way (usin...

2009-12-03T03:41:53.338Z

@Chris: I totally go with the WSPBuilder way (using both the command line but specifically the VS plugin to start projects). It packages things up great, with the latest release you can put your own .config file in the root and control the output, etc. I use command line version for more complicated builds where I have 3 or 4 wsps then it's NANt and wspbuilder.exe. VSeWSS is just too unworkable IMHO. I may try to give it a chance in 2010 as what I've seen looks better, but it's still behind WSPBuilder (although it does have a few key features like reverse engineering a WSP/STP/site).

"If you have a requirement to log to a ShareP...

2009-10-08T16:08:02.024+01:00

"If you have a requirement to log to a SharePoint list, creation of a custom log4net appender is the way to go. I haven’t done this yet, and bizarrely it seems no-one else has (publicly)."

Chris, I've done this. It IS in fact quite simple. My appender writes to the SharePoint Trace Log.

If people are interested, contact me: info@sharepoint-tools.de or http://www.sharepoint-tools.de

cheers
oliver

Top, it has been out there for a while and some se...

2009-10-08T12:56:44.090+01:00

Top, it has been out there for a while and some sections require updating.

Regardless, if you have any specific remarks then leave them in the comments in the relevant post or drop me a line.

Thanks for pointing me towards IDesign, they have a WCF naming standards doc that is quite relevant to me at the moment.

@Muhimbi, Yep, the CRL trick deserves to be widel...

2009-10-08T12:48:51.095+01:00

@Muhimbi,

Yep, the CRL trick deserves to be widely linked :)

I haven't seen anyone publicly publish their SharePoint dev guidelines before, commendable move. Where I worked for a long time, we moved away from writing our own guidelines (for .Net at least) in favour of the IDesign guidelines, but with all the SharePoint specifics I've gone back to thinking it's better to have a single location to point developers to. The SPDevWiki does a good job, but obviously doesn't contain any policies relevant to your organization.

I'll take a read!

Thanks,

Chris.

@Einar, Good point - I might have omitted this be...

2009-10-08T12:13:44.855+01:00

@Einar,

Good point - I might have omitted this because it's just such a fundamental thing, but only the other day I came across a developer who was doing an IISReset each time.

I've also long used Spence's utility and WSPBuilder to do the job.

Thanks,

Chris.

@Nadège, Personally I prefer the 'one-to-one&...

2009-10-08T11:52:25.049+01:00

@Nadège,

Personally I prefer the 'one-to-one' mapping to the 12 folder that having WSPBuilder and a '12' structure in my VS project gives. In early releases (than 1.3 CTP), VSeWSS was far less flexible in some circumstances leading to criticisms it was too much of a 'black box'. I think some of this has been remedied, and it certainly does some things very well - but the other reason I prefer WSPBuilder is because it seems to be the most popular SharePoint dev tool - see Todd's unscientific survey at http://sharepoint.mindsharpblogs.com/Todd/Lists/Tool/summary.aspx. I like consistency from project to project, team to team, so ubiquity is certainly in WSPBuilder's favour.

Thanks,

Chris.

Good stuff Chris. I had a chat with Jaap yesterday...

2009-10-08T11:10:54.883+01:00

Good stuff Chris. I had a chat with Jaap yesterday and he mentioned your posting. I am seeing quite a few people linking through to our CRL article, so thanks for the 'Link love'

Your list, to some degree, matches what is in our SharePoint development Guidelines (Free download at http://www.muhimbi.com/blog/2009/05/muhimbis-sharepoint-development.html). I hope we don't need to overhaul too much of this when SP2010 is out.

You should add that recycling application pools, r...

2009-10-08T10:42:41.845+01:00

You should add that recycling application pools, rather than pulling a brute force iisreset, significantly improves redeployment times as well :)

Recycling is simple, using WSPBuilder's Visual Studio addin; Harbar's tray util (http://www.harbar.net/articles/APM.aspx); or a console app of mine (http://dl.getdropbox.com/u/1878671/iisrecycle.zip (includes source)).

Hello, Your post is very interesting. I'd ju...

2009-10-08T09:34:07.416+01:00

Hello,

Your post is very interesting.
I'd just have a question. Is there a special reason not using VSeWSS in order to package and deploy your solution/feature ? Do you meet some problems with VSeWSS that decide you not to use it and use WSPBuilder instead ?

Thanks for your post and your response.