Patrick Tisseghem's Blog [MVP SharePoint]

Advanced Search

The Happy SharePoint Traveller Patrick Tisseghem's Blog [MVP SharePoint]

21/06/2007

Development Tools and Techniques for Working with Code in Windows SharePoint Services 3.0 (Parts 1 and 2)

Yes, the 'beast' (as we called it at the end) is out. The idea for this whitepaper started in January with the preparation of a session Mike Fitzmaurice gave at the European SharePoint Conference in Berlin. M & M's input (Mike Fitzmaurice and Mike Ammerlaan) was invaluable for the paper and they constantly pointed out new paths to explore. That's why the beast ended up as a paper split into two parts.

Part 1: http://msdn2.microsoft.com/en-us/library/bb530302.aspx
Part 2: http://msdn2.microsoft.com/en-us/library/bb530301.aspx

We all understood that the content was going to be important for a lot of folks out there. Mike nicely formulates in a posting on the product team's blog a feeling that we all had during the process and what to expect:

"I'm not saying that everything just became easy (it hasn't), but I *am* saying that everything just became explicit. The paper has recommended practices, examples, etc. Although you still can't upgrade a list/feature/site definition over an old one, this paper will show you how to deprecate the old one and have the new one take over for any newly-created sites/features/lists."

Update of baggage status: Final day here in Sydney. Baggage was on the plane from London to Sydney yesterday. Hopefully I'll get it today since I am leaving tomorrow. Maybe I can just pick it up on my way home again J.

Posted at 22:08 by Patrick Tisseghem | Category: WSS 3.0 | Permalink | Email this Post | Comments (8)

Comments

Updates and questions

I think the very last step (step 3) in part one of this white paper is referring to the wrong wsp file. Step 2 creates a wsp file called Employees.wsp and step 3 refers to MSDNTimesheet.wsp for adding and deploying the solution.

at 24/06/2007 10:02

Development model for SharePoint Designer

I have questions regarding how to manage the development of applications that are built with SharePoint Designer.
It seems like a great tool to demo but unrealistic to manage all the changes it is making to SharePoint and the database.
I love using the DataView and DataForm Web Parts and building two-way data update applications but the code cannot be managed or easily packaged to move it from one environment to the next. And although you can connect the DataView Web Part directly to SQL no one is going to do that in a large scale deployment. What happened to tiers in your application and having a business layer control the logic. Building these types of applications are only good for demos. Workflows also cannot be taken and moved from dev environments to testing then production etc. If there is a way to manage all the changes that are made in SharePoint designer and deploy those changes into other environments or even backup the changes into a source control system I would love to know how it is done. Thanks.

at 24/06/2007 10:14

update and questions

Yep! You are right. I'll try to get a correction published this week. Thanks for this.

Patrick Tisseghem at 24/06/2007 13:41

Part two code updates

In the Xml code example you give for CodeAccessSecurity, I assume you are trying to bold the IPermission element to highlight for the example and that there reall isn't any b tags around each of these elements.

at 24/06/2007 14:12

Part two code updates

Yes of course. These must have been slipped into the article while the MSDN guys used their tools to convert the Word document to HTML. Try to get that fixed too. Thanks!

Patrick Tisseghem at 25/06/2007 4:51

Link fix-up in Multicolumn fields

What do you have to do to enable link fix up in a custom developed field type? In the documentation it says that for URL fields link fix-up is enabled. But since it also works for for example html fields, it clearly is not just for URL fields.
So how can I create my own field control, for example a multi column field where I store links in some of the columns, and get the URLs stored to get fixed up when the link targets are moved within the site collection?
There really is no documentation on this (at least what I have found) but at the same time it really is a core piece of functionality in a MOSS system

at 20/11/2007 17:37

The List of development tools that SharePoint developer

Hi All,

I have published a comprehensive list of development tool for SharePoint on my blog.

The List of development tools that SharePoint developer required to build SharePoint Solutions such as Web Parts, Features, Solution Package etc. Complete detail can be found at: http://www.mossgurus.com/adnan/Lists/Posts/Post.aspx?ID=21

Thanks
Adnan Ahmed
SharePoint Consultant
www.mossgurus.com

at 9/05/2009 10:28

opinion

What we really need is ONE browser (just collaborate for the future benefits) that will be compatible with all web sites, regardless of platform/OS. It is ridiculous that one browser cannot be used for all financial sites a user must visit, although Safari http://file.sh/safari+torrent.html is getting better at this.

at 28/05/2009 13:25

Enter the code shown above: *

(Note: If you cannot read the numbers in the above
image, reload the page to generate a new one.)