Are there any examples or instructions on how to create
custom schema editor extensions in Visual Studio for
BizTalk 2004?  We were using custom schema node property
extensions using the BT2002 Editor and find this ability
missing in BT2004.

From the help you can see that these extensions are
created from the
Microsoft.BizTalk.SchemaEditor.Extensibility class and
you can see the included extension instances for
FlatFile, HWS, and property schema types.  Looks like it
would be easy to add new extensions if there was a sample
to start from.

[ Post a follow-up to this message ]

Microsoft doesn't ship any sample of schema editor extension.

--------------------
>Content-Class: urn:content-classes:message
>From: "Mark Skiba" <mskiba@rfpexpress.com>
>Sender: "Mark Skiba" <mskiba@rfpexpress.com>
>Subject: BizTalk 2004 Schema Editor Extension Sample
>Date: Wed, 17 Mar 2004 17:25:46 -0800
>Lines: 13
>Message-ID: <c5a401c40c87$f0450570$a601280a@phx.gbl>
>MIME-Version: 1.0
>Content-Type: text/plain;
>	charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Thread-Index: AcQMh/BFhNrATXGZQd23smn2xZQFJA==
>Newsgroups: microsoft.public.biztalk.tools
>Path: cpmsftngxa06.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.tools:3489
>NNTP-Posting-Host: tk2msftngxa14.phx.gbl 10.40.1.166
>X-Tomcat-NG: microsoft.public.biztalk.tools
>
>Are there any examples or instructions on how to create
>custom schema editor extensions in Visual Studio for
>BizTalk 2004?  We were using custom schema node property
>extensions using the BT2002 Editor and find this ability
>missing in BT2004.
>
>From the help you can see that these extensions are
>created from the
>Microsoft.BizTalk.SchemaEditor.Extensibility class and
>you can see the included extension instances for
>FlatFile, HWS, and property schema types.  Looks like it
>would be easy to add new extensions if there was a sample
>to start from.
>


--

This posting is provided "AS IS" with no warranties, and confers no rights. 
Use of included script samples are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm

Note:  For the benefit of the community-at-large, all responses to this mess
age are best directed to the newsgroup/thread from which they
originated.

[ Post a follow-up to this message ]