Office 2010 Developer Training Course and Training Kit (June 2011)

 Development  No Responses »
Jun 122011
 

An update to the MSDN Office 2010 Developer Training Course and downloadable training Kit has just been released. Updates include two new training Modules around developing your own custom Outlook Social Connector Provider and connecting up Office with Azure Services. There is also new content for the Open XML 2.0 SDK, using the JavaScript Object Model (JSOM) with Excel and Visio Services and how to migrate an Excel client solution to a new service-based Web solution.

Developing an Outlook Social Connector Provider:

The Outlook Social Connector (OSC) is a set of new features in Outlook 2010 that help you keep track of friends and colleagues while enabling you to grow your professional network. As your read your email, you can view information in the People Pane such as the picture, name, and title of the sender along with a rich aggregated collection of status updates and activities related to the sender. This module has a hands-on lab that provides the basics on developing a custom Social Connector Provider that can bring social or line-of-business data directly into Outlook 2010.

Using the JavaScript Object Model (JSOM) with Visio and Excel Services:

Visio Services includes a JavaScript Object Model that allows developers to integrate JavaScript code with a Visio Web Access web part. The objective of this hands-on lab is to provide you with a foundation for using the Visio JSOM to expand the functionality of a Visio Web Access web part.

Likewise, the Excel JSOM provides a way to interact with the Excel Web Access web part. The hands-on lab provides the fundamentals for doing so.

Open XML SDK 2.0:

For the Open XML SDK 2.0 there are two new videos with demo scripts and source code. The demo scripts and source code are located in the Open XML Programming Lab’s source folder.

  • The first video is an introduction to the Open XML SDK 2.0. The demo shows how to pull data out of an Excel document and generate a Word employee appraisal document on the client.
  • The second video discusses using the Open XML SDK 2.0 for solution development and demonstrates using the SDK for highly scalable document generation on SharePoint coupled with Word Automation Services.

Designing Excel Solutions for the Web:

Excel Services, part of SharePoint Server 2010, offers new capabilities to developers looking to create server-based Excel solutions either on-premises or in the cloud with Office 365. This hands-on lab will explore some of the common tasks that developers perform while designing and migrating Excel client-based solutions to Excel Services-based solutions.

In the two videos that accompany this module, Larry Waldman, Excel Program Manager, discusses how to think about designing Excel solutions for the Web and shows how to execute the migration of an Excel client solution to a web-based Excel Services solution. Larry discusses how to use the Excel Services JavaScript object model, the Excel Services REST API and the Excel Web Service to round-out the new web solution.

How to fix this error: Configuration binding extension ‘system.serviceModel/bindings/netTcpRelayBinding’ could not be found.

 Development, Web Development  10 Responses »
Apr 272011
 

There are several ways of fixing this problem and it usually involves editing your machine.config, web.config or app.config file. One of the possibilities that might have raised this error is a bug that you’ll encounter when uninstalling Microsoft Azure SDK. Apparently when you install the Microsoft Azure SDK, it adds a few lines to your machine.config file. However when you uninstall it, it doesn’t revert the changes causing your machine.config to refer to unavailable libraries.

So in order to fix this error, you’ll have to comment/delete these few lines from your machine.config file.

[sourcecode language="xml"]
<!– Under <behaviorExtensions> –>
<add name="connectionStatusBehavior" type="Microsoft.ServiceBus.Configuration.ConnectionStatusElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add name="transportClientEndpointBehavior" type="Microsoft.ServiceBus.Configuration.TransportClientEndpointBehaviorElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add name="serviceRegistrySettings" type="Microsoft.ServiceBus.Configuration.ServiceRegistrySettingsElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
[/sourcecode]

[sourcecode language="xml"]
<!– Under <bindingElementExtensions> –>
<add name="tcpRelayTransport" type="Microsoft.ServiceBus.Configuration.TcpRelayTransportElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add name="httpRelayTransport" type="Microsoft.ServiceBus.Configuration.HttpRelayTransportElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add name="httpsRelayTransport" type="Microsoft.ServiceBus.Configuration.HttpsRelayTransportElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add name="onewayRelayTransport" type="Microsoft.ServiceBus.Configuration.RelayedOnewayTransportElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
[/sourcecode]

[sourcecode language="xml"]
<!– Under <bindingExtensions> –>
<add name="basicHttpRelayBinding" type="Microsoft.ServiceBus.Configuration.BasicHttpRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add name="webHttpRelayBinding" type="Microsoft.ServiceBus.Configuration.WebHttpRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add name="ws2007HttpRelayBinding" type="Microsoft.ServiceBus.Configuration.WS2007HttpRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add name="netTcpRelayBinding" type="Microsoft.ServiceBus.Configuration.NetTcpRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add name="netOnewayRelayBinding" type="Microsoft.ServiceBus.Configuration.NetOnewayRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add name="netEventRelayBinding" type="Microsoft.ServiceBus.Configuration.NetEventRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
[/sourcecode]

[sourcecode language="xml"]
<!– Under <client> –>
<endpoint address="" binding="netTcpRelayBinding" contract="IMetadataExchange"
name="sb" />

<!– Under <metadata><policyImporters> –>
<extension type="Microsoft.ServiceBus.Description.TcpRelayTransportBindingElementImporter, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<extension type="Microsoft.ServiceBus.Description.HttpRelayTransportBindingElementImporter, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<extension type="Microsoft.ServiceBus.Description.OnewayRelayTransportBindingElementImporter, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

<!– Under <metadata><wsdlImporters> –>
<extension type="Microsoft.ServiceBus.Description.StandardRelayBindingImporter, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<extension type="Microsoft.ServiceBus.Description.TcpRelayTransportBindingElementImporter, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<extension type="Microsoft.ServiceBus.Description.HttpRelayTransportBindingElementImporter, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<extension type="Microsoft.ServiceBus.Description.OnewayRelayTransportBindingElementImporter, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
[/sourcecode]

Savvis Symphony Virtual Private Data Centre (VPDC) – Secured Enterprise Cloud Service

 Technology  No Responses »
Apr 132011
 

There are many different kinds of cloud offering out there – Amazon AWS, Google App Engine, Microsoft Azure – and they offer different services for the different ways you use cloud. Savvis offers an enterprise-grade cloud infrastructure service, Savvis Symphony, that allows you to maintain and configure your virtual cloud environment – from security to virtual hardware servers. Savvis is focused on “Infrastructure as a Service” (IaaS) where it provides a wide range of managed services for enterprise needs.

Savvis Symphony Virtual Private Data Centre (VPDC) is a virtual data center inside a shared cloud. What makes Savvis stand out among the competition is their end-to-end security service on Savvis Symphony. Savvis provides well-defined security policies and procedures, and ensures compatibility between newer security protections designed specifically for virtualized environments and more traditional, physical security controls. These comprehensive security features and processes are integrated into Savvis Symphony VPDC.

Personally, Savvis is probably the first cloud IaaS provider (and hopefully more to come) that I know of who puts so much emphasis on security for enterprises, giving enterprise businesses a peace of mind when moving to the cloud. Not only do they provide cloud services, but they also provide infrastructure consulting services to help your business streamline and “outsource” your IT department to the cloud.

For more information, check out savvisknowscloud.com or www.savvis.sg.