Comments for AppFabric Team Bloghttps://blogs.msdn.microsoft.com/appfabric
AppFabric Team Blog covering Windows Azure AppFabric, Windows Server AppFabric, WCF and WF, development, deployment, and managementTue, 13 Oct 2015 05:44:05 +0000hourly1Comment on Microsoft AppFabric 1.1 for Windows Server Support Lifecycle Extension – 4/11/2017 by Jimmy Zimmermanhttps://blogs.msdn.microsoft.com/appfabric/2015/06/19/microsoft-appfabric-1-1-for-windows-server-support-lifecycle-extension-4112017/#comment-1112
Tue, 13 Oct 2015 05:44:05 +0000https://blogs.msdn.microsoft.com/appfabric/2015/06/19/microsoft-appfabric-1-1-for-windows-server-support-lifecycle-extension-4112017/#comment-1112Yet more directionless flailing from MS. Really guys this is just getting ridiculous. I get that not every product and system gets to live forever under the corporate umbrella but when the advice is, "build your own custom solution" shows an utter lack of preplaning. A managed move of the system into an open community model would far better support your customers as well as drive .Net/Windows Server platform adoption.
]]>Comment on Microsoft AppFabric 1.1 for Windows Server Ends Support 4/2/2016 by Keith Doylehttps://blogs.msdn.microsoft.com/appfabric/2015/04/02/microsoft-appfabric-1-1-for-windows-server-ends-support-422016/#comment-1122
Wed, 02 Sep 2015 10:48:13 +0000https://blogs.msdn.microsoft.com/appfabric/2015/04/02/microsoft-appfabric-1-1-for-windows-server-ends-support-422016/#comment-1122It's just this sort of thing which sours me on considering adopting new Microsoft technologies. We've used the Always On feature of App Fabric to essentially, create Windows services that are always running (or potentially are) and have a web interface, without actually making it a windows service. Is that what is referred to as "hosting" here? That's not at all clear. We previously had done our own web listener process within a Windows service, rolling our own URL parsing, listening and connection thread handling. It's looking like we should go back to that in the future. When the press release here refers to "manually host", I have no idea what they are referring to there. Sounds to me that means going back to our own home-grown web server logic like we did before…
]]>Comment on Microsoft AppFabric 1.1 for Windows Server Support Lifecycle Extension – 4/11/2017 by Jonas Samuelssonhttps://blogs.msdn.microsoft.com/appfabric/2015/06/19/microsoft-appfabric-1-1-for-windows-server-support-lifecycle-extension-4112017/#comment-1132
Fri, 21 Aug 2015 04:22:44 +0000https://blogs.msdn.microsoft.com/appfabric/2015/06/19/microsoft-appfabric-1-1-for-windows-server-support-lifecycle-extension-4112017/#comment-1132Hi,

thanks for the clarification and extension! This gives us more time to migrate away from the technology. It also gives us possibility to share the information and flag to management that an investment is necessary during 2016.

The hosting and monitoring part that we use is only stating that a custom solution can be built. Will the source code be opened so that the community can further these type of solutions ?

"The monitoring feature in Microsoft AppFabric for Windows Server gives users an administrative UI built into the IIS Manager to configure, control and monitor applications. For applications utilizing the management and monitoring functionality of AppFabric, custom solutions can be built which will produce the same results. These custom solutions can best monitor the information from a specific application or service."

is ridiculous. You (MS) are open sourcing more and more code and surprisingly what we get here is 'go and f*!! yourself' Hust open source on github montioring and managing part of AppFabric for WF and WCF and the Community will do the rest, I can assure you. Do not be like MS 5 years ago. Listen to your mates in the CLR or Visual Studo Team.

]]>Comment on Microsoft AppFabric 1.1 for Windows Server Support Lifecycle Extension – 4/11/2017 by WF Developerhttps://blogs.msdn.microsoft.com/appfabric/2015/06/19/microsoft-appfabric-1-1-for-windows-server-support-lifecycle-extension-4112017/#comment-1162
Mon, 27 Jul 2015 06:36:21 +0000https://blogs.msdn.microsoft.com/appfabric/2015/06/19/microsoft-appfabric-1-1-for-windows-server-support-lifecycle-extension-4112017/#comment-1162Why doesn't MSFT Open Source the Hosting and Mgmt/Monitoring of Services and Workflows pieces of AppFabric? There are a good amount of solutions that rely on that and if people are going to use WF going forward, this would be beneficial to the community

On the flip side, if there is an Azure alternative I'm sure folks would be more than happy to transition.

]]>Comment on Microsoft AppFabric 1.1 for Windows Server Ends Support 4/2/2016 by Erica Mohler - MSFT1https://blogs.msdn.microsoft.com/appfabric/2015/04/02/microsoft-appfabric-1-1-for-windows-server-ends-support-422016/#comment-1101
Fri, 19 Jun 2015 16:53:03 +0000https://blogs.msdn.microsoft.com/appfabric/2015/04/02/microsoft-appfabric-1-1-for-windows-server-ends-support-422016/#comment-1101AppFabric 1.1 for Windows Server Support Lifecycle has been updated to 4/11/2017, please see this blog post for more information:

]]>Comment on Microsoft AppFabric 1.1 for Windows Server Ends Support 4/2/2016 by Chris Villingerhttps://blogs.msdn.microsoft.com/appfabric/2015/04/02/microsoft-appfabric-1-1-for-windows-server-ends-support-422016/#comment-1091
Wed, 27 May 2015 16:53:02 +0000https://blogs.msdn.microsoft.com/appfabric/2015/04/02/microsoft-appfabric-1-1-for-windows-server-ends-support-422016/#comment-1091We would also like to invite you to a Tweet Chat we are hosting on this topic on Thursday May 28 @ 9AM PDT (12PM EDT). RSVP: http://bit.ly/1Ba9jha #ScaleOutChat
]]>Comment on Microsoft AppFabric 1.1 for Windows Server Ends Support 4/2/2016 by Chris Villingerhttps://blogs.msdn.microsoft.com/appfabric/2015/04/02/microsoft-appfabric-1-1-for-windows-server-ends-support-422016/#comment-933
Wed, 27 May 2015 12:35:46 +0000https://blogs.msdn.microsoft.com/appfabric/2015/04/02/microsoft-appfabric-1-1-for-windows-server-ends-support-422016/#comment-933Full disclosure: I work for ScaleOut Software.

As a certified Microsoft Solution Provider, we’d like to offer some additional assistance to the community. For those of you looking for a commercially supported, on-premise or cloud alternative to Windows Server AppFabric (WSAF) Cache and Microsoft Azure Redis Cache, we would like to offer a migration option to ScaleOut StateServer [1] or ScaleOut SessionServer [2]. We put together a simple migration guide and architectural comparison [3] to help folks struggling with the AppFabric end-of-life. This will allow customers to continue using their application caching setup in both cloud and on-premise situations.

For those who don’t want to have to completely rewrite their application code from the ground up, we also created a WSAF Caching Compatibility Library [4][5] for applications that make use of the Azure-compliant subset of Windows Server AppFabric (WSAF) Caching APIs. We use the same class definitions, so you only need to change the references and recompile. Give it a try to see if it works for your application. Do note however, this is a bare-minimum approach and does not expose all the additional functionality that the platform provides; for example, there is a cool object browser you can use to easily visualize your object store for validation.

]]>Comment on Microsoft AppFabric 1.1 for Windows Server Ends Support 4/2/2016 by csrowellhttps://blogs.msdn.microsoft.com/appfabric/2015/04/02/microsoft-appfabric-1-1-for-windows-server-ends-support-422016/#comment-923
Fri, 22 May 2015 08:14:12 +0000https://blogs.msdn.microsoft.com/appfabric/2015/04/02/microsoft-appfabric-1-1-for-windows-server-ends-support-422016/#comment-923And what does this mean for Service Bus for Windows Server (On-Premise Service Bus) which uses it??
]]>