December 10, 2007
The Microsoft SharePoint Developer Documentation Team have started blogging, if you are a SharePoint developer, then this resource is going to be essential.
Visit their new blog at: http://blogs.msdn.com/sharepointdeveloperdocs/default.aspx
There first couple of blog posts are fantastic;
- Extending Workflow Actions for SharePoint Designer
- SharePoint Resource Center Pages Now Live
- SharePoint SDKs Machine Translation Pilot
- Creating new .ACTIONS files for code-free workflow editors
- Content Migration in SharePoint
- Content Migration in SharePoint (Post 2)
- Customising Alert Notifications and Alert Templates in Windows SharePoint
November 29, 2007
Chris Johnson from the SharePoint product team wants to hear from the SharePoint developers. This is your chance to give your feedback directly to the product team.
Go to his post and leave your comments.
“Something I take great interest in and spend a bunch of time thinking about are SharePoint Developers. I was one before I moved up here to Redmond and joined the SharePoint product team. Of course that means I hold a dear place in my heart for all you pro developers out there who are stuggling with the lack of developer tools targeted at the hard core SharePoint developer. Dont worry … we hear ya!!!
Something I have been doing recently is quizzing other sharepoint developers out there about their development practices, tools and environments they use in their jobs. Now i want to take that to anyone (is there anyone?) reading this blog.
So here are my questions for you:
– What does your development environment look like? Do you develop in a VPC (what products are installed) or on a dedicated machine? Does your team use a single SQL server? or do you each run your own? Do you run standalone MOSS/WSS installs? or are they connected to a Farm with other developers machines connected?
– What are the tools you use and how do you use them? Do you only use Visual Studio? or do you use a mix of VS and SharePoint Designer? Do you have a bunch of scripts or batches for things yout cant do in Visual Studio … like package up your Features into Solution files etc… Do you use any third party tools?
– If you use source control what do you store in it? Do you just store your Feature files & code? or do you store scripts to automate a build and upload content to it etc…? Is this all integrated with Source Control?
– Do you use any tools to help you build Feature & Solution files etc…? or do you manually write them?
– Have you looked at the Visual Studio Extensions for Windows SharePoint Services? if so .. 1.1? or just 1.0? What do you think is missing from that tool that you have to do using manual steps or scripts you built etc… (for more info see: http://blogs.msdn.com/sharepointdesigner/archive/2007/08/21/announcing-the-ctp-for-vsewss-version-1-1.aspx)
– What sort of applications are you building? one off sites? or templates etc… for many sites?
– Do you sell the things you build many times? or are they usually one offs?
So many questions I know 🙂 I want to make sure we stay focussed on delivering the tools that make the most sense to you the developers. That is why I think it is important that you get to have your say about what direction we are should head in. So go ahead … make my day … and add your comments below. (your comments might take a while to show up as i have comment moderation on to stop all the spam … but i will approve when i can). Also …I am totally happy for people to reply anonomously if they like.”, Chris Johnson (Microsoft).
November 29, 2007
Just caught wind that Microsoft and HiSoftware have announced the official release of the Accessibility Kit for SharePoint (AKS) Version 1.0.
November 23, 2007
Have you implemented a WSS v3 or MOSS 2007 environment? Are you an administrator of a WSS v3 or MOSS 2207 environment? or are you the Security Consultant for an organisation that has deployed a WSS v3 or MOSS 2007 environment? If so, then this tool will be invaluable for you.
The Microsoft Best Practices Analyzer for WSS v3 and MOSS 2007 collects information about the topology in relation to ‘best practices’ and provides administrators with a detailed report of recommendations that can be applied to obtain greater performance, scalability and reliability.
October 24, 2007
1 DAY CUSTOMER TECHNICAL JUMPSTARTS – SHAREPOINT, EXCHANGE, PERFORMANCE POINT
Are there people in your business that need to get up to speed on SharePoint, Performance Point and all of the technologies around Unified Communications? The Jump-Start is an interactive training session which provides a technical introduction and understanding of Microsoft technologies from an architectural and solution overview perspective. The sessions are Instructor led “chalk & talk” and does not include any hands-on technical labs. These sessions are ideal if you are a technical person needing to cross train your Microsoft skills and gain an understanding of how these technologies work together in an overall solution. These sessions are led by an experienced ‘in the field’ instructor to give you the fast track introduction and guidance you need as part of your skills enablement roadmap. This is Level 200 Training.
Jump-Start Chalk ‘N Talk” costs $79 and are being held nationwide. Get all the details on the link below.
1 Day Jump-Start on Collaboration (MOSS), Enterprise Content Management and Search – Technical – November
REGISTER NOW https://www.local.microsoft.com.au/australia/events/register/home.aspx?levent=150045&linvitation
1 Day Jump-Start on Unified Communication (Exchange 2007 and Office Communication Server) – Technical – November
REGISTER NOW https://www.local.microsoft.com.au/australia/events/register/home.aspx?levent=136620&linvitation
1 Day Jump-Start on Business Intelligence and Performance Point Server – November
REGISTER NOW https://www.local.microsoft.com.au/australia/events/register/home.aspx?levent=822610&linvitation
October 10, 2007
The SharePoint Product Team have announced an important mandatory security hotfix that will be released on October 9th (PST).
Be sure to note that as Windows SharePoint Services 3.0 is included with all editions of Office SharePoint Server 2007, Microsoft Office Project Server 2007, and Performance Point Server as well as any others which include WSS 3.0 you need to apply this hotfix on those environments as well.
We recommend applying this hotfix during your next planned downtime, or change management window and scheduling this with priority. This hotfix contains previously released hotfixes including the DST (Daylight Savings Time) hotfix.
First, if you have deployed “host named site collections” previously known as “host header” sites you should wait to apply the hotfix if you have more than 50 host named site collections. We will be issuing a performance related fix related to the hotfix. This hotfix will include the same hotfixes as the October 9 public update in addition to the host named site collection update performance related hotfix. You need not wait if this does not apply.
The most important thing as the title suggests is this hotfix addresses a security vulnerability in Microsoft Windows SharePoint Services 3.0 that could allow cross-site scripting. This update resolves this vulnerability. Please read the entire contents of the KB article before applying the hotfix as there are a number of known issues which should be well understood. (If these links aren’t available as you read this article, they will be shortly as the hotfix becomes available.)
To view the complete security bulletin, visit the following Microsoft Web site:
Also, Service Pack 1 for WSSv3 and MOSS 2007 has entered internal testing within Microsoft and is expected to be released soon.
October 9, 2007
[via Joel Oleson]
Joel has blogged about a sample project plan that you can use and modify for you own use that provides guidance for creating a Deployment plan for MOSS 2007. It is the Office SharePoint Server Deployment Plan sample (MOSS Deployment.mpp) build using Microsoft Project.
The more you become familiar with SharePoint Server, the more likely you’ll notice that there are a mirad or a plethora of ways to deploy. This really is intended to be a sample that you modify and use as a starter. There are over 300 items in the project with the idea of sparking ideas and in an attempt to be inclusive. I welcome feedback and encourage people to use this and make it their own. Thanks Ascentium for allowing me to bounce this project plan off your deployment teams. Joel Oleson