I went on course 2014B, with the exception of the security section of this course it was a waste of time. For developers with something about them all you need is this document to get you going and more
http://www.sharepointcustomization.com/resources/whitepapers/Web%20Parts2003.pdf
I’ve been experimenting with custom web part menus and custom toolpanes and its all in this document.
I was told this couldnt be done, you have a web part that requires personalisation but the designers do not want this web part to go on the My Page its to go in an area they choose but the client needs to configure the settings.
If you set the storage mode to personal, and place webpart in a zone in SPS, there is no ability to change that setting. If you try and force it in code it goes bang. If you load the property pane using script for personal then it errors with a naughty boy error you dont have permission to do this.
It is possible to allow this for web parts but you have to do something more evil to acheive it. You have to edit the area template find the zone you want to allow personalisation and change the AllowPersonalisation to true. So you can save your personal property, but you now have give the user control over the look of your SPS area, something far worse than not having a property.
Dont have an answer to this, considering the properties I want to store are user related an extension to the user profile may be possible, scary but possible, or I store this in a custom database and roll my own property.
Anyone who knows how to fix this let me know to work how I want it to without allowing users to create there own view of an area in sps let me know.
About to rebuild my machine again and need to create a desktop 2003 server
http://www.msfn.org/win2k3/misc.htm
Handy url with details how.
With web parts there is a special way in which to place resources in the correct folder and have the part deploy and reference them.
Take an image for example. Just drop the Image into the Root of the web part project (no need to separate it into separate folder unless you have lots of course or want to).
This example has a Traffic.jpg in the Web Part Project.
In the manifest is the following :
ClassResources>
ClassResource FileName=”Traffic.jpg”/>
/ClassResources>
The class can reference the href like this :
this.ClassResourcePath + “/Traffic.jpg”;
To give a Web Part a custom Icon then create a 32×32 gif/png/jpg (pref. gif for transparency), It is displayed at 16×16 though. Make an entry for it in the ClassResource Section, then in the DWP:
PartImageLarge>_WPR_/ICO32.gifPartImageLarge>
Notice the _WPR_, this is automatically replaced by stsadm with the wpresources path (which is the ClassResourcePath) for the specific web part, as this is where it gets deployed.
There is also a PartImageSmall setting which I couldn’t get to work, not enough time to play with it though so I stuck with this.
So you have your web part and you want to pre-configure the height of the web part at time of deployment, rather than have the support department have to set the height everywhere your part has automatically been added etc.
I found this Gem on how to create preconfigured custom properrties here
http://weblogs.asp.net/mnissen/archive/2004/05/20/135744.aspx
and just adpated it for Base properties (with a slight bodge), there may be a better way but I don’t have time to find it (I did try overriding/new the Height property but it wouldn’t have it).
In your web part code create a custom property for DefaultHeight in your class e.g.
[DefaultProperty("TeamName"),ToolboxData(""),
XmlRoot(Namespace=http://www.BinaryJam.com/HelpDeskWebParts/TeamWebPart)]
public class TeamWebPart : Microsoft.SharePoint.WebPartPages.WebPart
{
[Browsable(false),DefaultValue(defaultText),WebPartStorage(Storage.Shared)]
public string DefaultHeight{
get {
return this.Height;
}
set {
this.Height = value;
}
}
}
Then using the techniques described in the blog entry, enter the following line in the DWP file.
DefaultHeight xmlns=”http://EonUK/Oberon/RemedyWebPart/TeamWebPart”>150DefaultHeight>
When deployed this has the effect of Setting the Height of the Part to 150 pixels.
This technique could be used for width or any of the base properties exposed by WebPart.
Custom ToolParts can be really useful when you need to say select an item froma dropdown list whose data is stored in a WebService. Thats how I’ve useed them before.
But Consider using them for more than that. I created a new one, it has no properties to update or show, it just displays the Version number of the Assembly and the current user viewing the properties. Im going to extend it to display a host of other useful support information
Whilst customising our SPS installation various people were complaining of all the admin links down the left hand side.
So we thought about removing them, but how do you then edit.
I stumbled across configurator, really handy to see what can be done when customising area templates, and I remembered that this had removed all the admin links like change settings.
Well it hadnt removed them it just ensured that these links only appeared when in edit mode, a much better solution (why is this notthe default ?)
So the items for your <spswc:toolbar> that need hiding can have the value “EditOnly” instead of Both. Don’t ask me what the other value is.
Thanks to Stuart Estell for assistance on this one.
S’funny how you find the articles you need after you find another way to solve the problem.
But for those who want to use the combined web method.
http://support.microsoft.com/default.aspx?scid=kb;en-us;837376
Not sure I like the sound of some of their “fixes”.ÿ Whislt for us developers this dual natured development box is required its not advisable to do it in a live scenario, and yes I know Application Pools etc etc but when you get down to it your apps are going through a different http handler or if you make the changes listed looks like sharepoint does.
Developers are going to be the experts in Sharepoint, the amount of under-the-hood messing we have to do to get things working expose us to a large proportion of Sharepoint. So wouldn’t it be a good idea if our boxes were, not identical, but closer to how it would be deployed in live.
For those who are going to deploy apps/sharepoint combo, I hope you have your Advil handy.
ÿ
I may be wrong but this, to me, looks like an SPS installation
http://www.greatwesthealthcare.com
I cant tell if its WSSor SPS, but I didnt think the licening model allowed for SPS installs on the internet.
But the larger question is, for the functions that this site offers, WHY ? Why use sharepoint at all, would not CMS be better ?
If anyone knows please enlighten me.
Its very pretty by the way and does show how you can change an area template.
Well I’ve done that SPS build to another machine now and all seems well.
I had a combined SPS/WSS and Application installation. WSS install was to my default web which had loads of existing applications in it. I had manged paths in sharepoint to to make this work in this scenario. My wwwroot folder was on drive D: also so my changes reflect this.
So Heres exactly what I did.
Had some problems with stsadm not working against my sites whan adding a webpart, this is because I created my portal before the host-header rename. So before you do this to enable it to work you have to DELETE ALL SITES, than after this Create a new SPS site. (The same probably applies to WSS as well)
The best approach is to have all the Virtual Webs in place before installing WSS/SPS, but admittedly I havent tried this installation yet so cant advise on it, I will have to soon when I get some new more powerful kit. My 1.4mhz processor is creaking a little under all this strain.
- Create a new folder d:\intepub\wwwscarepoint
- Copy the aspnet_client script folder into it (not sure if needed, but safe than sorry)
- Copy the Web.config file from other wwwroot into here.
- In IIS change default web home directory folder to scarepoint folder (this is the Virtual web that has sharepoint installed in it, if you installed it elsewhere dont do it to default web, infact if you did it elsewhere you probably solved this problem anyway).
- Rename the Default Web Sharepoint (aethetics)
- Remove any Virtual Directories you have in here that you no longer want in here, take care IIS deletes can delete the source too not just the VD. Cant rememeber what circumstances though.
- For the Sharepoint IP address add a host-header for port 80 I used Scarepoint
- If you have control over your dns then enter an alias for your scarepoint url, if you dont you can put one in the hosts file for 127.0.0.1. (If you don’t know how to do this, why are you in web development again ? )
- Create a new WEB and call it Default Web, point it at your wwwroot folder, ensure you have the correct Application Pool.
- Reset the directory security you want
- Add any additional default documents you may have
- In the wwwroot folder return your web.config to its original state, minus sharepoint settings ! (This made my Session problems go away).
And thats all, everything seems to work now, sharepoint, my apps, and most importantly Visual Studio/IIS integration.
DO NOT DO THIS UNLESS YOU ARE PREPARED TO HAVE IT GO WRONG AND YOU NEED TO REBUILD. DO THIS AT YOUR OWN RISK.