The second Twin Cities Code Camp will occur this Saturday, April 28th. Here’s the website, which includes a schedule and list of sessions: http://www.twincitiescodecamp.com/TCCC/Default.aspx
I’ll be presenting on utilizing BizTalk’s BAM features from non-BizTalk applications.
Through the MOSS/WSS v3.0 TAP program and the early betas, there was a whole bunch
of ‘debug’ type messages being logged.
I’ve always loved the MOSS/WSS V3.0 log files – under …\12\Logs\…. as there’s
some very funny error messages. Here’s such one
04/23/2007 04:50:51.09 w3wp.exe (0x152C) 0x1650 Windows
SharePoint Services General 8l1n High An SPRequest object was not disposed before
the end of this thread. To avoid wasting system resources, dispose of this object
or its parent (such as an SPSite or SPWeb) as soon as you are done using it. This
object will now be disposed. Allocation Id: {65D8E0A2-C330-418A-8871-C597A7C612C9}
To determine where this object was allocated, create a registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared
Tools\Web Server Extensions\HeapSettings. Then create a new DWORD named SPRequestStackTrace
with the value 1 under this key.
The next version of Visual Studio, Microsoft%u00ae Visual Studio%u00ae code name “Orcas” has been released by Microsoft on April 19th, 2007.Visual Studio code name “Orcas” is the next generation development tool for Windows Vista, the 2007 Office system, and the Web. Beta 1 consists of multiple releases including, Visual Studio Professional Edition, Visual Studio Team […]
For all those that read my post on the BizTalk Backup job running at 10:00am (Melbourne, Australia time), there is a hot fix in the works, so keep checking back and as soon as it is released I will post the number.
A big thanks to MS Support in Australian for taking this and running with it.
>
I’ve spent the last two weeks
in Ireland doing training on R2 for BizTalk team. Had
some very interested students – especially in the EDI and RFID areas.
I also got to spend some time with the MS
and community people here – just great people – always up for a pint. Thanks Clare, Rob,
and Philip McKeown
(you should really blog there Philip) for taking me out to the smallest pub in Dublin.
BTW
– Clare I found out was at least partially responsible for this (http://www.youtube.com/watch?v=RRW-vqh49Bw –
this may not be work safe in all parts of the world so be careful – I do love Podge
and Rodge though)
I recently got an email to inform me I was able to participate in the CSD Technology
Advisors program………
Basically I can sit down and give MS feedback on what works, what doesnt – “the button
should be moved over 2cms”…..
Specifically about BizTalk, WCF, WF, .NET 3.x, 4.x oh and did I mention BizTalk??
I’ve had an interesting discussion this week with some of my fellow BizTalk MVPs
and also a few MS folks.
Here’s the crux of my beef.
1. Stop a Send Port or Orchestration – it is still Enlisted but
in the Admin Console it’s stopped. (at this stage – you’re stopped and my ‘stopped’
are the same)
2. Shoot a message into BizTalk destined for the stopped Send Port or grab one of
the queued up Suspended-Resumable messages and say “Resume” (mind
you, you do have other options here of Resume in Debug Mode etc)
3. Guess what happens?? BizTalk Queues the message up as it knows the corresponding
Send Port is stopped???? NO!!!!! BizTalk will send the message through the
STOPPED send port – (bang head against wall)
4. This ‘feature’ IS useful for when BizTalk receives a flood
of msgs and an issue arises downstream (backend system or so) and you can ‘trickle
feed’ A msg to the back end system.
5. I think this functionality should be tied into some sort of ‘Resume for Debug’
type wording. Something to indicate that it’s an ‘unusual’ circumstance.
6. The terminology within the Admin Console is what I have an issue with. The port
is Stopped, an NT Service is STOPPED, an application is ‘stopped’ –
so these terms of stopped differ in the biztalk world.
7. Outcome of the week’s discussion: MS are looking into changing the terminology
within the Admin console. 
Well I have been traveling heaps lately, I have a 4 week schedule that has me doing 12 flights, but that is not the point of this post, I was on a flight home last Friday night and I really wanted to finish working on a BizTalk error handling orchestration, so out came the Toshiba M4 tablet and even though I had a empty seat beside me, with the people in front having the seats reclined, I just could not use the keyboard, so I decided to try BizTalk programming with the pen, and as crazy as it sounds I could do most things I needed to do, I did need to key in a few things, but I found the items I needed and did some cut and past.
Now this makes my decision about what laptop to get in June when my Toshiba M4 is due to be replaced, I had pretty well decided on going with a Dell 820, full spec’d out, but now I am thinking more and more about another tablet pc, so time to start having some more looks.
Examining
and Building an R2 Adapter using the New R2 Adapter Framework
Wednesday, 2nd
May 2007
6:00 PM
Food and Drinks, 6:30 PM Kick Off
1
Epping Road, Microsoft
North
Ryde, Sydney
Hi
all on our Post Anzac Day Wednesday meeting and I hope two-up was (will be) kind to
you. This month we’re at Microsoft North Ryde with a presentation on Adapters, Adapters
and more Adapters. The new BizTalk Adapter Framework is called The
Line Of Business Adapter Framework SDK (LOB Adapter SDK between friends)
and is based on Windows
Communication Foundation(WCF). As you can imagine, WCF adds a ton of functionality
around the way we do messaging.
With BizTalk 2006 R2 comes many new features and improvements we examine R2 .NET Adapters
(WCF Based) and also look at new WCF and WF BizTalk BAM Interceptors, allowing you
to post to BAM directly from WCF or WF.
I’ve provided a calendar appointment for your calendars so join me.
Presenter:
Mick
Badran, BizTalk MVP who
specialises in Microsoft Technologies as a Solutions Architect/Developer. With over
15 years consulting experience and 12 years as a Microsoft Certified Trainer provides
in depth real world knowledge.
Session
Details
So
what is the story with Integration and Adapters in BizTalk 2006 R2? This session covers
the roadmap going forward in building BizTalk .NET Adapters (those based on WCF) in
the new Framework. It will discuss all the benefits of the new framework and explain
options on where to host these adapters.
We will also examine the relationship between BizTalk and the WCF based adapters with
respect to Message Contexts, and multipart messages.
The
Session details are as follows:
1. R2
WCF Adapters Explained – including the new BAM Interceptors for WCF and WF
2. LOB
Adapter SDK framework explained
3. Building
a new Custom Adapter using the LOB Adapter SDK
As
always love to hear from you and what’s been getting you excited at work.
Who
Should Attend?
If
you’re looking to get additional business related information out of your Biztalk
processes then this session is for you.
This session is technically focused for Biztalk developers and System Architects.
Please be sure that you RSVP so we know
how many to expect. Reply with a yea or ney to [email protected]
Looking forward to seeing you there at
Microsoft Premises – North Ryde
Mick and Mark
Ph: 0404 842 833 (Mick’s mobile)
SydBiz.Org