Take a look at our Appistry Enterprise Application Fabric (EAF) product. We have an EAF Community Edition license that is free, and good for five servers and/or ten cores. You can use the license for production or whatevever and it is perpetual (no end date). It's supported through our Peer2Peer developer network.
EAF takes a distributed network of N servers or virtual machines and makes them act as a single cloud resource for your Plain Old .NET objects and code. You package your .NET objects, and then deploy your .NET objects to the fabric with a single call. The fabric automatically provisions the code to all the servers, and makes it available to run. Your application and objects are versioned, so if you deploy an update, the fabric makes sure automatically that all servers are running the latest version. The theme here is that you don't administer individual boxes.
Your code running on the fabric's cloud environment runs as persistent services (as you desire), and not as transient things. The services are monitored and managed by the fabric's self-healing and self-organizing infrastructure. However, you do not write code to make this happen. It comes from the environment itself. Again, your code are just PONOs.
Clients call on your objects/services in the fabric through either .NET remoting or using our APIs. The code you deploy on the fabric does not have to use any special APIs, nor does it "know" its running in a distributed manner. Your code just automatically gets load balancing, scaling, and reliability with no single points of failure. The fabric is self-organizing and self-healing and works around hardware and other failures. Your code is free to utilize external resources like databases, but the fabric does not require a database.
Cool stuff to have built! :-) EAF is in production at many customers, and our latest release has a lot of new .NET enhancements. The Peer2Peer community is active and helpful, and again, the community edition license is free and does not expire.
So, specifically addressing what seems to be your requirements:
1. Automated deployment, versioning, and provisioning of .NET assemblies on a cloud? Yes
2. .NET objects becoming persistent services distributed across a cloud? Yes