As the heading states. Support DI frameworks in the programming model.160 votes
I noticed ASP.NET 5 applications takes a long time to deploy and debug. About 1-2 minutes on my computer on a brand new project. This should be better optimized to load faster199 votes
Totally agree. Waiting for a whole new deployment just to see some quick CSS changes is a huge pain. We’ve introduced a new deployment mode in Visual Studio that let’s you edit projects in place and see updates live as you make them, similar to what you’re used to with ASP.NET Core development outside of Service Fabric. Read more about it on the Service Fabric blog: https://blogs.msdn.microsoft.com/azureservicefabric/2017/04/17/speed-up-service-fabric-development-with-the-new-refresh-application-debug-mode-2/
Following the pattern of many other development resources from Microsoft, it would be amazing to see Service Fabric open sourced, so that others can modify, improve and view it.329 votes
Done! Come take a look at https://github.com/azure/service-fabric where you’ll find links to all Service Fabric open source repos. This is just a start..
This is now available in preview for Windows Server 2012 R2 and up.
Add windows 7 support! Because processors i7 are very good and a lot of PCs/Laptops are sold with Win7 Pro already, there are more then a few developers with Win 7 Pro on their dev machines and they are not going to have any real need for hardware/os upgrade any time soon. In our company we develop for Azure for three years now and continue to build upon the platform. It will be great loss of time if every developer has to switch OS now. I suggest that this will not be an isolated case and the problem will be multiplied. The suggestion to install VS 2015 on WS 2012/Win8 on a VM is a bad idea because it slows down development.
Add windows 7 support! Because processors i7 are very good and a lot of PCs/Laptops are sold with Win7 Pro already, there are more then a few developers with Win 7 Pro on their dev machines and they are not going to have any real need for hardware/os upgrade any time soon. In our company we develop for Azure for three years now and continue to build upon the platform. It will be great loss of time if every developer has to switch OS now. I suggest that this will not be an isolated case and the problem will be…125 votes
This is available as of SDK v1.5.175.
There are scenarios where I can be absolutely certain that a particular actor will never be used again. While I realize that they will be garbage collected from memory after a period of inactivity, I would actually like to remove them from the system altogether. It would be great to have a way to tell the platform which actors can be cleaned up.80 votes
The ability to delete actors is available as of SDK v1.5.175.
Those of us with existing investments in CloudServices (both Web & Worker Roles) need a clear migration path to Microservices. Especially early on in preview to prep our projects for this upgrade path.97 votes
The framework looks fantastic, and so documentation that reveals how to do everything properly for an example project that is moderately complex would be appreciated.
Documentation that explains how to integrate with legacy apps (to slowly migrate partial things to existing apps) as well would be really interesting.
Basically a few of these big tutorials I think would help explain how all the parts work and the best practices on using Fabric.
It's a huge undertaking I am sure, but that would be really good to see.155 votes
Allow Inheritance for IActor Interfaces. So I'm able to make for Example:
ITestableActor : IActor, which has a Reset Function.
ISpezificActor : ITestableActor
ISpezificActor actor = ActorProxy.Create<ISpezificActor>(...);
public void Cleanup(ITestableActor cleanActor)
Inheritance for actor interfaces and types was added in the public preview SDK.
We want to publish this to Azure! :)48 votes
Service Fabric is now in Public Preview. You can create clusters in the Azure portal, via PowerShell, or in Visual Studio.
- Don't see your idea?