by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
To access R2 Public Beta, please follow these instructions:
Sign in using your passport
Click on Available Connections (on the Connect Home menu)
Scroll down to the Programs table (shown below)
Apply for BizTalk 2006 R2 Beta program
Program |
Nomination Start Date |
Nomination End Date |
Options |
BizTalk 2006 R2 Beta |
4/2/2007 |
8/1/2007 |
Details Apply |
You’ll immediately get access to the R2 public beta site and download.
Marjan
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
Last January 31th my good friends Javier and Carmen Mariscal were blessed with the birth of their second son, Daniel Mariscal. After two months, the baby got his first exposure to the Microsoft world. DO NOT make any assumptions about the finger; he is…(read more)
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
I recently had reason to revisit the exact mechanisms Microsoft use when you assert facts to the Microsoft Rules Engine. I was discussing stuff on-line with a fellow rules enthusiast when a terrible thought occurred to me. Can the MS BRE always uniquely identify each different fact, or is there a chance that sometimes it might confuse two facts with each other?
For a couple of days, I was convinced that I had stumbled on a significant bug. Indeed, at one point, I thought there was such a serious problem that I would have to recommend to my company that we desist from any further use of Microsoft’s rules engine. Melodramatic, huh! Fortunately, after a bit more research, I discovered that I was quite wrong. The MS BRE does not suffer from a terminal flaw and can be trusted to always distinguish correctly between all your facts. It’s worth recording my suspicions, mistakes and eventual enlightenment. There is something useful to learn, here, about the inner workings of the engine, and also about Microsoft’s implementation of the Hashtable class in .NET.
Read more at http://geekswithblogs.net/cyoung/articles/110852.aspx
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
84% it wasn’t that bad, but it should have been easy after 3+ years working with BizTalk, lots on BAM and the BRE. I think I lost marks on the drag and drop questions and there was a tricky question on coding a BRE fact retriever. I used Saravana’s exam preparation diary.
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
We were having a problem with a BizTalk assembly (containing only maps) having a “project”
reference to a standard C# library. As soon as the project reference was added,
we were unable to open the maps – errors along the lines of “unable to
open source schema” and “unexpected error encountered…vsee\internal\inc\vscomptr.inl”.
See here for
a good forum discussion on the issue that we came across.
It turns out this issue crops up if you have a VSTS unit testing project in the same
solution…How is that for a strange product interaction? Possible workarounds
include removing the unit testing project (and putting it in a separate solution)
or using a file reference instead of a project reference. (If you go the
latter route, go to the properties of your solution and set up the project build dependencies
manually to account for this!)
We opted for file references rather than removing our unit test assembly, at least
for the time being. Hopefully this will be addressed soon…
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
We were having a problem with a BizTalk assembly (containing only maps) having a “project”
reference to a standard C# library. As soon as the project reference was added,
we were unable to open the maps – errors along the lines of “unable to
open source schema” and “unexpected error encountered…vsee\internal\inc\vscomptr.inl”.
See here for
a good forum discussion on the issue that we came across.
It turns out this issue crops up if you have a VSTS unit testing project in the same
solution…How is that for a strange product interaction? Possible workarounds
include removing the unit testing project (and putting it in a separate solution)
or using a file reference instead of a project reference. (If you go the
latter route, go to the properties of your solution and set up the project build dependencies
manually to account for this!)
We opted for file references rather than removing our unit test assembly, at least
for the time being. Hopefully this will be addressed soon…
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
I just came across another Eric Stott at myspace.com don’t visit this while at work (http://www.myspace.com/ericstott)
I don’t live in England, and am not single, I might be sarcastic, but not this crude.
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
These days, Microsoft is busy veiling out lots of LOB Adapters for BizTalk Server 2006 R2. One of them , which interests me most is WCF LOB Adapter. We can get all latest updates and news on this and other adapters from Sonu Arora (Program Manager, Microsoft).
Check for more information on this here
I know for […]
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
The BizTalk Server Teamhas announced the release of the public beta 2 for BizTalk Server 2006 R2 yesterday. It might be a good idea to read their post here to get an idea of the upcoming features in R2 and also how to get it.
On a side note, here is another interesting post from a […]
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
BizTalk Server 2006 R2 Beta 2 released – Thanks Mike 😉