dotnet general: What is the reason for the WCF error message
"Der Typeninitialisierer für System.ServiceModel.DiagnosticUtility hat eine
Ausnahme verursacht."
(WCF type init DiagnosticUtility failed) ?

created by the line
myServiceHost = New ServiceHost(GetType(CalculatorService))

and
Imports System.ServiceModel
Imports Contracts

Public Class CalculatorService
Implements ICalculator

Public Function Add(ByVal operand1 As Integer, ByVal operand2 As
Integer) As Integer Implements Contracts.ICalculator.Add
Return operand1 + operand2
End Function
End Class


thank you very much

[quoted text, click to view]

You will have to post the remainder of the exception. Please, always post
the complete exception, including any InnerException.

Please also include English translations, as ich spreche kein Deutsch. ;-)
--
--------------------------------------------------------------------------------
John Saunders | MVP – Windows Server System – Connected System Developer

I wrote <system.servicemodel> instead of <system.serviceModel> which caused
the Type init error message. The service type is OK.

Is there a wizard to create the WCF host-side app.config by reflecting
through contracts and services of a solution?

Thank you very much, Herbert

[quoted text, click to view]

When you write it, you should publish it. I am working on a logical N-tier
desktop solution that is using WCF, which I just encountered about two weeks
ago as a consultant. This thing is unbelievable. Maybe, because 17
consultants developed this application, that this thing is the most
a$$tacular and $hittacular thing I have ever seen as a developer, and I have
been a professional software developer since 1980 and started working MS
solutions in 1996. They are still trying to get the thing implemented at
this company, after a year of development.

I mean WCF doesn't look that complicated based on the book I am reading, I
see the concepts that they were trying to implement in the project, but it
is obvious that they missed the concepts of using WCF to some extent.

Dear Mr. Arnold,

I am programming network stuff for 35 years now, and WCF is clearly the best
thing that happened to me. It simply allows all kind of comm patterns with a
single metaphor.

First, I recommend to everybody to read two books:
Michelle L. Bustamente (contains both C# and VB.NET !)
J. Löwy (at a higher level, C# only, plenty of useful
tools)

For German speaking readers, access the blog of Mr. Christian Weyer (of
Thinktecture).

Yes, there are some unfinished surfaces: most WCF tools float around not
integrated in VS.2008, and there is no guidance/wizard about which
combination of parameters create a working/nonworking configuration.

The only thing I really miss is a configurable authentication/authorization
security subsystem (role providers) that allows speedy rollout of intranet
apps.

And yes, you need a clear design upfront, as WCF leads to multithreading the
host.
I redesiged my server apps in favor of WCF.

Memory transactions are high on my wishlist for VS.next

I hope Microsoft can improve this with a VS.2008 service pack.