Man, I feel like a small child, I'm getting so excited!! Anyway, download the beta here:
At the time of writing the Beta 2 bits of 2007 Microsoft Office System are not yet available for download, but on the Microsoft download center you can already find some 2007 Office System related stuff:
- 2007 Office System Beta 2 Administrative Templates (ADM)
- 2007 Office System: How Do I ScreenCasts
- Visual Studio 2005 Tools for Office Update: InfoPath 2007 Beta Support
- 2007 Office System Document: UI Style Guide for Solutions and Add Ins
- 2007 Office System Document: Lists of Control IDs
- 2007 Microsoft Office System Beta: Send a Smile to Office Feedback Tool
- Project 2007: Software Development Kit
[Via Patrick] The release of Beta2 for the 2007 Microsoft Office System seems to be imminent. The SDK's for Windows SharePoint Services (WSS) and Microsoft Office SharePoint Server (MOSS) are ready to download.
- Windows SharePoint Services V3: Software Development Kit
The Windows SharePoint Services V3 (Beta) SDK is a preliminary release for solution providers, independent software vendors, value-added resellers, and other developers to learn about the new Windows SharePoint Services platform. It features conceptual and "How to" articles, sample code, and preliminary programming references. The Windows SharePoint Services V3 (Beta) SDK will be updated for the released version of Windows SharePoint Services V3.
- SharePoint Server 2007: Software Development Kit
The Microsoft Office SharePoint Server 2007 (Beta) SDK is a preliminary release for solution providers, independent software vendors, value-added resellers, and other developers to learn about the new SharePoint Server 2007 enterprise application and platform. It features conceptual and "How to" articles, sample code, and preliminary programming references. The Microsoft Office SharePoint Server 2007 (Beta) SDK will be updated for the released version of SharePoint Server 2007.
- Windows SharePoint Services V3: Software Development Kit
I love reading SmartPart success stories! Matt Ranlett has a nice one: "So I've just wrapped up a quick little demo of how easy it is to code for SharePoint. Since the focus is on easy, and they're not yet 100% sure if we'd be using SharePoint vs a make-your-own ASP.Net 2.0 site, I decided the best way to go is to use the SmartPart and show off how you can write normal old ASP.Net code and still get it to show up in SharePoint. Since we're thinking about an ASP.NET 2.0 site and everyone wants to write ASP.NET 2.0 code, I really had to use the Son of SmartPart, which includes the ability to display 2.0 User Controls and 2.0 Web Parts in SharePoint. Since this is only a demo, I knocked up a quick little user control that replicates a report we have here. To get SoSmartPart to "see" a user control, all you have to do is drop the .ascx into a UserControl directory on your SharePoint server. I did that and PRESTO! My control shows up in the list of available user controls in the SmartPart toolbox area. I select the desired control and hit Apply. BAM - error.
It turns out that you can't use the easy drag/drop data access components in a UC and get it to show up in SharePoint - maybe it has something to do with how the page gets rendered. Whatever. Change all those components to ones created dynamically in code (what's that, 5 lines?) and everything started working. I showed this off to my demo audience and everyone is deeply impressed with how easy everything is.
Then I tell them that we can use ASP Web Parts in SharePoint - which gives us the flexibility to move to a ASP.NET 2.0 site if SharePoint gives us unexpected trouble. And that the next version of SharePoint will be able to use ASP Web Parts natively without this SmartPart layer... They love it. I guess development will start soon."
Thanks Matt! A tip when you use the drag/drop data access controls and components: probably the connection string was will be saved in the web.config. You need to add it manually to the web.config of the SharePoint site. Let me know if you have any problems.
Next month I will present a session on Office 2007 Client Programmability. Registration is free, so register yourself at the MSDN Belux site!
MSDN Evening on Office 2007 Client Programmability
There is a lot of talk about the new user experience available with the forthcoming Office 2007 client products. But this is not the only innovation in Office 2007. Office 2007 introduces a whole set of new extensibility scenarios for both power users as well as for professional .NET developers.
Join this session to get a 2-hour overview of the most important techniques. We will start with the innovations at the level of the file format. Storing our documents as ZIP/XML-based files will enable plenty of new business scenarios. Then we will show you the new ways of storing XML data into Word documents and use the new content controls to bind to this data. Visual Studio Tools for Office 3.0 is the environment for .NET developers for extending Office 2007 clients both at the document-level as for the application-level. We will cover the building of smart documents for Word and Excel and the creation of (cross) application-level add-ins extending the user experience with custom ribbons and custom task panes. To conclude, an overview on the new ways of extending Outlook 2007 is on the agenda covering the consolidated object model and extensions via form regions.
When & Where
• Thursday, June 22, 2006 from 18.00 till 20.30
• Registration starts at 17.30
• Lamot Congres- en Erfgoedcentrum, Mechelen
[Via Mike Diehl] Hehehe, I like this one! But it's also very true: think about your schema's, get people involved and get them to think about the schema's as well. This will save a lot of time (trust me: been there, dont that).
Thanks to Maurice we know that WSSv3 has been signed off Beta 2 last Monday. Also the last few days quite some Microsoft guys and girls have been raving about the fact that Word 2007 Beta 2 can be used to create blog posts. So the whole SharePoint and Office community is holding their breath for the moment Beta 2 will be available to download. Officially there is no fixed date but Don (another MS employee) gives us another hint (and I quote): "This is in Beta 2 which will be available externally in the next week or two". Let's hope this information is accurate! :-)
[Yet Another SharePoint Relief Series] One of the pain points of SharePoint 2003 (especially Windows SharePoint Services), is the lack of navigation possibilities. It’s quite hard to find out which sub sites are created under a WSS site. Also when you’re on a WSS site, you don’t have any clue or way to navigate to the parent site hierarchy. With a small amount of customization however, it’s possible to solve these issues. In my SharePoint classes I always show how to create a breadcrumbs web part and drop-down navigation web part. For a pre-fabricated solution, check out Tom’s tree navigation web part. In SharePoint 2007 these web parts become obsolete, navigation is available everywhere. First of all, breadcrumbs are everywhere! Take a look at the screenshot below; it’s displaying a Contact list on a site. Notice the breadcrumbs to navigate back to the site.
Last month I spent some time with a customer discussing their SharePoint implementation, during these sessions they brought the following product to my attention: 80-20 Retention Server. It has been available for a couple of months (I know I’m a little bit behind compared to my fellow bloggers Mark and the other Mark, but it’s interesting enough to mention once again. Basically 80-20 Retention Server is a product that handles the life cycle of documents stored in SharePoint 2003. 2007 Microsoft Office System is still quite far on the horizon, so this product nicely fills up the gap. I haven't got any hands-on experience, but it looks very promising!
Jelle has released the long awaited version 1.1 of his InfoPathHelper component! This version fixes a nasty bug that appears when caching data from a web service. Check his latest post for the download and the source code.
[Yet Another SharePoint Relief Series] In SharePoint 2003 you can enable versioning for a Document Library, so SharePoint will store for each document in that library previous versions when the document gets edited. That’s nice, but that’s about it what you get out-of-the-box. Since each version of the document is in fact a complete document (it’s not the delta that’s stored for a version) big documents can take up more space than desired. Just imagine that you have a 1MB Word document for which you have 15 versions, the total size that the document item will use, is 15 MB (15 times 1 MB). So a very common request is to limit the number of versions that is stored in a document library. In SharePoint 2003 there is no out-of-the-box functionality to do that, although it’s quite easy to write a Document Library Event Handler to accomplish this, but you do need to write some code and deploy the solution.
[Yet Another SharePoint Relief Series] If you know a little bit about SharePoint 2003 you probably are aware of the fact that you can add custom columns to a SharePoint List or a Document Library. For example you can add an Importance column to a Document Library so each document in that library can have an Importance value. Probably if you want to do this nicely, you create Choice column so users can select the value for the Importance field from a couple of predefined values (e.g. Important, Very Important …). So far so good, this works fine in SharePoint 2003. But suppose you would like to have this Importance column also in another Document Library or in another List. The only option that you have in SharePoint 2003 is to repeat the creation of the field for the other Lists or Libraries (including defining all the different Importance values). In SharePoint 2007 you can avoid this repetitive work by using a new feature called Site columns. When you navigate to the Site Settings of a site, you’ll see a link called Site columns.
If you have been working with SharePoint 2003 you probably know the abbreviation YASQ which stands for yet another SharePoint quirk. Those quirks seem to be insignificant at first sight, but they are so important to be aware of if you don’t want to run into serious problems. Just imagine that you (or your sales person) have sold document level security in a content management system built on top of SharePoint 2003. :-)
Now it’s getting really funny: head hunters are looking for SharePoint Consultants who know how to use the SmartPart. So if you know the SmartPart, and if you’re looking for a new job the following ad.
Remark: in general in don’t publish job offerings on my blog (unless if my company is looking for people, and they still are!), but consider this one as the single exception. Btw, I'm not affiliated with the company offering this job or it's client.
Our client, a leading Microsoft Gold partner is currently looking for a sharepoint Consultant to work on a high profile project. This is an excellent opportunity to work on a fantastic project with Microsoft's latest technologies. In order to be successful you must have experience with Sharepoint preferably smartparts - not essential. Experience with Biztalk is a massive bonus also. We are looking for an experienced professional with extensive experience in development, Web parts, administration and configuration. Any commercial experience of architecture is a plus. An all round knowledge of .NET technology is a must. Please apply without delay as this is an immediate start (however, notice periods are fine).
Start Date ASAP
Employment Agency E-Synergy Solutions
Contact Daniel Ankah
Telephone 0207 444 4088
Fax 0207 444 4099
Posted Date 30/04/2006 10:57:43
More info here: http://www.jobserve.com/W9168E77E66A8C5D9.job
When talking to customers about the new version of SharePoint, a lot of questions I get are related to moving the existing infrastructure and data to the new version of SharePoint once it gets released. For now there wasn't a lot of (public) information available, but now Joel Oleson has written a nice post about the topic. There are actually three scenarios:
Since the last couple of weeks I’m spending again some time with BizTalk. Although there is no official training material for BizTalk Server 2006 available yet, U2U is already offering BizTalk 2006 training. So it was about time to upgrade my BizTalk Server 2004 skills!