Microsoft have rounded up all the serious BizTalk Bloggers (MVPs + keen MS guys + Teams) and the Connected Systems Division (CSD Team) within Microsoft and produced a valuable aggregator with all this in one spot.

Just have a look at the bloggers that are contributing to this - sensational!!! One stop shop for you guys.

From WCF to BizTalk, EDI + Custom Pipelines.

We all display this logo on our site.

Here's the RSS Feed http://biztalkblogs.com/RssDoc.xml

Merry Christmas!!!!!

Well firstly - I've got to say this comes off the back of a great Sharepoint MVP and collegue of mine Ishai Sagi. Big THANKS Ishai!!!

Typically my experience with the DataFormWebPart has been through the eyes of Sharepoint Designer - open pages with webparts on them and looking at the XML configuration of these parts. It look pretty ugly AND very site/web specific - IDs all over the place etc etc.

Ishai the wealth of knowledge came up with this solution - by overriding the SetDataSourceProperties method, you can effectively create a datasource from anywhere!!!! Forgetting the IDs etc that cause all the pain.

I've marked the 2 important lines with (**) in the code.

Big Thanks Ishai!!! Folks he's always one to watch - lock his blog in and learn!! :)

Ishai mentioned that his code below is purely for educational purposes

using System;
using System.Runtime.InteropServices;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Serialization;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using Microsoft.SharePoint.WebPartPages;
using System.Data;
using System.Xml;

namespace AdvancedQueryWebPart
{
[Guid("46a8853d-415c-458e-990c-419c12fa04f5")]
public class AdvancedQueryWebPart : DataFormWebPart, IWebPart
{
public AdvancedQueryWebPart()
{
this.ExportMode = WebPartExportMode.All;
}

protected override void SetDataSourceProperties()
{
   try
   {
      // Call a custom function that returns the data you want to show as a data table
      DataTable results = GetCustomData();
      if (results.Rows.Count > 0)
      {
         // generate xml for selected items
         XmlDocument doc = new XmlDocument();
         XmlNode root = doc.AppendChild(doc.CreateElement("Rows"));
         foreach (DataRow row in results.Rows)
         {
            XmlElement rowNode = doc.CreateElement("row");
            foreach (DataColumn col in row.Table.Columns)
            {
               string val = row[col].ToString();
               XmlAttribute att = doc.CreateAttribute(col.ColumnName);
               att.Value = val;
               rowNode.Attributes.Append(att);
            }
            root.AppendChild(rowNode);
         }
         // create an XmlDatasource with the new data, and set it to cache for one second
         XmlDataSource ds = new XmlDataSource();
         ds.CacheDuration = 1;
         ds.Data = doc.InnerXml;
         // bind the web part to the xml
(**)     this.DataSource = ds;
(**)     this.DataBind(true);
       }
       else
       {
         Label noResults = new Label();
         noResults.Text = "No results were found";
         this.Controls.Add(noResults);
       }
   }
   catch (Exception ex)
   {
      Label lblError = new Label();
      lblError.Text = ex.ToString();
      this.Controls.Add(lblError);
   }
   base.SetDataSourceProperties();
}

private DataTable GetCustomData()
{
   try
   {
      SPWeb webSite = SPContext.Current.Web;
      SPSiteDataQuery query = new SPSiteDataQuery();
      //look only in document libraries
      query.Lists = "<Lists ServerTemplate=\"101\" />";
      //search for documents that have "Test" in the title
      query.Query = @"<Where><Contains><FieldRef Name=""Title"" /><Value Type="Text"">Test</Value></Contains></Where>";
      //bring back the title field of the documents
      query.ViewFields = @"<FieldRef Name=""Title"" Nullable=""TRUE"" /><FieldRef Name=""FileLeafRef"" Nullable=""FALSE"" />";
      DataTable items = webSite.GetSiteData(query);
      return items;
   }
   catch (Exception ex)
   {
      throw new Exception("There was a problem querying the site with the query", ex);
   }
}

}

}

Well looks like the team have made ready some great goodies in WSS 3.0 SP1, MOSS SP1 and SPD SP1.

These are Service Packs with enhancements also.

You need to install WSS 3.0 SP1 first then install MOSS SP1 (if you have a MOSS server)

Grab the details from the links below for both x86 AND x64 versions....

Enjoy,

Mick.

Just to let you folks know -

you no longer have to create special pipeline components, cases etc. for handling flat files.

R2 will resolve (dynamically) the schema from those that are deployed!!! (c.f. to xml)

To set it up:

- create a custom pipeline + add a FFAsm component to it.
- leave the schemas properties blank.
- BizTalk will now use dynamic resolution for the incoming schemas.

This is great news!!!! I can now throw out my 'dynamic FF schema resolver custom component'

Enjoy!

Rahul (MS BTS TS in our parts - great guy and is hugely knowledgeable in both Java integration technologies as well as MS) has been hard at work again weaving his magic... I just couldn't go past his post without sharing it with you guys.

Great step by step instructions Rahul!

Well done.

Finally the word on the street is out with Volta finally being announced (cool name).


What is it? What can it do for me? (lately

Here's an example scenario:
- you write a classic .NET Winform/Client App.
- put your 'Volta' hat on and nominate sections, routines etc. of your app and which tier/layer you would like the components/classes/sections to run on.
- You then nominate Web Layers or classic CLR client layers etc.
- Volta crunches your design and boom!!! You've got your SENSATIONAL multitier app from your original single whole app.

In fact - check out this great Walkthrough for the 'Hello World app'

You don't need to worry about app splitting yourself the Volta 'directives' do the work.

When I was at Uni this sort of thing was in an area of my studies (simplified and more specific though - nominating code sections to run concurrently across many distributed CPUs....yeah I know - I'll get back to some English).

Where is this going?
Did I tell you about the next version of BizTalk codenamed 'Oslo'....

My take is that this is (and this is purely just me kicking some tyres with you guys) that BizTalk vNext is all about Modelling. Having a central repository that holds all forms of 'models' that describes not only the process, design, test....but Volta is a preview on the 'deploy' aspect of these Models.

The important point in BTS vNext is that *it is the Model that is executed* not some result of a process that you've run a week ago on that model, otherwise these models get out of date quite quickly.

Here's the 'official Volta blurb'-
------------------------

On Wednesday, December 5th, Live Labs will announce Volta, an experimental developer toolset that enables developers to build multi-tier web applications by applying the familiar techniques and patterns of developing .NET applications.  In effect, Volta extends the .NET platform to further enable the development of software+services applications, using existing and familiar tools and techniques.  Similar to other technology previews from Live Labs, the purpose of releasing Volta as an experiment, allows for testing of the model with customers and partners in order to gather early feedback and continually influence the direction of Live Labs technologies and concepts.  In addition, where and how Volta will fit into a product roadmap is not the end goal, but rather to experiment with new alternative models to enable Microsoft to continue to be innovative in this new generation of software+services.

Volta Key Messages:

• Volta is an experimental developer toolset that enables developers to build multi-tier web applications by applying the familiar techniques and patterns from the development of .NET applications.
• Developers can use C#, VB, or other .NET languages utilizing the familiar .NET libraries and tools.
• Volta offers a best effort experience in multiple environments without requiring tailoring of the application.
• Volta furthers Microsoft's software+services efforts by making it easier to write and build multi-tier applications.
• Volta automates certain low-level aspects of distributing applications across multiple tiers, allowing programmers to devote their creative energy to the distinguishing features of their applications.
• Via declarative tier splitting, Volta lets developers postpone irreversible design decisions until the last responsible moment, making it faster and cheaper to change the architecture to accommodate evolving needs.
• Through MSIL rewriting, Volta follows developer's declarations to turn a single-tiered application into a multi-tiered application, generating boilerplate code for communication and serialization.
• Volta, like other technology previews from Microsoft Live Labs, is an example of the rapid innovation of web-centric technologies happening at Microsoft.
• The purpose of the technology previews, such as Volta, is to test new technologies and product concepts with customers and partners and to gather early feedback to influence the direction of Live Labs projects.

The problem about Sharepoint implementations is that typically when you create your Sharepoint Web Application from Central Admin, there is one ContentDB that you assign.

Then spare no more thought to it......

In update KB934525 MS added a new command to stsadm called MergeDBs.

This handles it all for you in a single command. You need to specify, WebApp1 address, contentDB1 and an excerpt of the stsadm -o enumsites command to specify the site(s) you want to 'migrate' to ContentDB2.

Here's a great step by step article by Todd

Well done!