patterns & practices – Enterprise Library

New Post: Enterprise library validation block is generating exception when it is used with WF4.0

vivekvishal — Fri, 25 May 2012 08:51:21 GMT

Thanks,

Yes i am using Async one. I have implemented the changes suggested on that link but no luck.

operation.SyncMethod and operation.BeginMethod both return null for WF4.0 services. Is there any way to resolve this issue?

I want to use validation block to validate request parameter.

New Post: Enterprise library validation block is generating exception when it is used with WF4.0

vivekvishal — Fri, 25 May 2012 08:51:21 GMT

Thanks,

Yes i am using Async one. I have implemented the changes suggested on that link but no luck.

operation.SyncMethod and operation.BeginMethod both return null for WF4.0 services. Is there any way to resolve this issue?

I want to use validation block to validate request parameter.

New Post: Enterprise library validation block is generating exception when it is used with WF4.0

randylevy — Fri, 25 May 2012 08:37:53 GMT

Are you using an Asynchronous service? I don't believe asynchronous services are supported. See http://entlib.codeplex.com/discussions/31493 for discussion and a potential code change to Enterprise Library to support async.

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com

New Post: Enterprise library validation block is generating exception when it is used with WF4.0

randylevy — Fri, 25 May 2012 08:37:53 GMT

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com

New Post: Enterprise library validation block is generating exception when it is used with WF4.0

vivekvishal — Fri, 25 May 2012 07:57:58 GMT

Hi Randy,

Thanks for your replay.

I am using Enterprise library Validation block with WF 4.0 (Windows Forkflow foundation ) not for WCF, for WCF service it is working well but for WF service it it not working.

It is generating exception here.

private bool HasValidationAssertions(OperationDescription operation)

{

MethodInfo

methodInfo = operation.SyncMethod;

if (methodInfo == null )

{

throw new ArgumentNullException("operation.SyncMethod"

);

}

return methodInfo.GetCustomAttributes(typeof(ValidatorAttribute), false

).Length > 0 || HasParametersWithValidationAssertions(methodInfo.GetParameters());

}

in class public class ValidationBehavior

Please help me to resolve this issue.

New Post: Enterprise library validation block is generating exception when it is used with WF4.0

vivekvishal — Fri, 25 May 2012 07:57:58 GMT

Hi Randy,

Thanks for your replay.

I am using Enterprise library Validation block with WF 4.0 (Windows Forkflow foundation ) not for WCF, for WCF service it is working well but for WF service it it not working.

It is generating exception here.

private bool HasValidationAssertions(OperationDescription operation)

{

MethodInfo

methodInfo = operation.SyncMethod;

if (methodInfo == null )

{

throw new ArgumentNullException("operation.SyncMethod"

);

}

return methodInfo.GetCustomAttributes(typeof(ValidatorAttribute), false

).Length > 0 || HasParametersWithValidationAssertions(methodInfo.GetParameters());

}

in class public class ValidationBehavior

Please help me to resolve this issue.

New Post: Enterprise library validation block is generating exception when it is used with WF4.0

randylevy — Fri, 25 May 2012 07:01:25 GMT

For the record the posted configuration was:

<?xml version="1.0" encoding="utf-8" ?>
<configuration> 
  <system.web>
    <compilation debug="true" targetFramework="4.0" />
  </system.web>
  <system.serviceModel>
    <services>
      <service name="Service1" behaviorConfiguration="PublishMetadata">
        <endpoint address=""
        binding="basicHttpBinding" contract="ITestService" behaviorConfiguration="Validation"/>       
      </service>      
      </services>

    <behaviors>
      <endpointBehaviors>
        <behavior name="Validation">
          <validation enabled="true"/>
        </behavior>
      </endpointBehaviors>

      <serviceBehaviors>
        <behavior name="PublishMetadata">
          <serviceMetadata httpGetEnabled="true"/>
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <extensions>
      <behaviorExtensions>
        <add name="validation"
             type="Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF.ValidationElement, Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF, Version=4.1.0.0, Culture=neutral, PublicKeyToken=null" />
      </behaviorExtensions>
    </extensions>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
  </system.serviceModel>
  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true"/>
  </system.webServer>
</configuration>

And the error is:

Server Error in '/' Application.
Value cannot be null. Parameter name: operation.SyncMethod Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentNullException: Value cannot be null. Parameter name: operation.SyncMethod

It looks like you are using Validation with WCF. You said the above error occurs when simply browsing the service metadata.

Are you using a custom build of Enterprise Library? The reason I ask is because the configuration indicates a non-signed assembly. Usually the type would be

type="Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF.ValidationElement, Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

This is the configuration I'm successfully using:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <system.web>
    <compilation debug="true" targetFramework="4.0" />
  </system.web>
  <system.serviceModel>
    <services>
      <service name="Service1">
        <endpoint address="http://localhost:59355/"
        binding="basicHttpBinding" contract="ValidationWcfBaseClass.IMyService" />
      </service>
    </services>

    <behaviors>
      <endpointBehaviors>
        <behavior name="Validation">          
          <validation enabled="true" ruleset="MyRuleset"/>
        </behavior>
      </endpointBehaviors>

      <serviceBehaviors>
        <behavior>
          <serviceMetadata httpGetEnabled="true"/>
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <extensions>
      <behaviorExtensions>
        <add name="validation"
             type="Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF.ValidationElement, Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      </behaviorExtensions>
    </extensions>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
  </system.serviceModel>
  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true"/>
  </system.webServer>
</configuration>

And the service code is:

    public class Service1 : IMyService
    {
        public bool ExecuteCommand(CommandBase command)
        {
            return true;
        }
    }

    [ValidationBehavior]
    [ServiceContract]
    public interface IMyService
    {
        [FaultContract(typeof(ValidationFault))]
        [OperationContract]
        bool ExecuteCommand(CommandBase command);
    }

    [DataContract]
    public class CommandBase
    {
        [DataMember]
        [StringLengthValidator(5)]
        public string Name
        {
            get;
            set;
        }
    }

At runtime the service will need to access to the following assemblies:

Microsoft.Practices.EnterpriseLibrary.Common.dll
Microsoft.Practices.EnterpriseLibrary.Validation.dll
Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF.dll
Microsoft.Practices.ObjectBuilder2.dll
Microsoft.Practices.Unity.dll

If that doesn't help I would recommend posting some code that demonstrates the issue.

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com

New Post: Enterprise library validation block is generating exception when it is used with WF4.0

randylevy — Fri, 25 May 2012 07:01:25 GMT

For the record the posted configuration was:

<?xml version="1.0" encoding="utf-8" ?>
<configuration> 
  <system.web>
    <compilation debug="true" targetFramework="4.0" />
  </system.web>
  <system.serviceModel>
    <services>
      <service name="Service1" behaviorConfiguration="PublishMetadata">
        <endpoint address=""
        binding="basicHttpBinding" contract="ITestService" behaviorConfiguration="Validation"/>       
      </service>      
      </services>

    <behaviors>
      <endpointBehaviors>
        <behavior name="Validation">
          <validation enabled="true"/>
        </behavior>
      </endpointBehaviors>

      <serviceBehaviors>
        <behavior name="PublishMetadata">
          <serviceMetadata httpGetEnabled="true"/>
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <extensions>
      <behaviorExtensions>
        <add name="validation"
             type="Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF.ValidationElement, Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF, Version=4.1.0.0, Culture=neutral, PublicKeyToken=null" />
      </behaviorExtensions>
    </extensions>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
  </system.serviceModel>
  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true"/>
  </system.webServer>
</configuration>

And the error is:

Server Error in '/' Application.
Value cannot be null. Parameter name: operation.SyncMethod Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentNullException: Value cannot be null. Parameter name: operation.SyncMethod

It looks like you are using Validation with WCF. You said the above error occurs when simply browsing the service metadata.

Are you using a custom build of Enterprise Library? The reason I ask is because the configuration indicates a non-signed assembly. Usually the type would be

type="Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF.ValidationElement, Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

This is the configuration I'm successfully using:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <system.web>
    <compilation debug="true" targetFramework="4.0" />
  </system.web>
  <system.serviceModel>
    <services>
      <service name="Service1">
        <endpoint address="http://localhost:59355/"
        binding="basicHttpBinding" contract="ValidationWcfBaseClass.IMyService" />
      </service>
    </services>

    <behaviors>
      <endpointBehaviors>
        <behavior name="Validation">          
          <validation enabled="true" ruleset="MyRuleset"/>
        </behavior>
      </endpointBehaviors>

      <serviceBehaviors>
        <behavior>
          <serviceMetadata httpGetEnabled="true"/>
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <extensions>
      <behaviorExtensions>
        <add name="validation"
             type="Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF.ValidationElement, Microsoft.Practices.EnterpriseLibrary.Validation.Integration.WCF, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      </behaviorExtensions>
    </extensions>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
  </system.serviceModel>
  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true"/>
  </system.webServer>
</configuration>

And the service code is:

    public class Service1 : IMyService
    {
        public bool ExecuteCommand(CommandBase command)
        {
            return true;
        }
    }

    [ValidationBehavior]
    [ServiceContract]
    public interface IMyService
    {
        [FaultContract(typeof(ValidationFault))]
        [OperationContract]
        bool ExecuteCommand(CommandBase command);
    }

    [DataContract]
    public class CommandBase
    {
        [DataMember]
        [StringLengthValidator(5)]
        public string Name
        {
            get;
            set;
        }
    }

At runtime the service will need to access to the following assemblies:

If that doesn't help I would recommend posting some code that demonstrates the issue.

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com

New Post: Enterprise library validation block is generating exception when it is used with WF4.0

vivekvishal — Fri, 25 May 2012 05:23:27 GMT

Enterprise library validation block is not working with WF4.0 workflow service. When we configure it with WF4,0 workflow service is unable to start.

For more details you can refer this link .

http://social.msdn.microsoft.com/Forums/en/wfprerelease/thread/2f2198d0-ae06-40ab-abe8-0e52ee0249b2

Thanks....

New Post: Enterprise library validation block is generating exception when it is used with WF4.0

vivekvishal — Fri, 25 May 2012 05:23:27 GMT

Enterprise library validation block is not working with WF4.0 workflow service. When we configure it with WF4,0 workflow service is unable to start.

For more details you can refer this link .

http://social.msdn.microsoft.com/Forums/en/wfprerelease/thread/2f2198d0-ae06-40ab-abe8-0e52ee0249b2

Thanks....

New Post: IsolatedStorageTraceListenerData: The repository is not available

randylevy — Fri, 25 May 2012 03:05:32 GMT

Threading issues can be difficult to track down. Can you describe how you are using logging and perhaps post some code snippets?

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com

New Post: IsolatedStorageTraceListenerData: The repository is not available

randylevy — Fri, 25 May 2012 03:05:32 GMT

Threading issues can be difficult to track down. Can you describe how you are using logging and perhaps post some code snippets?

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com

New Post: IsolatedStorageTraceListenerData: The repository is not available

randylevy — Fri, 25 May 2012 03:05:32 GMT

Threading issues can be difficult to track down. Can you describe how you are using logging and perhaps post some code snippets?

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com

New Post: IsolatedStorageTraceListenerData: The repository is not available

randylevy — Fri, 25 May 2012 03:05:32 GMT

Threading issues can be difficult to track down. Can you describe how you are using logging and perhaps post some code snippets?

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com

New Post: IsolatedStorageTraceListenerData: The repository is not available

Trinition — Wed, 23 May 2012 11:55:25 GMT

I could try, but I'm not sure where to start. We have a 2-year development project in beta, with approximately 0.5M LoC in the Silverlight client. We recently added EntLib 5 Silverlight logging to it, logging to both IsolatedStorageTraceListenerData and RemoteServiceTraceListenerData. Through the remote listener, we see reports of the isolated listener's occasional failure from our production, beta environment. However, I've never managed to catch it in the act or even have a clue what portion of the client is leading to this. So I'm unsure of where to begin and making a repro solution to demonstrate the problem.

New Post: IsolatedStorageTraceListenerData: The repository is not available

Trinition — Wed, 23 May 2012 11:55:25 GMT

New Post: IsolatedStorageTraceListenerData: The repository is not available

Trinition — Wed, 23 May 2012 11:55:25 GMT

Created Issue: Enterprise library validation block is generating exception when it is used with WF4.0. [32758]

vivekvishal — Wed, 23 May 2012 09:39:50 GMT

Hi Team,
Enterprise library validation block is generating exception when it is used with wf4.0.
For details
Please refer this link.

http://social.msdn.microsoft.com/Forums/en/wfprerelease/thread/2f2198d0-ae06-40ab-abe8-0e52ee0249b2

New Post: IsolatedStorageTraceListenerData: The repository is not available

randylevy — Wed, 23 May 2012 06:20:40 GMT

You could be right. The actual TraceData call should be thread-safe since a Monitor.Enter is invoked if the TraceListener is not thread-safe (IsThreadSafe). However, if ApplyChanges() is called at the same time then this could potentially remove the storage reference out from under another Write request which could generate the "repository not available" message.

Can you post a small repro project?

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com

New Post: IsolatedStorageTraceListenerData: The repository is not available

randylevy — Wed, 23 May 2012 06:20:40 GMT

Can you post a small repro project?

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com