<authenticationmode="Windows">

      </authentication>

      <authorization>

        <allowusers="*" />

        <denyusers="?" />

      </authorization>

      <anonymousIdentificationenabled="false" />

You will get the username etc and will be able to take actions you desire.

Hopefully might come in handy for someone who forgets!

The operating system that is installed can be one of the following:

• Windows Server 2008 R2 Enterprise (English only)
• Windows Server 2008 R2 Standard (English only)

Hyper-V cannot currently be enabled on the VM images to allow you to install operating systems like Windows 7 or something else.

Your scenario:

1. Upload Win2008R2 Image to Azure
2. Enable Hyper-V on uploaded Azure image

You will fail on step 2.

You will get something like this:

{"Could not load file or assembly 'TheAssemblyYouHaveReferenced' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)":"TheAssemblyYouHaveReferenced'}

And you meet the following criteria

• You are referencing a Delay Signed Dll in your project
• Your OS is Win7 x64 or Vista x64
• You have the messages mentioned above.

You can create a "MyDisableRegistryFile.reg" file with something like below:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\StrongName\Verification\*,58845dcd9090cc91]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\StrongName\Verification\*,58845dcd9090cc91]

Where 58845dcd9090cc91(Fictious Value :-)) is the PublicKeyToken. If you create this file you can run it on each deployment or machine as part of your install process.

It should be pointed out that disabling SN verification isnt very secure but you may have your own reasons.

Also beaware your dll thats causing the error may have referenced other dlls that may have the same problem, so you may have to do this multiple times.

Quick fix use C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\x64\sn.exe if on X64 and combine with  -Vr <dllpath> if you want to disable verification too(-Vr is case sensitive). This is basically because sn.exe is 32bit and always returns success even in failure.

If you dont have the SDK installed for SN then get it here: https://www.microsoft.com/en-us/download/details.aspx?id=8279

This blog has some more information too -> https://blogs.msdn.com/b/shitals/archive/2008/05/01/8446582.aspx

No matter what I could do I couldnt get the WCF service to load the aqppropriate client certificate using its thumprint. It always just couldnt find it. It turns out that its actually quite easy and that I was making one silly mistake that I didnt see anywhere else online. The certs thumbprint requires you to remove all the spaces.

WSHttpBinding sampleBinding= new WSHttpBinding();

sampleBinding.Security.Mode = SecurityMode.Transport;

sampleBinding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;

EndpointAddress ea = new EndpointAddress(" https://myerviceaddress.svc");

WsClient wsClient =  new WsClient(sampleBinding, ea);

wsClient.ClientCredentials.ClientCertificate.SetCertificate(StoreLocation.LocalMachine,StoreName.My, X509FindType.FindByThumbprint, "6827A9E09EEE24C6290C808ACEDD000FFC825345");

If you want the certs properties so that you can just get them as it expects you could also just load them like below and print to intermediate window or look them up through the locals and copy the values in..

X509Certificate2 actualCert = new X509Certificate2(@"C:\Certpath\cert.pfx", "password");

The certmanager does this but I find this easier when your programming it exactly as it should expect

First Setup IIS  correctly:

1:Create a new AppPool in IIS  and give it an identity with suitable privileges -  Ill call it “NewAppPool”

2: In IIS add a new application “Example”

3. Edit the Basic Settings so your new app uses the “NewAppPool”

4. In Authentication –

·        Disable Anonymous access

·        Enable Windows Access

This example assumes you have an ASPX site hosting your SilverlightApplication and the ASPX Site also exposes a WCF service that you are using to get\send some data which requires some form of user authentication

In your WCF Config make sure you have your authentication scheme set to Negotiate. Windows or NTLM will not work when deployed on IIS. NTLM will only work on your ASP.NET Development server when you press F5.

      <customBinding>

        <binding name="MyApsxWebSite.MyService.customBinding0">

          <binaryMessageEncoding  />

          <httpTransport authenticationScheme="Negotiate"  />

        </binding>

      </customBinding>

Now Configure your WCF service\Silverlight to work on IIS.

Wcf First and then ASPX binding’s:

In your binding in the web.config, comment out the IMetaDataExchange. This causes the infamous error “Security settings for this service require ‘Anonymous authentication but it is not enabled for the IIS application ….. ”. This endpoint forces your service to use Anonymous bindings, so remove it or change it..

<services>

<service name="MyApsxWebSite.MyService">

<endpoint address="" binding="customBinding" bindingConfiguration="MyApsxWebSite.MyService.customBinding0"

          contract="MyApsxWebSite.MyService" />

        <!--<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />-->

</service>

The system.web should be like below– Select Windows:

  <system.web>

    <compilation debug="true" targetFramework="4.0" />

    <authentication mode="Windows">

    </authentication>

  </system.web>

·        Now build\save and publish to your IIS location. I have intentionally not mentioned SL app yet.

·        Once published and setup correctly in ISS Open your SL app in Visual Studio.

·        If you had an existing service reference to this service delete it.

·        Now add a new Service Reference and point it at https://MyMachineName/Myservice.svc

·        Compile\Build the SL App

·        Locate it in the ClientBin folder of your ASPX build location

·        Copy it to your published ClientBin folder where IIS accesses it and replace the one that is there with this one.

·        Run your service and you should be able to access user credentials by passing them to the SL app via InitParms(Not secure) in your aspx page hosting the SL app.

   <param name="initparams" value="UserAccount=<%=HttpContext.Current.User.Identity.Name%>" />

In SL retrieve them by

       private void Application_Startup(object sender, StartupEventArgs e)

        {

           string UserID = e.InitParams["UserAccount"];

 }

Or in WCF use the HttpContext to do as you require and limit windows access.

You should have your SL app running and retrieving the user credentials you require.

Really hope this helps!

Thanks

Keith

This problem manifests for me in the following situation.

• Silverlight App hosted in a ASPX site
• The Silverlight app is a data-consumer and requires data via a WCF service also hosted in the ASPX Page

Everything works fantastic when you run it via F5 in VS. Once published to IIS it stops communicating with WCF.

Two problems cause this:

1. The Silverlight app is defaulting to the https://localhost:25775/servicename.svc
   1. Get rid of the port number as it thinks your trying to communicate across domain https://localhost/servicename.svc
   2. Note this wont work via VS when you change it
2. If you have that fixed but the silverlight app reverts to being unable to communicate with the WCF service again when called remotely you need to do the following(works for me anyway):
   1. Publish the Website with all pieces, SIlverlight, WCF etc to your IIS publish location
   2. Go back tot he Silverlight App and open your web reference to the service in VS
   3. Change it to point at the newly deployed web service location
   4. Change LocalHost to your server name or what ever your setup is. ie https://MyServer/servicename.svc
   5. Press OK in the configure service and build the silverlight app
   6. Copy the newly compiled .xap file from the clientbin folder
   7. Overwrite the deployed .xap file in the location where you published your service
   8. Open up the silverlight app\Website  from the published location

This should now communicate fine under the https://MyServer/servicename.svc but will not under https://localhost/servicename.svc as it will look for the servername and not localhost

 Ideally it really should figure this out for itself in a perfect world ;-)

Really hope this helps!

The Actual errors

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Timestamp: Mon, 29 Nov 2010 21:43:41 UTC

Message: Unhandled Error in Silverlight Application An exception occurred during the operation, making the result invalid.  Check InnerException for exception details.   at System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
   at MyService.GetMyJobsCompletedEventArgs.get_Result()
   at MyService.MainPage.t_GetMyJobsCompleted(Object sender, GetMyJobsCompletedEventArgs e)
   at  MyService.MyClient.OnGetMyJobsCompleted(Object state)

An exception occurred during the operation, making the result invalid.  Check InnerException for exception details.

[ExceptionOccurred]
Arguments:
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See https://go.microsoft.com/fwlink/?linkid=106663&Version=4.0.50917.0&File=System.dll&Key=Async_ExceptionOccurred

This is only relevant if your service installs perfect but you can find it – Where is it? It should be identifiable in the services.msc but its not there??

InstallUtil doesn’t complain during install so whats the problem.. ??

Simple & obvious when you know why – in VS2010 when you add your serviceInstaller and your serviceProcessInstaller the parent property doesn’t get set automatically like in previous versions of VS.

To Fix:

Goto your ServiceInstaller and set the Parent property from none to your ProjectInstaller

OR IN THE CASE WHERE YOU HAVE RENAMED THE PROJECTINSTALLER CHANGE THE SETTIGN THERE!

Should work like a gem ;-)

Keith

If you  see this error you havent installed the prerequistes for ASP.NET 4.

Try this

1. Open Visual Studio Command Prompt
2. Type the following: 
   1. aspnet_regiis.exe -i
3. Run the command
4. Try your service again...
   
5. Happy Face - it should be working :-)
   

This basically installs the necessary ASP pieces to get your service up and working!

Enjoy..

Keith

This is due to the fact that by default IIS7 runs as ‘IIS APPPOOL\\DefaultAppPool’  and doesn’t have enough permission. Change to Network service and it should be fine!

Quite simple to do it, just in case your more used to IIS6 :-)

1.     Start->Run-> Type 'inetmgr'

2.     Expand the server name on the left connections panel and you will see Application Pools

3.     Click ‘DefaultAppPool’

4.     Click ‘Advanced Settings’

5.     Goto ‘Process Model’ Section

6.     Select 'Identity'  = 'Network Service'

Hope that helps!

Keith

Are you self hosting a WCF library service inside a console or windows forms application? Then the most likely cause of this problem is that you have the library project contained within your same solution.

The problem happens because the WCF Service Host running at the same time as your custom host application. You run or debug your app and when your host initialises the WCF stack, you will see an AddressAlreadyInUseException as in the above pic.  This is happening because the WCF Service Host in Visual studio is already listening on the same address...

Basically remove the wcf lib from the solution and reference it. When you run the host you should now be able to open it.

ServiceHost host = new ServiceHost(typeof(ClientHost));

Host.Open();

Now there should be no errorJ!

Rick Rainey's  suggested a fix to the config file which doesn’t work for me, but may for somebody else which prevents removing it from the project. https://blogs.msdn.com/rickrain/archive/2008/02/14/Preventing-the-WCF-Service-Host-from-launching-in-Visual-Studio-2008.aspx

I have not seen if this bug exists in 2010 yet.. I will update when I check it..