1. To a SharePoint Form Library. (Requires direct access to the SharePoint environment from Infopath 2007)
2. As a SharePoint content type. (Requires direct access to the SharePoint environment from Infopath 2007)
3. As an administrator-approved form template. (Requires permissions to the central admin site for deploying the form template)

Last week we had our first SharePoint 2010 event. We had four interesting sessions that covered topics like Social networking, SharePoint 2010, Office 2010, Fast search and migrating a 2007 environment to 2010.

The first session was about Social Networking and presented by Rene Jansen from WinkWaves. Rene is a very experienced and enthusiastic presenter. He learned us the way communities work and how they can be incorporated in real life business scenarios. You can find the slide deck here.

The second session was about SharePoint 2010 and Office 2010. It was presented by Bart Wessels from Microsoft. Bart explained to us all the beautiful new capabilities in the SharePoint- and Office 2010 product line.

The third session was about Fast search in the SharePoint 2010 platform. About a year ago Microsoft completed its acquisition of Fast search & transfer. This product offers powerful enterprise search capabilities combined with the SharePoint 2010 platform.
This session was presented by Astrid van Raalte from Microsoft and Adriaan Hondelink from Content Strategy. You can find the slide deck here.

Last, but not least our MCM colleague Robert Jaakke presented the migration scenario from a SharePoint 2007 platform to 2010. You can find the slide deck here.

Up to the next SharePoint event. Please check back on our website regularly for any upcoming events.

Ciao,
Niels

Yesterday I ran into a situation where I really got to know CAS.
I had built a webpart that loads an ASCX control dynamically (it uses Page.LoadControl("")). Since we all develop in Full Trust (right?), that is of no problem.
As I was preparing my webpart to be handed over to the IT Pro's, I added all CAS permissions necessary to my Manifest.xml file.

I created the WSP file, used SharePoint Solution Installer (SSI) to deploy my package and voila. It gave me an error: File /_controltemplates/mycontrols/MyDemoControl.ascx can not be found.

I verified whether I added FileIO permissions. After a long search I found out that using Page.LoadControl("controlname") needs more than that. It needs Full trust. My webpart (and I guess yours too) have the Allow Partially Trusted tag in the Assembly.cs file. Partially trusted... Full Trust.
Full trust can be set by using the attribute Unrestricted="True" in the node PermissionSet.

I did some testing in my Manifest.xml, adding Unrestricted="True" to my PermissionSet. When deploying the package with SSI, I got an error message, making me think this wasn't the way to go.

Removing the attribute, installing the package and then manually updating the WSS_CustomTrust.config file (adding the attribute to my PermissionSet node), worked. My control now loads fine.

In the near future I'll do some investigation as why SSI doesn't seem to support the Unrestricted="True" attribute in the Manifest.xml.

-Marcel

The beta of SharePoint 2010 and Office 2010 is available on MSDN and TechNet!
The build number for the beta is 14.0.4536.1000 and can be downloaded since 16-11-2009.

If you're having trouble activating the products go to, Start -> Control Panel -> Programs and Features, select the product from the list and click on " Change". This opens up the installer window which has an option to enter the productkey. Do this and click next a couple of times and you're ready to activate :-)

Have fun testing!

Update: here's the public link http://officebeta.microsoft.com/en-us/products/microsoft-office-2010-suites-comparison-FX101745464.aspx

The DCOM error 10016 is a well known one. To be honest this error only indicates that you've forgotten one step during the installation. :)

A. Solving this is quite easy:
1. Open Component Services
2. Navigate to DCOM Config and select IIS WAMREG admin Service
3. Choose Properties, select tab Security
4. At Launch and Activation Permissions, select Edit
5. Choose Add
6. Select from the local users and groups the group WSS_Admin_Wpg
7. Give this group Local Launch and Local Activation rights
8. OK that.
9. Now the error will not occur anymore.

Now when I was installing MOSS onto a Windows 2008 R2 machine I found the following situation:



B. As you can see, this dialog is disabled. It turns out that Windows 2008 R2 gives full rights to the TrustedInstaller instead of giving rights to Administrators. This results in you being administrator not being able to edit anything. You can solve this by doing the following:

1. Open RegEdit
2. Search for the IIS WAMREG admin Service guid {61738644-F196-11D0-9953-00C04FD919C1}
3. Select Permissions (as you can see Administrators only have Read rights)


4. Click Advanced


5. Click on the tab Owner and select Administrators
6. Click OK
7. Close RegEdit
8. Close Component Services (if hadn't done that already)
9. Open Component Services
10. Now the dialog is enabled so you can perform the steps in section A.

- Marcel