azure-appfabric

Via Google, I found another question on stackoverflow regarding the differences and similarities between Azure AppFabric and Windows Server AppFabric. It was mentioned that both versions of AppFabric come closer together or even melt together. This post is almost 2 years old and today in 2012, I still struggle with trying to unterstand the plan behind both AppFabric versions. From my point of view, I worked with the Azure AppFabric (Caching, Service Bus, ACS) and I am familiar with it. But when look at the product website of Server AppFabric, I'm confused. Am I wrong or is the Caching Service

I have a consistent, repeatable 120 second hang whenever the application calls this.cacheProvider.Add(new CacheItem(cacheKey, data, this.regionName), cachePolicy); at line 60 of the CachedDataSource.cs of the sample. . The .Add method is internal to Microsoft's DLL and I don't have code to it. Here are my parameters: cacheKey = "listofCompanies" data = // this is an EF 4.0 database first model class with 70 entries... result from IQueryable this.regionName = "companies" Reproducing the error: I have a database-first EF4.0 project that I recently upgraded to 4.1 by adding the "EntityFramework"

Writing a test application for my AppFabric-based library, I started getting a strange exception. The X.509 certificate CN=servicebus.appfabriclabs.com chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. The revocation function was unable to check revocation because the revocation server was offline. I've tried with next configuration with no success <behaviors> <endpointBehaviors> <behavior name="SecureMessageUserName"> <clientCredentials> <serviceCertificate> <authentication

If there are no longer any publishers or subscribers reading nor writing to a Queue, Topic, or Subscription, because of crashes or other abnormal terminations (instance restart, etc.), is that Queue/Topic/Subscription effectively orphaned? I tested this by creating a few Queues, and then terminating the applications. Those Queues were still on the Service Bus a long time later. It seems that they will just stay there forever. That would be wonderful if we WANTED that behavior, but in this case, we do not. How can we detect and delete these Queues, Topics, and Subscriptions? They will count

I am working on a POC with azure service fabric. Deployed my service in a local cluster and it's working fine with default settings in Local.xml. The moment I change the instance count it's throwing following exception. Where is the option to change the instance count? Basically i am trying to run my service on two nodes now. It's working fine when it is the default value that is 1. InnerException: HResult=-2146233088 Message=Error -4091 EADDRINUSE address already in use Source=Microsoft.AspNetCore.Server.Kestrel StatusCode=-4091 My local.xml is copied here <Parameters> <Parameter Name=

I have a application that can be broken down into multiple communicating services. My current implementation is monolithic and I want to reorganize it so that individual components can be deployed,iterated upon, scaled independently. I see two ways to do this with Azure: Service Fabric service composed of set of communicating micro-services (stateless, web-api etc.) A collection of individual Azure Web Apps/ Cloud Services that call each other at the http end points. Are there any obvious advantages of 1 over 2? Any rule of thumb to chose one over the other would also be very helpful. Peter

I'd like to make my application as flexible as possible, but not dig myself into a hole by making my Interface too specific. What is the best object type for a repository? IEnumerable, IQueryable, or List? The technologies I'm considering using are Azure App Fabric Caching Entity Framework 4.1 Possibly Windows Server AppFabric I would say build your DAL using IQueryable, and pass it around, make sure your object contects lifetime is the request. This way you will get benefit of delayed execution, but are exposed to the risk of inefficient querying of database. Then make sure you performance