Overview of WCF Architecture
Service-Oriented Development by Using WCF

read more

read more
[Source: http://geekswithblogs.net/EltonStoneman]
You can actually use this to check for correct deployment of any .NET stack where you want to verify that assemblies and dependencies in the GAC are correctly deployed. Mostly I use it for troubleshooting when BizTalk can’t load maps or schemas.
With PowerShell you can instantiate any .NET object, and if there are any issues in loading the assembly or its dependencies, you’ll see the whole error message, which might otherwise be truncated or buried in a stack trace somewhere.
Firstly load the assembly so PowerShell can locate the type. Use the full name if you’re loading from the GAC, or the basic name if you’ve navigated to a program’s bin directory:
[System.Reflection.Assembly]::Load(‘x.y.z.Integration.Maps, Version=1.0.0.0, Culture=neutral, PublicKeyToken=104fee075643f423’)
Next use Activator to create and unwrap an instance from the assembly and type name. If this fails, it will highlight any issues with missing dependencies:
$map = [System.Activator]::CreateInstance(‘x.y.z.Integration.Maps, Version=1.0.0.0, Culture=neutral, PublicKeyToken=104fee075643f423’, ‘x.y.z.Integration.Maps.x_yService_Getz’).Unwrap()
If you don’t have any error messages, then your object ($map in this example) is ready to use, and you’ve verified the deployment is correct. For BizTalk maps you have the additional benefit that running ToString() (or just entering the object name) will show you the underlying XSLT:
$map
If you get do get errors along the way, they should tell you where the problem is. You can get more detail by querying the PowerShell $error object.
Now it is the timeline of the development tools only. It is a little bit “unofficial”. For example, I included the ESB but not RFID. Versions 2000 and 2002 are not covered , there only placeholders. Mainly because since the 2004 version it is completely new product from many points of view, including the developer’s point of view.
It is interesting, the main tools: the Schema Editor, Mapper, Orchestration Editor, Pipeline Editor were not changed since version 2004. BizTalk was heavily expanded over new areas and technologies. The core principle was “do no change things that work, add new features”.
Several tools were discarded, because of lack of user’s interest or because of the technology trends. For example, HWS, BAS, ODBA.
Please, let me know if you find out errors or weak points. Suggestions would be very-very appreciated.
It is version 1.
Here are some great resources to get you started.
If you have been working with Visual Studio for a while I am sure you came across situations where the TFS Server was unavailable when you were working on the Project source code. Its nice to know that TFS allows you to continue working on your project offline when your TFS server is down. That’s really cool and you do that by opening your Project Solution file (.sln) and if TFS is not available it will ask if you want to work offline and lets you work offline.
read more
|
Property
|
Values
|
Description
|
|
IsScalable
|
True | False
|
Indicates if transform should always be scalable
|
|
MapName
|
{XslUrl} | {BizTalk Map Name}
|
Defines the XSL URL or fully qualified map name to use for transformation
|
|
MessageType
|
{namespace}#{root}
|
Target message type
|
|
SchemaStrongName
|
{Class}, {Assembly}, Version={}, Culture={}, PublicKeyToken={}
|
Fully qualified .Net schema type name
|
|
TransformUsing
|
XslStylesheet | BizTalkMap
|
Indicates what kind of transformation is used
|
Since SO-Aware was a few months ago, our team has produced a considerable amount of interesting content that cover some of the most important patterns and techniques that will help developers and architects to be even more successful adopting this technology…(read more)
Error:
Error SQL01268: .Net SqlClient Data Provider: Msg 2627, Level 14, State 1, Line 3 Violation of PRIMARY KEY constraint ‘PK_ComponentTypeLu’. Cannot insert duplicate key in object ‘dbo.ComponentTypeRef’.
read more
I have posted online all the sample code from my book, “Applied Architecture Patterns on the Microsoft Platform”. You can download it at http://www.biztalkgurus.com/media/p/30260.aspx. This code contains various samples using BizTalk, BizTalk ESB Toolkit, Server AppFabric, SharePoint 2010, .Net 4.0 Workflow, SQL, Stream Insight, Azure, SQL Azure, Platform AppFabric Service Bus, Server AppFabric Caching, and more. Of course, you will get the most benefit of this code using it alongside with the chapter of the book that walks through it.
The book is available now on Amazon.com and PacktPub.com.
Thanks to our friends in Sweden we now have a Commercial for our book! I have not seen many commercials for Technology books, but this video gives some context of the “why” behind our book. You get to hear from Richard, Ewan, and myself about why we wrote the book and why we picked to release the book at the European BizTalk Conference in Stockholm, Sweden to a room full of top notch, hard-core BizTalk people.
This video is available at http://www.biztalkgurus.com/media/p/30247.aspx and on YouTube.
If you are looking for more detailed information on the types of solutions covered in the book, I have put together a video walking through Chapter 10 – Repair and Resubmit with Human Workflow. This solution uses SharePoint 2010 to store customer information. This information is processed by a .Net 3.5 workflow that sends the data to a Server AppFabric hosted .Net 4.0 workflow service for processing.
This video is available at http://www.biztalkgurus.com/media/p/30249.aspx and on YouTube.