Microsoft Enterprise Solutions Mega Trends

Microsoft enterprise solutions have found their way into businesses with sure steps with the best technology solutions for web applications, mobile applications, server side solutions and business intelligence. Both, Windows based and web based applications development practices are rolled out by implementing quick, accurate and cost effective business solutions. Microsoft technologies for the business intelligence, web, mobiles, tablets, and cross Platform Applications, using HTML 5, ASP.Net MVC and responsive design tools ensure faster Return on Investment (ROI), robustness and growth.

The Microsoft Platter

Microsoft offers different core technologies on one platter, be it for business and enterprise, windows and server or cloud technologies.

The Microsoft Platter

Microsoft enterprise solutions and business productivity solutions provide an amalgamation of Microsoft Dynamics CRM and business intelligence with Microsoft SQL Server and Power BI for Office 365. Microsoft social genre tools and solutions transform enterprises into a network spanning the employees, core data and the customers themselves with niche tools like Yammer, Office 365 and Lync. Various Microsoft CRMs can be integrated to connect meaningfully with the customer base. To support these innovative methods, hybrid cloud infrastructure solutions with Microsoft Azure, Windows Server, and Microsoft System Center are the choice of the times.

Microsoft enterprise solutions are designed to help business increase efficiency and collaboration, operate securely, and make better decisions. Concepts like data center, cloud, Windows Server 2008 R2, SharePoint, System Center, and SQL Server 2008 R2 ensure that the organizations increase productivity. The mega trends to be followed at Microsoft are social, mobile, analytics and cloud; integrating data, employees, customers and business intelligence into a single package.

Microsoft technologies enable rapid application development by following a simple and consistent programming model. The improvised scalability, robustness of solutions and a service oriented architecture ensure ease of deployment and maintainability. All the solutions support cross platform blends.

SPEC INDIA has 27 years of experience in Desktop Application Development, Web Application Development, Mobile Application Development and Enterprise Mobility Solutions implementation and deployment for clients spread across over 20+ countries using varied technologies. Integrating of modern day techniques of cloud computing, CRMs, server concepts and business intelligence into the apps and solutions developed, puts the solutions developed by SPEC into a completely new perspective.


Android – An Open Handset Alliance Project

Upgrading the SDK

This guide will help you migrate your development environment and applications to the Android 0.9 SDK beta. Use this guide if you’ve been developing for Android on any of the m3 or m5 versions of the SDK.

The Andoid 0.9 SDK beta includes:

  • Extensions, changes and improvements to the framework and library APIs
  • New developer tools
  • Enhancements to existing developer tools
  • Redesigns to the home screen, some applications and UI
  • Plus various other improvements throughout the system

To take advantage of these features, you need to install the new SDK and upgrade your existing Android applications. The sections below guide you through the process.

 Install the new SDK

Download the SDK and unpack it into a safe location.

After unpacking the new SDK, you should:

  • Wipe your emulator data.Some data formats have changed since the last SDK release, so any previously saved data in your emulator must be removed. Open a console/terminal and navigate to the /tools directory of your SDK. Launch the emulator with the -wipe-data option.

    Windows: emulator -wipe-data
    Mac/Linux: ./emulator -wipe-data

  • Update your PATH variable (Mac/Linux; optional).If you had previously setup your PATH variable to point to the SDK tools directory, then you’ll need to update it to point to the new SDK. E.g., for a .bashrcor .bash_profile file: export PATH=$PATH:<your_new_sdk_dir>/tools

Update your ADT Eclipse Plugin

If you develop on Eclipse and are using the ADT plugin, follow these steps to install the new plugin that accompanies the latest SDK.

Eclipse 3.3 (Europa) Eclipse 3.4 (Ganymede)
  1. Select Help > Software Updates > Find and Install….
  2. Select Search for updates of the currently installed features and click Finish.
  3. If any update for ADT is available, select and install.
  4. Restart Eclipse.
  1. Select Help > Software Updates…
  2. Select the Installed Software tab.
  3. Click Update…
  4. If an update for ADT is available, select it and click Finish.
  5. Restart Eclipse.

After restart, update your Eclipse preferences to point to the SDK directory:

  1. Select Window > Preferences… to open the Preferences panel. (Mac OSX: Eclipse > Preferences)
  2. Select Android from the left panel.
  3. For the SDK Location in the main panel, click Browse… and locate the SDK directory.
  4. Click Apply, then OK.

Set Up Application Signing

All applications must now be signed before you can install them on the emulator. Both the ADT plugin and the Ant-based build tools support this requirement by signing compiled .apk files with a debug key. To do so, the build tools use the Keytool utility included in the JDK to to create a keystore and a key with a known alias and password.

To support signing, you should first make sure that Keytool is available to the SDK build tools. In most cases, you can tell the SDK build tools how to find Keytool by making sure that your JAVA_HOME environment variable is set and that it references a suitable JDK. Alternatively, you can add the JDK version of Keytool to your PATH variable.

If you are developing on a version of Linux that originally came with Gnu Compiler for Java, make sure that the system is using the JDK version of Keytool, rather than the gcj version. If keytool is already in your PATH, it might be pointing to a symlink at /usr/bin/keytool. In this case, check the symlink target to make sure that it points to the keytool in the JDK.

If you use Ant to build your .apk files (rather than ADT for Eclipse), you must regenerate your build.xml file. To do that, follow these steps:

  1. In your Android application project directory, locate and delete the current build.xml file.
  2. Run activitycreator, directing output to the folder containing your application project.
    - exec activitycreator --out <project folder> your.activity.YourActivity

Run in this way, activityCreator will not erase or create new Java files (or manifest files), provided the activity and package already exists. It is important that the package and the activity are real. The tool creates a new build.xml file, as well as a new directory called “libs” in which to place 3rd jar files, which are now automatically handled by the Ant script.

Migrate your applications

After updating your SDK, you will likely encounter breakages in your code, due to framework and API changes. You’ll need to update your code to match changes in the Andriod APIs.

One way to start is to open your project in Eclipse and see where the ADT identifies errors in your application. From there, you can lookup respective changes in the Overview of Changes and API Diffs Report.

If you have modified one of the ApiDemos applications and would like to migrate it to the new SDK, note that you will need to uninstall the version of ApiDemos that comes preinstalled in the emulator.