I'm sure you're not the only one having these issues so post away!

On Feb 22, 2012, at 11:14 AM, RyanL wrote:

> Google is my friend.
> Sorry to post so much here, these were all IIS issues.
> Resolved with the following:
> http://wishmesh.com/2010/08/iis-7-5-error-handler-pagehandlerfactory-integrated-has-a-bad-module-managedpipelinehandler-in-its-module-list/
> 
> On Feb 22, 9:27 am, RyanL <[email protected]> wrote:
>> I believe this may be a problem with IIS.  It runs locally in debug.
>> First, I did need to install WCF in IIS, following the instructions in
>> this 
>> article:http://www.dotnetthoughts.net/2010/04/23/deploying-wcf-service-in-iis...
>> Now, I get a new error about 'Castle.Core' assembly being built by a
>> runtime newer than the loaded runtime.  In IIS my site is using .NET
>> framework v4.0, so I'm not sure what is causing that problem.
>> 
>> Thanks for any assistance.
>> 
>> Error:
>> Could not load file or assembly 'Castle.Core' or one of its
>> dependencies. This assembly is built by a runtime newer than the
>> currently loaded runtime and cannot be loaded.
>> 
>> On Feb 22, 7:08 am, Craig Neuwirt <[email protected]> wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> Is it possible to send me a unit test of solution that I can run?
>> 
>>> On Feb 21, 2012, at 3:03 PM, RyanL wrote:
>> 
>>>> I'm trying to use Castle.Facilities.WcfIntegration.
>>>> It works great when debugging in Visual Studio.  I am then able to
>>>> connect tohttp://localhost:53349/ServiceName.svc?wsdl.  However, once
>>>> I publish and deploy to IIS I cannot connect to it (using
>>>> http://localhost:95/ServiceName.svc?wsdl.  I get the following error:
>> 
>>>> Error: Cannot obtain Metadata fromhttp://localhost:95/ServiceName.svc?wsdl
>>>> If this is a Windows (R) Communication Foundation service to which you
>>>> have access, please check that you have enabled metadata publishing at
>>>> the specified address.  For help enabling metadata publishing, please
>>>> refer to the MSDN documentation 
>>>> athttp://go.microsoft.com/fwlink/?LinkId=65455.WS-Metadata
>>>> Exchange Error    URI:http://localhost:95/ServiceName.svc?wsdl
>>>> Metadata contains a reference that cannot be resolved: 'http://
>>>> localhost:95/ServiceName.svc?wsdl'.    The remote server returned an
>>>> unexpected response: (405) Method Not Allowed.    The remote server
>>>> returned an error: (405) Method Not Allowed.HTTP GET Error    URI:
>>>> http://localhost:95/ServiceName.svc?wsdl  There was an error
>>>> downloading 'http://localhost:95/ServiceName.svc?wsdl'.    The request
>>>> failed with HTTP status 404: Not Found.
>> 
>>>> Here is my installer:
>> 
>>>>    public class WcfServiceInstaller:IWindsorInstaller
>>>>    {
>>>>            public void Install(IWindsorContainer container,
>>>> IConfigurationStore store)
>>>>            {
>>>>                var returnFaults = new ServiceDebugBehavior
>>>>                                       {
>> 
>>>> IncludeExceptionDetailInFaults = true,
>>>>                                           HttpHelpPageEnabled = true
>>>>                                       };
>>>>                var metadata = new ServiceMetadataBehavior
>>>> {HttpGetEnabled = true};
>> 
>>>>                container.AddFacility<WcfFacility>()
>>>>                            .Register(
>> 
>>>> Component.For<IServiceBehavior>().Instance(returnFaults),
>> 
>>>> Component.For<IServiceBehavior>().Instance(metadata),
>>>>                                Component.For<IMyService>()
>>>>                                .Named("MyService")
>>>>                                .ImplementedBy<MyService>()
>>>>                                .DependsOn(
>>>>                                    Property.ForKey("number").Eq(42))
>>>>                                );
>>>>            }
>>>>    }
>> 
>>>> And my Svc file:
>> 
>>>> <% @ServiceHost Service="MyService"
>>>>    Factory="Castle.Facilities.WcfIntegration.DefaultServiceHostFactory,
>>>> Castle.Facilities.WcfIntegration" %>
>> 
>>>> Here is my powershell deploy to set up the app pool and site.
>> 
>>>>            .$env:SystemRoot\System32\inetsrv\appcmd.exe add apppool -Name:
>>>> $apppoolname -managedRuntimeVersion:v4.0
>>>>            .$env:SystemRoot\System32\inetsrv\appcmd.exe add site /name:
>>>> $sitename /bindings:http/*:95: /physicalPath:$targetpath
>> 
>>>> Thanks for any assistance.
>> 
>>>> --
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Castle Project Users" group.
>>>> To post to this group, send email to [email protected].
>>>> To unsubscribe from this group, send email to 
>>>> [email protected].
>>>> For more options, visit this group 
>>>> athttp://groups.google.com/group/castle-project-users?hl=en.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Castle Project Users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/castle-project-users?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Castle Project Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/castle-project-users?hl=en.

Reply via email to