dotnet web services enhancements: I know this is an old question but I cannot find any of the previous posting
wrt this issue.

We are finally upgrading to VS 2008 and .NET 3.5 from VS 2003 and .NET 1.1.
We have Windows forms, ASP.Net code and Windows services that interface with
3rd party web services that require the DIME attachments. We developed
libraries that are used in all three environments. The proxies are all setup
to use WSE 2.0 SP3. I also have the configuration settings from the .NET 1.1
implementation.

I'm getting the

WSE032: There was an error loading the microsoft.web.services2 configuration
section.

error in the Windows forms application.

I know it is stated that .NET 2.0 supports WSE 2.0 SP3 and that VS 2008 does
not provide the interface that VS 2003 does. However, I cannot find any
documentation on what is specifically necessary to implement WSE 2.0 SP3 in
..NET 2.0. Or specifically what causes the above error.

Thanks for your help - Rich F.

Below are the relavent app.config sections:
-------------------------------
<configSections>
<section name="microsoft.web.services2"
type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration,
Microsoft.Web.Services2, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" />
</configSections>

<microsoft.web.services2>
<diagnostics>
<trace enabled="true" input="Trace/Response.xml"
output="Trace/Request.xml" />
<detailedErrors enabled="true" />
</diagnostics>
<security>
<securityTokenManager type="IRSSaml.SamlTokenManager, IRSSaml"
xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" qname="saml:Assertion" />
<securityTokenManager type="IRSSaml.UserTokenManager, IRSSaml,
DATWebService"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
qname="wsse:UsernameToken" />
</security>
<messaging>
<executionTimeout value="300" />
<maxRequestLength>-1</maxRequestLength>
</messaging>
</microsoft.web.services2>
-----------------------------------
Note: Same error if I change the version to 2.0.3.0.

Below is sample code from the proxies:
-----------------------------------
/// <remarks/>
[System.Diagnostics.DebuggerStepThroughAttribute()]
[System.ComponentModel.DesignerCategoryAttribute("code")]
[System.Web.Services.WebServiceBindingAttribute(Name="InitialLogin",
Namespace="http://www.irs.gov/a2a/mef/MeFMSIServices")]
public class InitialLoginClass :
Microsoft.Web.Services2.WebServicesClientProtocol
{

public MeFHeaderType MeF;

/// <remarks/>
public InitialLoginClass()
{
this.Url = ConfigurationSettings.AppSettings.Get("WebServiceURL") +
"/a2a/mef/InitialLogin";
this.Timeout =
int.Parse(ConfigurationSettings.AppSettings.Get("WebServiceTimeout"));
}

/// <remarks/>
[System.Web.Services.Protocols.SoapHeaderAttribute("MeF",
Direction=System.Web.Services.Protocols.SoapHeaderDirection.InOut)]
[System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://www.irs.gov/a2a/mef/InitialLogin",
Use=System.Web.Services.Description.SoapBindingUse.Literal,
ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Bare)]
[return:
System.Xml.Serialization.XmlElementAttribute("InitialLoginResponse",
Namespace="http://www.irs.gov/a2a/mef/MeFMSIServices.xsd")]
public InitialLoginResponseType
InitialLogin([System.Xml.Serialization.XmlElementAttribute(Namespace="http://www.irs.gov/a2a/mef/MeFMSIServices.xsd")]
InitialLoginRequestType InitialLoginRequest)
{
object[] results = this.Invoke("InitialLogin", new object[]
{InitialLoginRequest});
return ((InitialLoginResponseType)(results[0]));
}

/// <remarks/>
public System.IAsyncResult BeginInitialLogin(InitialLoginRequestType
InitialLoginRequest, System.AsyncCallback callback, object asyncState)
{
return this.BeginInvoke("InitialLogin", new object[]
{InitialLoginRequest}, callback, asyncState);
}

/// <remarks/>
public InitialLoginResponseType EndInitialLogin(System.IAsyncResult
asyncResult)
{
object[] results = this.EndInvoke(asyncResult);
return ((InitialLoginResponseType)(results[0]));
}
}

Hi Rich,

From your description, you have a WSE 2.0 webservice client used in a
converted VS 2008 .NET 3.5 project(winform). When you try running the
application, it report an exception indicate that the configuration can not
be loaded, correct?

Since the error indicate the configuration section can not be loaded. I
would suggest you first check whether WSE 2.0 runtime assmblies has been
correcctly installed into the GAC. When .net try parsing a custom section,
it will first request the certain custom section type from the assemblies
specified in configuration.

You can also try creating a very simple WSE 2.0 client application (in vs
2003) and convert it to VS 2008 and run it to see whether it can run
correctly. If that also fails, there must be something incorrect with the
WSE runtime. Otherwise, we may focus on the specific WSE client project.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
From: "Rich Fowler" <RJF@newsgroup.nospam>
Subject: DIME WSE 2.0 in .NET 2.0
Date: Wed, 9 Apr 2008 14:48:36 -0600


I know this is an old question but I cannot find any of the previous
posting
wrt this issue.

We are finally upgrading to VS 2008 and .NET 3.5 from VS 2003 and .NET 1.1.
We have Windows forms, ASP.Net code and Windows services that interface
with
3rd party web services that require the DIME attachments. We developed
libraries that are used in all three environments. The proxies are all
setup
to use WSE 2.0 SP3. I also have the configuration settings from the .NET
1.1
implementation.

I'm getting the

WSE032: There was an error loading the microsoft.web.services2
configuration
section.

error in the Windows forms application.

I know it is stated that .NET 2.0 supports WSE 2.0 SP3 and that VS 2008
does
not provide the interface that VS 2003 does. However, I cannot find any
documentation on what is specifically necessary to implement WSE 2.0 SP3 in
..NET 2.0. Or specifically what causes the above error.

Thanks for your help - Rich F.

Below are the relavent app.config sections:
-------------------------------
<configSections>
<section name="microsoft.web.services2"
type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration,
Microsoft.Web.Services2, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" />
</configSections>

<microsoft.web.services2>
<diagnostics>
<trace enabled="true" input="Trace/Response.xml"
output="Trace/Request.xml" />
<detailedErrors enabled="true" />
</diagnostics>
<security>
<securityTokenManager type="IRSSaml.SamlTokenManager, IRSSaml"
xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" qname="saml:Assertion" />
<securityTokenManager type="IRSSaml.UserTokenManager, IRSSaml,
DATWebService"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri
ty-secext-1.0.xsd"
qname="wsse:UsernameToken" />
</security>
<messaging>
<executionTimeout value="300" />
<maxRequestLength>-1</maxRequestLength>
</messaging>
</microsoft.web.services2>
-----------------------------------
Note: Same error if I change the version to 2.0.3.0.

Below is sample code from the proxies:
-----------------------------------
/// <remarks/>
[System.Diagnostics.DebuggerStepThroughAttribute()]
[System.ComponentModel.DesignerCategoryAttribute("code")]
[System.Web.Services.WebServiceBindingAttribute(Name="InitialLogin",
Namespace="http://www.irs.gov/a2a/mef/MeFMSIServices")]
public class InitialLoginClass :
Microsoft.Web.Services2.WebServicesClientProtocol
{

public MeFHeaderType MeF;

/// <remarks/>
public InitialLoginClass()
{
this.Url = ConfigurationSettings.AppSettings.Get("WebServiceURL") +
"/a2a/mef/InitialLogin";
this.Timeout =
int.Parse(ConfigurationSettings.AppSettings.Get("WebServiceTimeout"));
}

/// <remarks/>
[System.Web.Services.Protocols.SoapHeaderAttribute("MeF",
Direction=System.Web.Services.Protocols.SoapHeaderDirection.InOut)]

[System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://www.irs.g
ov/a2a/mef/InitialLogin",
Use=System.Web.Services.Description.SoapBindingUse.Literal,
ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Bare)]
[return:
System.Xml.Serialization.XmlElementAttribute("InitialLoginResponse",
Namespace="http://www.irs.gov/a2a/mef/MeFMSIServices.xsd")]
public InitialLoginResponseType
InitialLogin([System.Xml.Serialization.XmlElementAttribute(Namespace="http:/
/www.irs.gov/a2a/mef/MeFMSIServices.xsd")]
InitialLoginRequestType InitialLoginRequest)
{
object[] results = this.Invoke("InitialLogin", new object[]
{InitialLoginRequest});
return ((InitialLoginResponseType)(results[0]));
}

/// <remarks/>
public System.IAsyncResult BeginInitialLogin(InitialLoginRequestType
InitialLoginRequest, System.AsyncCallback callback, object asyncState)
{
return this.BeginInvoke("InitialLogin", new object[]
{InitialLoginRequest}, callback, asyncState);
}

/// <remarks/>
public InitialLoginResponseType EndInitialLogin(System.IAsyncResult
asyncResult)
{
object[] results = this.EndInvoke(asyncResult);
return ((InitialLoginResponseType)(results[0]));
}

Hi Steven,

After installing the WSE 2.0 SP 3 runtime (full developer install), I copied
the .NET 1.1 application over to the new development system and everything
worked correctly (ie. WSE is installed correctly).

I was able to get more information wrt the error message.

InnerException {"An error occurred creating the configuration section
handler for microsoft.web.services2:
The given assembly name or codebase was invalid. (Exception from HRESULT:
0x80131047)
(D:\\Form990Development\\Form990DevelopmentSoftware\\FedStateBackend\\bin\\Debug\\FedStateBackend.vshost.exe.Config
line 14)"}
System.Exception {System.Configuration.ConfigurationErrorsException}

Part of the stack trace:

at
Microsoft.Web.Services2.Configuration.WebServicesConfiguration.Initialize()
at
Microsoft.Web.Services2.Configuration.WebServicesConfiguration.get_ReferralConfiguration()
at Microsoft.Web.Services2.Referral.ReferralCache.Initialize()
at Microsoft.Web.Services2.Referral.ReferralCache.ResolvePath(Uri uri)
at
Microsoft.Web.Services2.WebServicesClientProtocol.set_Destination(EndpointReference
value)
at Microsoft.Web.Services2.WebServicesClientProtocol.set_Url(String value)
IRSProxies40.LoginService.LoginClass..ctor() in
D:\\Form990Development\\Form990DevelopmentSoftware\\IRSProxies40\\LoginService.cs:line
265
.....

Line 14 is the start of the microsoft.web.services2 section. This error
happens when creating an instance of the proxy. If I comment out the
security section containing my custom SAML token managers, I get beyound
this point in the code. Here's the security section:

<security>
<securityTokenManager type="IRSSaml.SamlTokenManager, IRSSaml"
xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" qname="saml:Assertion" />
<securityTokenManager type="IRSSaml.UserTokenManager, IRSSaml,
DATWebService"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
qname="wsse:UsernameToken" />
</security>

The IRSSam dll is targeted to .NET 3.5. Does this dll need to be .NET 1.1
(this is just a guess).

Thanks - Rich F.


[quoted text, click to view]