Sunday, August 26, 2007

What's good and what's missing from WSS Visual Studio Extensions 1.1?

The Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions, Version 1.1 CTP were released, with
"Support for 'Web Solution Package' editing, List Instance item template ,List Event Handler item template,Bug fixes", so I decided to take a quick look at what's in the web part project template.

First, I liked the fact that now by default when you create a web part project you don't get the "Render" event that you used to get in the past. This caused many developers to start writing html in the Render event, and then be puzzled when the events on controls didn't work (see Server side controls and data binding in web parts in this blog).

I am still looking into it, but one thing that I would expect from a webpart project template is a wizard when creating the project that asks:

  1. Do you want the web part to support connections? (add stubs for connection interface)

  2. Do you want the web part to connect to a specific list? (add properties and functions to connect to a list)

  3. Do you want a custom toolpane?

What do you think? what else would you want from a template?

1 comment:

Anonymous said...

The "Would you like a connectable webpart..." idea seems pretty neat. I'd like that... although I've only once really needed to write connectable webparts...

I like the fact that these new templates provide support for VB(even though i now only work in C#) and I also really like the fact that it doesn't cause an iisreset every time. Also the WSP view is fantastic. (Having control over the feature files etc.)

I would just like this new template to not create a new project named WebPart1 (even if i change the solution name). The previous Extensions didn't do this - the webpart had the same name as the solution name. What's up with this? Still haven't figured this out. I can't seem to deploy my webpart since the previous one named webpart1 is already deployed in the solution store...

How do I change this WebPart1 name? sigh...