If i bought a 10.1.1 deployment pack, will I be able to upgrade my code to 10.2 and deploy using my previous 10.1.1 license? Or do I have to buy a whole new 10.2 deployment pack?
If i bought a 10.1.1 deployment pack, will I be able to upgrade my code to 10.2 and deploy using my previous 10.1.1 license? Or do I have to buy a whole new 10.2 deployment pack?
Yes, as long as it's the same application you are re-compiling against the new version of the API you can keep using the same license code for your existing number of deployments. If it is a new application that you are creating and it is to be deployed alongside the existing application it would be considered a separate/new license.
Do the deployments still come in packs of 25?
Yes, Standard deployment licenses are available in packs of 25.
dear, sorry but im little bit confused, what is the defference between arcGIS runtime SDK for WPF, and for window store app? if i want to develop an enterprise applications that is running on windows 8 tablet what i have to use?
You're correct, if you would like to build an enterprise app which runs on Windows 8 tablets you do have two choices, you can either:
1. Build an app which runs in the traditional Windows Desktop environment (http://msdn.microsoft.com/en-US/windows/desktop/) This is the desktop environment with which we're all familiar and means you'll likely be using .NET 4.5 and Windows Presentation Foundation (WPF) - for which the 'ArcGIS Runtime SDK for WPF' is targeted.
2. Build an app which runs in the Windows Store app mode (http://msdn.microsoft.com/en-US/windows/apps/) This is a new app environment which arrived with Windows 8 and was initially termed "Metro" then subsequently the "Modern UI". It's referred to now as "Windows Store". These are the apps you launch from the start screen and which run full screen, provide a more content-centric and touch-centric user experience with many aspects of this "modern" UI design prescribed/recommended by Microsoft. The underlying Microsoft API is different from WPF - instead you develop against the ".NET for Windows Store apps". The important thing to note is that you can develop apps for this environment and still deploy in an enterprise scenario, this is called "sideloading" - for more information see http://technet.microsoft.com/en-us/windows/jj874388.aspx.
To cater for developers targeting the Microsoft platforms we are developing a new SDK called the "ArcGIS Runtime SDK for Microsoft .NET Framework", or informally, the ".NET SDK". This is the next evolution of the existing Esri developer products which target the Microsoft platforms. It will be one single SDK with three APIs based on a common design and implementation, thereby allowing you to easily build apps for the Windows Desktop, Windows Store apps, and for Windows Phone 8.
The new .NET SDK will be available in beta early in 2014, and is scheduled for release in summer 2014.
The answer to your question depends on when you would like to deploy your app - if it's before summer 2014, then you have one option: the ArcGIS Runtime SDK for WPF. If your schedule is summer 2014 or beyond, then my advice is to start working with the beta and choose either the Desktop environment or the Windows Store app environment, depending on what's appropriate for your requirements.
To clarify the products you mentioned in your question:
- ArcGIS Runtime SDK for WPF: This SDK allows you to build applications using .NET 4.0 and Windows Presentation Foundation (WPF) for the traditional Windows Desktop environment. We recently released version 10.2 of this SDK (late Oct / early Nov). During 2014 there will be further releases of this SDK, but we are focussing on the new .NET SDK (above) which includes an evolution of the existing WPF API.
- ArcGIS Runtime SDK for Windows Store apps: This is a Beta SDK released back in March 2013 to give you early access to a future SDK for building apps which target the Windows Store app environment. If you would like to build a Windows Store app, I would recommend waiting until the New Year when we will be releasing the beta of the new .NET SDK.
