BizTalk RFID Event Handlers

Source code checked in, #69631

Project Collection Service Accounts — Mon, 01 Oct 2012 21:13:48 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69630

Project Collection Service Accounts — Mon, 01 Oct 2012 21:07:03 GMT

Checked in by server upgrade

Source code checked in, #48968

_TFSSERVICE — Thu, 22 Jul 2010 18:55:41 GMT

Checked in by server upgrade

NEW POST: Event Handler naming convention

ryancrawcour — Fri, 16 May 2008 10:31:52 GMT

mlandler wrote:
I would suggest to follow naming conventions especially when it comes to the term "sink".
How about only calling eventhandlers "sink" when they return void - which means a 100% filter or swallowing all readevents. Similar to the SQLSink event handler.
Whith this naming convetion on could easily determine wheter a specifica eventhandler can be used at any position in the event queue.

I tend to agree with this line of thinking completely.
Can we go ahead and rename the existing file and msmq event handlers to remove the "sink" from the name?

NEW POST: Event Handler naming convention

mlandler — Tue, 29 Apr 2008 15:28:15 GMT

I would suggest to follow naming conventions especially when it comes to the term "sink".
How about only calling eventhandlers "sink" when they return void - which means a 100% filter or swallowing all readevents. Similar to the SQLSink event handler.
Whith this naming convetion on could easily determine wheter a specifica eventhandler can be used at any position in the event queue.

Source code checked in

ArpitN — Thu, 28 Feb 2008 13:55:09 GMT

1st checkin for FilterEventHandler

NEW POST: FileSync

ArpitN — Wed, 27 Feb 2008 13:33:41 GMT

Hey Shaul,

Can I register multiple event handlers to a single process, even though their functions have the same input type "TagRead"?

Yes this is exactly the kind of scenario that RFID Process enables. Think of a RFID Process as a sequential pipeline of EventHandlers. The only thing to keep in mind is that output of one EH is one of the inputs for another EH. (The Validate Process with check this statically).
So, suppose if you have one EH(say EH1) whose output is TagListEvent and the input of this EH(say EH2) is TagReadEvent then EH2 cant be placed after EH1. But if output of EH1 was TagReadEvent then placing EH2 after EH1 was OK.
Also, say EH2 input was RfidEventBase (the base class of both TagReadEvent and TagListEvent) then placing EH2 after EH1 was possible.

Are they executed in-line in a single thread or in separate threads?

BizTalk RFID garentees that they are called sequentially with output of 1st EH acting as input for 2nd EH and so on but does no garentee that they are invoked on the same thread. Also your EH code could be called from multiple differnent threads, thus it is important that EH are thread-safe.

Hope I answered your questions.
-Arpit Nand
P.S. To get your questions answered by BizTalk RFID experts head to http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=1474&SiteID=1

NEW POST: FileSync

Shaul — Wed, 27 Feb 2008 12:13:44 GMT

Thank you both :)
I've been reading some of the documentation regarding Event Handlers.
I understand that one EH function's output type is another function's input, this way you can pass a tag read to a line of functions, depending on processing results.

Lets say I want to add this file EH a process which already has an EH which I've created.
Can I register multiple event handlers to a single process, even though their functions have the same input type "TagRead"?
Are they executed in-line in a single thread or in separate threads?

Shaul

Source code checked in

ArpitN — Wed, 27 Feb 2008 12:02:15 GMT

Adding FileEvtHandler.VS2005.csproj a VS 2005 based project. Removed Linq dependancy from FileSink.cs so that this EH can be build with .NET 2.0/3.0 too.

NEW POST: FileSync

ArpitN — Wed, 27 Feb 2008 10:55:15 GMT

Hello Shaul,

Biztalk RFID uses .NET 3.0 so it will not even install if you dont have .NET 3.0.

BizTalk RFID had a issue with .NET 3.5 Beta1 due to a bug in .NET 3.0 Service Pack that is shipped with .NET 3.5 due to which Rfid Service was unable to start. But there is no issue with the Released version of .NET 3.5

If have .NET 3.5 installed, any EH/Provider written for it will work just fine. If you are facing any specific problem, please report and we can take a look.

As for solution file, I will upload VS2k5 csproj and sln files for this EH.

-Arpit Nand

CREATED ISSUE: Event handler for Filtering

shasbe — Tue, 26 Feb 2008 23:43:44 GMT

Filtering is a challenge and I have heard requests for an event handler that can provide basic filtering. To begin with we should provide a way for folks to filer based on string functions like startswith, endswith and substring.

NEW POST: FileSync

shasbe — Thu, 21 Feb 2008 23:12:42 GMT

Hi Shaul, Sorry about using 2008. That is the version I have on my machine so I just used it.

I have used 2008 to create event handlers and use them with Biztalk and it works fine. I don't think there should be any problems. BizTalk will still use 2.0 libraries as it was built with 2.0.

VS 2008 can be used to build applications using .NEt 2.0 also. I know there is some issue with 3.5 and Biztalk but I think building DSPI with VS 2008 should not be a problem.

Let me know if you face any specific issue.

regards
Sudhir

NEW POST: FileSync

Shaul — Thu, 21 Feb 2008 15:59:09 GMT

Hi,
I tried to open the solution but it seems you used vs 2008 and my vs 2005 can't open it.

First of all: is it possible to develop an event handler with .net 3.5 and add it to the rfid manager?
I thought that was impossible since biztalk rfid was made using .net 2.0.
Is it possible to develope a DSPI using VS 2008 & .Net 3.5 as well?

Thanks,
Shaul

RELEASED: File and MSMQ Sink(Update) (Feb 03, 2008)

Mon, 04 Feb 2008 00:36:59 GMT

This release contains first version of MSMQ Sink and update to File Sink. Both support csv or XML file formats. MSMQ handler supports both transactional and non transactional queues.

UPDATED RELEASE: File and MSMQ Sink(Update) (Feb 03, 2008)

Mon, 04 Feb 2008 00:36:59 GMT

This release contains first version of MSMQ Sink and update to File Sink. Both support csv or XML file formats. MSMQ handler supports both transactional and non transactional queues.

UPDATED WIKI: Home

shasbe — Mon, 04 Feb 2008 00:35:04 GMT

Project Description
This project delivers various extensions to Standard Biztalk RFID framework. This will come in form on various event handlers. BizTalk RFID ships with BRE and SQL handler. This project will deliver various other handlers for customers to download and use.

BizTalk RFID provides .NET based RFID platform for developers to build RFID applications. One way the platform can be extended is by building custom event handlers. BizTalk RFID 2006 R2 provides BRE and SQL Sink handlers out of the box. This project is an effort to involve community to build and deliver additional frequently required and requested handlers.

Following are few important links
BizTalk RFID Site: http://www.microsoft.com/rfid
BizTalk RFID Blog: http://blogs.msdn.com/biztalkrfid
Sudhir's Blog: http://blogs.msdn.com/sudhir

The goal of this project is to reduce the time required to implement and build RFID applications.

Please join this effort and help make RFID a mass deployment technology using BizTalk RFID platform.

Additional information on starting a new project is available here: Project Startup Guide.

UPDATED WIKI: Home

shasbe — Mon, 04 Feb 2008 00:34:43 GMT

CREATED RELEASE: File and MSMQ Sink(Update) (Feb 03, 2008)

Mon, 04 Feb 2008 00:25:48 GMT

This release contains first version of MSMQ Sink and update to File Sink. Both support csv or XML file formats. MSMQ handler supports both transactional and non transactional queues.

Source code checked in

shasbe — Mon, 04 Feb 2008 00:19:22 GMT

Adding MSMQ event handler and fixed issue with chaining of event handlers.

NEW POST: MSMQ Sink

shasbe — Mon, 21 Jan 2008 01:03:15 GMT

This thread can be used to discuss about MSMQ Sink Event Handler