http://blogs.msdn.com/richardbpi/archive/tags/General+.NET/default.aspxTags: General .NETen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/richardbpi/archive/2005/07/13/438550.aspxWed, 13 Jul 2005 23:45:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:438550rseroter0http://blogs.msdn.com/richardbpi/comments/438550.aspxhttp://blogs.msdn.com/richardbpi/commentrss.aspx?PostID=438550<SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: arial"> <P>I've been spending some free time getting back up to speed on <A href="http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/default.aspx">Indigo</A> because (a) it is quite interesting, and (b) has big implications for BPI solutions moving forward. I've added a VS.NET 2005/Indigo machine to my <a href="http://blogs.msdn.com/richardbpi/archive/2005/07/01/434774.aspx">BizTalk farm</A> and want to see how I can get the BizTalk Servers to play nicely with it. </P> <P>However, sometimes I have serious brain cramps while setting things up, and today is no exception. Wasted like 10 minutes figuring out why my Indigo *.svc file wouldn't get processed by IIS. I then realized that the *.svc extension probably wasn't mapped within IIS. I had assumed that the Indigo install would have done that for me. Luckily I found <A href="http://www.15seconds.com/issue/050707.htm">this article</A> (see <B>Host the Web Service in IIS</B> section) which reminded me of the steps necessary to get things back on track. </P></SPAN><img src="http://blogs.msdn.com/aggbug.aspx?PostID=438550" width="1" height="1">BizTalkGeneral .NEThttp://blogs.msdn.com/richardbpi/archive/2005/06/08/426915.aspxWed, 08 Jun 2005 23:50:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:426915rseroter1http://blogs.msdn.com/richardbpi/comments/426915.aspxhttp://blogs.msdn.com/richardbpi/commentrss.aspx?PostID=426915<DIV><FONT face=Arial size=2>Greetings.&nbsp; I expect to use this space to discuss best practices, tips, code, product&nbsp;roadmaps and more around <A href="http://www.microsoft.com/biztalk/default.mspx">BizTalk Server</A>, <A href="http://www.microsoft.com/hiserver/default.mspx">HIS</A>, and <A href="http://www.microsoft.com/commerceserver/default.mspx">Commerce Server.</A></FONT></DIV> <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV> <DIV><FONT face=Arial size=2>I've been working with BizTalk Server since the beta of BizTalk Server 2000 nearly five years ago when <A href="http://www.avanade.com">Avanade</A> was just getting started.&nbsp; I joined Microsoft as a Technology Specialist fairly recently, and considered blogging right away, but kept putting it off.&nbsp; However, I've recently been inspired again&nbsp;by <a href="http://blogs.msdn.com/martywaz/">Marty Waz</A> and <a href="http://blogs.msdn.com/oallen/">Owen Allen</A> and decided to put material out that will hopefully be somewhat useful to my customers, partners and the general BPI development community.</FONT></DIV> <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV> <DIV><FONT face=Arial size=2>Over the last few weeks, Marty and I tried to break the spirits of 30 customers and 60 partners with some pretty hard core week-long&nbsp;BizTalk training.&nbsp; Most everyone came out alive, and my house has only be egged twice since.&nbsp;&nbsp; It's exciting to spread the integration message throughout our district and get folks to see that BizTalk is actually an enterprise-ready platform.</FONT></DIV> <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV> <DIV><FONT face=Arial size=2>There are some great BPI opportunities here in Southern California and each of the BPI products will be experiencing a version refresh very soon.&nbsp; All in all, a wild time to be doing BPI work.</FONT></DIV><img src="http://blogs.msdn.com/aggbug.aspx?PostID=426915" width="1" height="1">BizTalkCommerce ServerHost Integration ServerGeneral .NETOther