(German version may be written at a later time / Deutsche Version wird gegebenenfalls später geschrieben) This post combines several concepts from several posts about BizTalk Workflow Services . You should read the intro , about flow control , about send&receive activities and about the little...
Posted to
Andreas Erben's posts
by
Andreas Erben
on
10-02-2008
Filed under:
Filed under: Windows Communication Foundation, WCF, .NET 3.0, VS 2005, Visual Studio 2005, BizTalk, .NET, Visual Studio 2008, VS 2008, .NET 3.5, BPM, Workflow, WF, Windows Workflow Foundation, Cloud Computing, Cloud, BizTalk Services, Cloud Services, OSLO, BizTalk Workflow Services
(German version maybe coming later / deutsche Version folgt eventuell später) http://workflow.biztalk.net now offers a CTP of BizTalk Workflow Services. Let's look at what that means. First you should download the latest version of the SDK. Right now this is the file " BizTalk Services...
Posted to
Andreas Erben's posts
by
Andreas Erben
on
08-05-2008
Filed under:
Filed under: .NET 3.0, VS 2005, Visual Studio 2005, BizTalk, BizTalk Server, .NET, Visual Studio 2008, VS 2008, .NET 3.5, BPM, Workflow, WF, Windows Workflow Foundation, SOA, Cloud Computing, Cloud, BizTalk Services, Cloud Services
Damir recently posted about a WCF designer, or rather that there is no WCF designer yet and it does not seem to be on the immediate roadmap for Orcas / Visual Studio 2008. Let me look deeper into the promise of the WCF designer.. Chris Smith said in early 2006 he is working on the WCF designer experience...
When working with Windows Presentation Foundation (WPF) you quickly run into limitations of current tool support and also encounter unexpected limitations. This may or not change with the release of "Orcas", however, at the time of the initial post, Orcas is not available. This post will be...
In a WCF project we recently received a WSDL from our customer that we needed to build a client/proxy to. So we used svcutil.exe to generate the C#-code we wanted. To our surprise, the code did not contain the types of the contract we expected, but something like this: [System.CodeDom.Compiler.GeneratedCodeAttribute...