After finding out that the caching API is severely divergent depending if you're targeting Windows Azure or Windows Server, I'm concerned that Microsoft isn't going to continue to develop AppFabric for Windows Server. Does anyone know if AppFabric for Windows Server is still being supported/developed?
It is currently being supported by Windows Server 2012:
http://blogs.msdn.com/b/workflowteam/archive/2012/10/25/appfabric-now-supported-on-windows-server-2012.aspx
Microsoft has released 4 cumulative updates for AppFabric (latest one being April 2013):
http://support.microsoft.com/kb/2800726
I think your answer is that it is being supported. However, I have not seen any publishings/blog posts about the technology unfortunately. All the development on distributed caching has been done on the Azure side, where they have 3 different caching API offerings (albeit one being deprecated and another in preview mode).
I personally have stopped using it, since the API causes problems with the Azure SDK/API and there are better options out there if you have a hybrid environment with Linux (i.e. Redis)
Edit (10/06/2014): Note Microsoft's guidance on using the AppFabric Cache for Azure..."We just announced support for the Azure Redis Cache, and we recommend new development use this cache." AND "If you recommend Redis, why do you have Managed Cache, an option that you do not recommend? To support customers who made investments into Velocity Cache, who have dependency on it in their apps, to give them as much time as they need to move to the Redis cache."
Link: https://azure.microsoft.com/en-us/pricing/details/cache/
Looks like Microsoft (at least for Azure) is recommending, developers start using the Redis Cache. May not apply for Windows Server Caching, but I with the slower release cadence of AppFabric...I would strongly look at other options.
I asked the team for you. Here's the answer today:
AppFabric will continue to be supported under Microsoft Support Lifecycle.
In March Microsoft shipped a CU5 for AF 1.1 and are actively working on a CU6.
The basic information is this:
If AppFabric is currently working for them, stick with AppFabric
For new development, evaluate Redis. This is Open Source and not MS-Supported.
We are working on a supported solution for Redis in the future.
// end
According to a MS blog post Microsoft is now ending support for AppFabric on the 2nd of April 2016 - see here: http://blogs.msdn.com/b/appfabric/archive/2015/04/02/windows-server-appfabric-1-1-ends-support-4-2-2016.aspx
Related
I have developed the extension for microsoft edge browser.Now i want to pack the extension so that i can publish it. But I have not found any information that how to pack the extension. Can anyone tell me how to pack it.?
Currently you can't.
For the Windows 10 Anniversary Update, we are intentionally starting with a small set of extensions. The list of extensions is locked - you can see the list at our extensions page here. We want to be mindful about what extensions are available on the platform and watch for telemetry and feedback and make sure the reliability, performance and functionality of the browser isn’t impacted by these new features. Extension developers can submit a request to https://aka.ms/extension-request to be considered for a future update.
https://developer.microsoft.com/en-us/microsoft-edge/platform/faq/
Newly released steps for packaging an Edge extension are available here: https://developer.microsoft.com/en-us/microsoft-edge/platform/documentation/extensions/guides/packaging/
As Elad mentions, however, submitting to the Windows Store is still a process managed by Microsoft. Submitting a request to https://aka.ms/extension-request will get you added to the list for future consideration.
I believe you can use Visual Studio 2015 Community to do it (free download from Microsoft). I've been trying the same thing, but I'm using Windows 7 and it keeps crashing, so I don't know if it's possible from my OS (or even if publishing an "app" is the same as publishing an "extension").
Packaging Apps for Windows 10
I could not google a straight simple answer to this, so i'm trying my luck here.
is there a problem installing Microsoft office 2007\2010\2013 on a network windows-based server, to be able to do some server-side conversions and simple automatic operations using its inter ops libraries on user generated documents?
If it is, is there anything i need to know prior to installing it ? any licenses needed ? cost of these ? is it the same as installing office on a client pc ?
Thanks in advance.
Microsoft Office supports Windows Server OS - feel free to install it on your server. But it doesn't support automation on the Server server side. The Considerations for server-side Automation of Office page states the following:
Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution.
Developers can use Automation in Microsoft Office to build custom solutions that use the capabilities and the features that are built into the Office product. Although such programmatic development can be implemented on a client system with relative ease, a number of complications can occur if Automation takes place from server-side code such as Microsoft Active Server Pages (ASP), ASP.NET, DCOM, or a Windows NT service.
I've been following the progress of VS 2013 as its progressed through its releases (Beta, RC, and now GA) and have had an overall positive feeling about the release. Today, I spent the day working entirely in the new version (GA Premium) to ensure that it provides all of the basic functionality needed by my team prior to adoption.
It works well for general dev tasks - given several of my favorite extensions haven't been ported yet - but while attempting to administer our Azure storage from within the IDE it appears to be removed from the previous release.
While in VS2012's Server Explorer, I'm able to link to Azure account to discover all of my top level objects - Cloud Services, Service Bus, Storage, and VMs. Now within VS2013 - following the same setup procedures from the previous version - I only see Mobile Services, SQL Databases, and Web Sites under the Windows Azure node of Server Explorer.
After a little googling I found little insight or even others asking the same thing (since GA) so I'm starting to wonder if it's just me or if this is the way it'll be from now on??? Can anyone confirm and/or provide evidence from Microsoft indicating that this is intentional?
Installing the Windows Azure SDK should give you all of the features you're looking for. You can find directions here: http://www.windowsazure.com/en-us/develop/visual-studio-2013/ for using the current version of the SDK with the VS 2013 GA release.
My question is this: How can I stop my .NET 1.1 application from trying to verify the digital signature in an environment where there is no access to the Internet?
Background to my question:
I have a product installed at a customer which is based on .NET 1.1 SP1. The customer site has no access to the Internet. This causes a delay in application startup which in some cases causes my Windows services to fail to start because they time out.
The delay when starting appears to be caused by the app attempting to verify the digital signature. This is well documented in other posts and the normal answer is to include generatePublisherEvidence=false in the app.config file, as documented here http://support.microsoft.com/kb/936707
It seems that using generatePublisherEvidence=false doesn't make any difference to .NET 1.1 apps, which seems to agree with MSDN (http://msdn.microsoft.com/en-us/library/0kk0kk35(VS.71).aspx does not mention the element) and with the hotfix I mentioned above, which was released for .NET 2.0 apps.
My next release to the customer will be built on .NET 3.5 SP1 and I have no problems with using generatePublisherEvidence on that version of the .NET framework, but I currently cannot simply change the customer to that release - I am stuck with .NET 1.1 SP1 - so I'm looking for an answer other than to simply use a later version of the .NET framework.
I just solved this for a vendor-supplied application today. I assume that their application was written in .net, but I did not confirm. Since the subnet did not have internet access, I removed the DNS server entry from the TCP/IP settings on the local computers that have static addresses. For addresses supplied by DHCP, I removed the DNS server option (006) from the DHCP scope.
I have some IIS 6.0 filters and extensions that I need to create a configuration panel for in IIS Manager. I need to create something similar to the ASP.NET tab, for instance.
I need to support versions of Windows Server 2003 prior to R2, and can't assume that they will have the MMC 3.0 update installed, so I guess I have to do it with unmanaged C++.
I've read up on MMC snap-ins, and I have a very basic idea of how they work, but I'm not sure about how to get one that is loaded as a tab in the IIS Manager. I'm thinking that maybe an "extension snap-in" is what I need, but I'm not positive.
So, I'm looking for any kind of documentation, literature, tutorials, examples, etc on how to do something like this. Any ideas?
There isn't much out there on how to do this....
Here's a link to the MMC 2.0 guides:
http://msdn.microsoft.com/en-us/library/aa815085(v=VS.85).aspx
Here's a link on extending IIS via snap-ins:
http://msdn.microsoft.com/en-us/library/aa814685(VS.85).aspx
About the only tutorial out there from what I could find but it is not specific to IIS....
http://msdn.microsoft.com/en-us/magazine/cc301779.aspx
This isn't the answer you're looking for, but it's the answer you need to hear:
MMC 2.0 is no longer supported by Microsoft.
MMC 3.0 is included with Windows Server 2003 Service Pack 2, which is the only remaining service pack release supported by Microsoft. Do you really have customers that refuse to upgrade to Server 2003 Service Pack 2? It came out 3.5 years ago and represents the best the Server 2003 platform has to offer in terms of security, performance, and software compatibility. It's also the only release that continues to receive security updates for IIS.
And if there are people out there that refuse to upgrade to 2003 SP2 due to specific compatibility concerns, do you really think they're going to jump at the opportunity to pay you and install your snap-in on their servers?
Probably not.
So save yourself a lot of grief, and position yourself well for the future -- do your development in MMC 3.0.
Unfortunately, there is no way to do what you are asking. You can create a snap-in/extension for MMC, but you will not be able to extend the IIS snap-in.