IWebCF - DotNetNuke WCF Services Module

RELEASED: IWebCF 01.00.00 (Jul 20, 2008)

Mon, 21 Jul 2008 16:29:50 GMT

Install this module using the normal module install process on a DotNetNuke 4.8+ http://DotNetNuke.com site on Windows Vista or Windows 2003/2008 server.

If you encounter errors / issues with using this module please post them in the Discussions are of this project.

Please use the Source Code tab in order to download the core code. You will need a local installation of DotNetNuke in order to use the source code version.

UPDATED RELEASE: IWebCF 01.00.00 (Jul 20, 2008)

Mon, 21 Jul 2008 16:29:50 GMT

Closed Issue: Issue: Exception is thrown when i try to browse the CoreService.svc

ITLackey — Mon, 21 Jul 2008 04:20:53 GMT

Closed Issue: Set Address button wont work the first time

ITLackey — Mon, 21 Jul 2008 04:19:59 GMT

You need to click the set Set Address button twice to set it the first time you use it after placing an instance of the module on a page.

Source code checked in, #12118

ITLackey — Mon, 21 Jul 2008 04:19:58 GMT

Fixed issue with needing to click the set address button twice to configure service address.

New Post: Problem: Getting exception while browsing my newly added web method in Iweb-CF

ITLackey — Mon, 21 Jul 2008 04:14:35 GMT

It appears that your configuration is incorrect. You have specified a binding of mexHttpBinding with a configuration name of ws2007HttpBinding for some of your endpoints:
<endpoint address="IComponent" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IComponent" contract="System.ComponentModel.IComponent" />

This will cause a conflict in binding type and binding configuration it should match the type and configuration name like this one:
<endpoint binding="ws2007HttpBinding" bindingConfiguration="ws2007HttpBinding" name="CoreService" contract="DotNetNuke.Modules.IWebCF.IWebCoreService" />

If you change the binding in the to ws2007HttpBinding then the name is valid, otherwise you could change the configuration name to mexHttpBinding. Either option should be valid.

I hope this helps.

Commented Issue: Issue: Exception is thrown when i try to browse the CoreService.svc

ITLackey — Mon, 21 Jul 2008 04:03:33 GMT

Sorry for the slow response, but could you please post the details of the exception.

New Post: Problem: Getting exception while browsing my newly added web method in Iweb-CF

akhtarrasool — Tue, 08 Jul 2008 07:23:19 GMT

I added a new web method in Iweb-CF..It complied without errors. When i browse DNN the service addresss is shown but when I click on the service address following exception is thrown

The binding at system.serviceModel/bindings/mexHttpBinding does not have a configured binding named 'ws2007HttpBinding'. This is an invalid value for bindingConfiguration.

My web.config looks like

<?xml version="1.0"?>
<configuration>
    <system.web>
        
        <webServices>
        </webServices>
        <webControls clientScriptsLocation="/aspnet_client/{0}/{1}/" />
        <httpRuntime executionTimeout="1500" maxRequestLength="512000" />
    </system.web>
    <system.serviceModel>
        <bindings>
            <basicHttpBinding>
                <binding name="basicHttpBinding" />
                <binding name="mtomHttpBinding" receiveTimeout="00:25:00" sendTimeout="00:25:00" maxBufferSize="524288000" maxReceivedMessageSize="524288000" messageEncoding="Mtom">
                    <readerQuotas maxArrayLength="524288000" />
                </binding>
            </basicHttpBinding>
            <ws2007HttpBinding>
                <binding name="ws2007HttpBinding">
                    <security mode="None">
                        <transport clientCredentialType="None" />
                        <message clientCredentialType="UserName" />
                    </security>
                </binding>
            </ws2007HttpBinding>
            <mexHttpBinding>
                <binding name="mexHttpBinding" />
            </mexHttpBinding>
        </bindings>
        <behaviors>
            <serviceBehaviors>
                <behavior name="DefaultBehavior">
                    <serviceMetadata httpGetEnabled="true" />
                    <serviceDebug includeExceptionDetailInFaults="true" />
                </behavior>
            </serviceBehaviors>
        </behaviors>
        <serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
        <services>
            <service behaviorConfiguration="DefaultBehavior" name="DotNetNuke.Modules.IWebCF.CoreService">
                <endpoint address="IComponent" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IComponent" contract="System.ComponentModel.IComponent" />
                <endpoint address="IDisposable" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IDisposable" contract="System.IDisposable" />
                <endpoint address="IParserAccessor" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IParserAccessor" contract="System.Web.UI.IParserAccessor" />
                <endpoint address="IUrlResolutionService" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IUrlResolutionService" contract="System.Web.UI.IUrlResolutionService" />
                <endpoint address="IDataBindingsAccessor" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IDataBindingsAccessor" contract="System.Web.UI.IDataBindingsAccessor" />
                <endpoint address="IControlBuilderAccessor" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IControlBuilderAccessor" contract="System.Web.UI.IControlBuilderAccessor" />
                <endpoint address="IControlDesignerAccessor" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IControlDesignerAccessor" contract="System.Web.UI.IControlDesignerAccessor" />
                <endpoint address="IExpressionsAccessor" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IExpressionsAccessor" contract="System.Web.UI.IExpressionsAccessor" />
                <endpoint address="INamingContainer" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="INamingContainer" contract="System.Web.UI.INamingContainer" />
                <endpoint address="IFilterResolutionService" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IFilterResolutionService" contract="System.Web.UI.IFilterResolutionService" />
                <endpoint address="IAttributeAccessor" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IAttributeAccessor" contract="System.Web.UI.IAttributeAccessor" />
                <endpoint address="INonBindingContainer" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="INonBindingContainer" contract="System.Web.UI.INonBindingContainer" />
                <endpoint address="IUserControlDesignerAccessor" binding="mexHttpBinding" bindingConfiguration="ws2007HttpBinding" name="IUserControlDesignerAccessor" contract="System.Web.UI.IUserControlDesignerAccessor" />
                <endpoint binding="ws2007HttpBinding" bindingConfiguration="ws2007HttpBinding" name="CoreService" contract="DotNetNuke.Modules.IWebCF.IWebCoreService" />
                <endpoint address="IWebFileManager" binding="ws2007HttpBinding" bindingConfiguration="ws2007HttpBinding" name="IWebFileManager" contract="DotNetNuke.Modules.IWebCF.IWebFileManager" />
                <endpoint address="IWebFileTransferManager" binding="basicHttpBinding" bindingConfiguration="mtomHttpBinding" name="IWebFileTransferManager" contract="DotNetNuke.Modules.IWebCF.IWebFileTransferManager" />
                <endpoint address="IWebPortalManager" binding="ws2007HttpBinding" bindingConfiguration="ws2007HttpBinding" name="IWebPortalManager" contract="DotNetNuke.Modules.IWebCF.IWebPortalManager" />
                <endpoint address="IWebUserManager" binding="ws2007HttpBinding" bindingConfiguration="ws2007HttpBinding" name="IWebUserManager" contract="DotNetNuke.Modules.IWebCF.IWebUserManager" />
            </service>
        </services>
    </system.serviceModel>
</configuration>

CAn anyone help me in this..

Created Issue: Issue: Exception is thrown when i try to browse the CoreService.svc

akhtarrasool — Tue, 08 Jul 2008 07:17:11 GMT

I added a new web method in Iweb-CF..It complied without errors. When i browse DNN the service addresss is shown but when I click on the service address following exception is thrown

New Post: Beta Testing IWebCF_01.00.00_Beta06102008.zip

adefwebserver — Wed, 11 Jun 2008 13:30:17 GMT

Please check the Issues Log (http://www.codeplex.com/IWebCF/WorkItem/List.aspx) and then post your Beta Testing results here:

o Your DotNetNuke version

o Your operating system

o Results testing IWebCF Connector

o Results testing IWebCF Explorer

Created Issue: Set Address button wont work the first time

adefwebserver — Wed, 11 Jun 2008 13:06:17 GMT

You need to click the set Set Address button twice to set it the first time you use it after placing an instance of the module on a page.

Source code checked in, #9263

ITLackey — Tue, 10 Jun 2008 16:22:36 GMT

Removed delete fle operation from service and from explorer client, cleaned out my username and password from default settings, corrected core connector install path, fixed bug with changing website address in core connector client, removed encrypt and unencrypt operations from service and core connector.

CLOSED ISSUE: Error creating new folder

ITLackey — Sun, 08 Jun 2008 00:31:39 GMT

An issue has been reported thatfolder ceration is failing. We are currently working to resolve this issue. If you experince this issue, please vote for this work item.

CLOSED ISSUE: Error uploading file

ITLackey — Sun, 08 Jun 2008 00:31:38 GMT

An issue has been reported that file uploading is failing. We are currently working to resolve this issue. If you experince this issue, please vote for this work item.

Source code checked in, #8827

ITLackey — Sun, 08 Jun 2008 00:31:32 GMT

Updated install packages for clients.

COMMENTED ISSUE: Error creating new folder

ITLackey — Thu, 29 May 2008 04:16:21 GMT

An issue has been reported thatfolder ceration is failing. We are currently working to resolve this issue. If you experince this issue, please vote for this work item.
Comments: Associated with changeset 7313.

COMMENTED ISSUE: Error uploading file

ITLackey — Thu, 29 May 2008 04:16:19 GMT

An issue has been reported that file uploading is failing. We are currently working to resolve this issue. If you experince this issue, please vote for this work item.
Comments: Associated with changeset 7313.

Source code checked in

ITLackey — Thu, 29 May 2008 04:16:17 GMT

Modified client and service to correct issues with adding folders and uploading files.

CREATED ISSUE: Error creating new folder

ITLackey — Wed, 21 May 2008 05:17:57 GMT

An issue has been reported thatfolder ceration is failing. We are currently working to resolve this issue. If you experince this issue, please vote for this work item.

CREATED ISSUE: Error uploading file

ITLackey — Wed, 21 May 2008 05:17:18 GMT

An issue has been reported that file uploading is failing. We are currently working to resolve this issue. If you experince this issue, please vote for this work item.