Compatibility between beta 2 and June CTP

Question

I'm porting my app to the June CTP and thought that the wire formats would be sufficiently stable to try to convert my client to the June CTP and let it connect with the existing beta 2 server.

However, this does not seem to work. I encountered two problems:

1) svc_util returns a number of warnings:

Attempting to download metadata from 'http://www.blogoholic.net/blogoholicwebser
vice/service.svc' using WS-Metadata Exchange or DISCO.
Error: Cannot import the security policy. The protection requirements for the se
cure conversation bootstrap binding are not supported. Protection requirements f
or the secure conversation bootstrap must require both the request and the respo
nse to be signed and encrypted.

Error: Cannot import the security policy. The protection requirements for the se
cure conversation bootstrap binding are not supported. Protection requirements f
or the secure conversation bootstrap must require both the request and the respo
nse to be signed and encrypted.

Warning: A security policy was imported for the endpoint. The security policy co
ntains requirements that cannot be represented in a Windows Communication Founda
tion configuration. Look for a comment about the SecurityBindingElement paramete
rs that are required in the configuration file that was generated. Create the co
rrect binding element with code. The binding configuration that is in the config
uration file is not secure.

Warning: The following Policy Assertions were not Imported:
  XPath://wsdl:definitions[@targetNamespace='http://tempuri.org/']/wsdl:binding[
@name='WSFederationHttpBinding_IBlogoholicService']
  Assertions:
    <wspe:Utf816FFFECharacterEncoding xmlns:wspe='http://schemas.xmlsoap.org/ws/
2004/09/policy/encoding'>..</wspe:Utf816FFFECharacterEncoding>
    <wsap10:UsingAddressing xmlns:wsap10='http://www.w3.org/2005/08/addressing'>
..</wsap10:UsingAddressing>

2) On beta 2, I got the server certificate by extracting it from the results of the MetadataResolver:

ClientCredentials creds = new ClientCredentials();

X509CertificateEndpointIdentity cid = (X509CertificateEndpointIdentity)

serviceEndpoint.Address.Identity;

creds.ServiceCertificate.DefaultCertificate = cid.Certificates[0];

However, when I connect my June CTP client to my beta 2 server, the returned Identity is null.

 

 

Answer 1

Hey Nico.

I believe you're running into this problem because of inconsistencies between WinFX Beta2 and the NETFX3 JuneCTP. Have you tried updating your server to JuneCTP, rebulding your site and then re-generating your client proxy?

Answer 2

I expect that that would solve it, but I haven't done that because apparently the Vista June CTP will not be available to MSDN subscribers, and that would mean that I loose the ability to test my app on Windows Vista. I'll probably roll back to beta2 and stick with that version until there is a new CTP of Windows Vista on MSDN.

Answer 3

Why not just install the next CTP of NetFX3 on Vista Beta2?

Answer 4

Apparently that's not going to work:

This CTP (Community Tech Preview) is intended for users of Windows Vista build 5456, Windows XP, or Windows 2003 Server. It is not supported for users running the Windows Vista Beta 2 for .NET Framework 3.0 development. If you are using Windows Vista Beta 2 for .NET Framework 3.0 development, we recommend that you do not install this version of the CTP and instead use the Beta 2 release.

Answer 5

I tried this weekend to install the June CTP of WinFX on Beta 2 of Windows Vista and it doesnt't work. I'm unable to properly uninstall the Beta 2 version of WinFX.

Answer 6

Nico, are you getting any specific error message? I've successfully uninstalled .net 3.0 on Vista Beta 2 previously.

I'm pretty sure that there should be no good reason you can't uninstall it. I assume that you went to the control panel, and uninstalled it from there?

Garrett

Answer 7

It's not under 'Add or remove programs' like in Windows XP. Instead, I used Control Panel->Programs->Windows Features.  I removed the check mark next to 'Microsoft Foundation Components for WinFX 3.0' and clicked on OK. IIRC, that made de InfoCard control panel applet disappear, but the June CTP still complained that I should deinstall the previous version. I then also tried the CTP removal tool, but that also didn't work.

Answer 8

.NET Framework 3.0 is an integral part of Windows Vista. Vista uses parts of .NET FX 3.0 (specifically the Media Integration Layer) so it’s not possible to simply swap versions around. You can uninstall .NET Framework 3.0 from a Windows Vista machine (parts of the MIL will remain), but you can’t install a new version and if you decide to reinstall you should do it from Software Explorer rather than through a web-based download. AFAIK more recent builds of Vista will actually block installation rather than just fail.

-Nigel