Downloading and installing .NET 3.0 (previously WinFX)
-
.NET 3.0 (WinFX) Runtime Components Beta 2
-
Windows SDK
-
VS.NET 2005 Extensions
-
Workflow Foundation RC and Extensions
If you haven’t already heard, the next big conference that our folks in Redmond are planning is the 2nd annual Business Process Management and Integration conference. This conference is going to be sponsored by the BizTalk server product group and it’s going to be held October 3rd through to the 6th at the Microsoft Conference Centre in Redmond (2006). Complete details are going to be made available in the early summer, but be sure to save those dates if you’re interested.
People that attended last year tell me that they were around 500 partners and customers attending and that we had at least 40 from right here in Canada. We’re expecting to get around 750 this year, so it’ll be the place to meet other BizTalk experts, exchange BizTalk stories and generally ramp up your skills. Hope to see you there.
Cheers
What would you like to see? Seems the team is ramping up again to tackle the next version of the Ent Lib libraries. Great stuff. I love enterprise libraryand use it in almost every project I do. Keep it up.
-B
InfoPath supports forms with file attachments by encoding the attachement as base64 and including the following PI
<?mso-infoPath-file-attachment-present ?>
at the top of the XML document to indicate that a file has been attached to the document.
WSS adapter works with InfoPath forms with attachements by making sure that it does not add/remove/update any of the PIs that are related to file attachment. If the files are attached to the form in InfoPath then the PI should be there because InfoPath adds it. If the files are attached by your orchestration or some component other than InfoPath, then the orchestration/component needs to add the PI explicitly. The adapter cannot know if a file attachment is included in the form (unless the PI is present in which case there’s nothing to be done) so it will never add the PI. You can add the PI explicitly in your orchestration using a construct like this:
msg(XMLNORM.ProcessingInstructionOption) = 1;
msg(XMLNORM.ProcessingInstruction) = “<?mso-infoPath-file-attachment-present ?>”;
So, whatever component attaches the files to the form needs to also add the PI. WSS adapter will preserve the PI if it’s in the document, but it will never add such a PI to the XML document.
The latest draft of the content for this year’s TechEd in Australia has been posted to Kleefy’s blog. http://blogs.technet.com/mkleef/archive/2006/06/09/434444.aspx Please comment!!
Let me know if you want any Tracks relating to BizTalk removed / added…
At this stage the connected Systems Track includes;
(BTS) Business Process and Integration Landscape
(WinFX) Introduction to WinFX
(BTS) BizTalk Server 2006 and Office Business Scorecard Manager 2005: Integrating Real-Time Business Activity Monitoring with the Scorecard
(BTS) Planning and Designing Enterprise Class BizTalk Server Solutions
(CS) Connected Commerce with Commerce Server 2007
(WinFX) “InfoCard”: Introduction
(WinFX) Windows Communication Foundation: Introduction
(WinFX) Windows Workflow Foundation: Introduction
(BTS) BizTalk Server: Adapters for Host Systems
(BTS) Integration of BizTalk Server 2006 and Windows Workflow Foundation.
(BTS) Management, problem identification, trouble shooting, automation
(CRM) Modeling and Automating Business Processes with Microsoft CRM
(NET) .NET 2.0 to WinFX: How WCF will change the way you’re developing Service Oriented solutions
(WinFX) Windows Communication Foundation: Building Secure, Reliable and Transacted Services with WCF
(WinFX) Windows Communication Foundation: Designing Bindings and Contracts
(WinFX) Windows Workflow Foundation: Building Rules-Based Workflows
(WinFX) Windows Workflow Foundation: Creating Custom Activities for Workflows
(NET) .NET Framework 2.0: Build your own Enteprise Service Bus with it
Tiho has a good entry on why it is that way and how to fix it. He also explains how to diagnose the problem….(read more)
[Via Eli Robillard] So you want to learn about the new version of SharePoint? Both Windows SharePoint Services v3 and Microsoft Office SharePoint Server 2007? Than this book is for you: 7 Development Projects for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0.
Quite a long title for a 236 page book, but the good news is that you can download it for free! These are the chapters:
Commerce Server 2007 RTMs are now available. I’ve been working with this version since the first Beta ; really great stuff. Congrats to the team!!
I have received requests for what might be called “Developing for BAM 101”. To address these requests I am planning to provide a topic set that will help the new BAM code developer get started. I have outlined our proposed set of topics below. I welcome your feedback on these topics. Does this set of topics address the needs of the new BAM developer?
The topics in this table of contents will initially be delivered as a stand alone document set. on the Microsoft Dev Center. Moving forward the contents of this guide will be pushed into the core documentation for the BizTalk Server.
The target audience for this document is the new BAM developer. This document will focus on development tasks associated with handling BAM events.
Getting Started Developing For BAM
Topic: What is BAM?
Content: This will be brief overview of BAM and will point to other resources.
Topic: Why Write Code for BAM
Content: This topic discuss the advantages and benefits gained by writing code to perform BAM tasks.
Additional topics that topic covers are code written to be called from inside BizTalk Server using the OrcheestraionEventStream and MessagingEventStream APIs and the use the native Interceptor.
Code written to be called from outside of BizTalk Server using the BufferedEventStream and DiredEventStream.
Topic: BAM Concepts for the Developer
Topic: What is an Activity
Topic: Tracking vs. Transactional Processing
Topic: What are Continuations
Topic: What is a Reference
Topic: BAM Development Prerequisites
Topic: Other Prerequisites
Topic: Prerequisites for developing against a BizTalk Solution
Content: This topic contains information on what minimal BizTalk and BAM infrastructure components must be in place before you can develop against them.
Topic: Key APIS for BAM Development
Content: This topics covers the BAM name spaces and describes the usage of the key BAM APIs. This topic may have several subtopics to address separate areas of functionality.
Topic: Best Practices for BAM development
Topic: Developing Secure BAM code
Topic: Considerations for developing BAM code solutions
Content: This topic helps steer the new developer around common programming issues that are encountered by the new BAM developer.
Topic: Simple Sample
Content: The sample is a minimal sample designed to highlight the usage of the APIs without burying them in to much complexity.