News

'Acropolis' Project Speeds Smart Client Dev

Microsoft's 'Acropolis' aims to speed up smart client development.

The software industry has for decades dreamed of an application development platform that would allow programmers to quickly assemble software by snapping together blocks of stock code like Legos.

The goals of the Microsoft Windows client development platform project, code-named "Acropolis," may not be quite that ambitious, but it does aim to speed up and simplify the process through a set of templates and pre-written code modules for building .NET apps. Once dev shops have coded custom modules for one line-of-business app, the theory goes, those modules could then be easily plugged into other apps.

Building Blocks
Acropolis builds upon Microsoft's Smart Client Software Factory/Composite UI Block (SCSF/CAB) project and will bring full support for Windows Presentation Foundation (WPF) to the modular dev platform for the first time, the company says.

"Our goal is to allow you to focus your coding efforts on your business logic or business problem and not have to code up your applications plumbing," Microsoft Solution Architect David Hill writes on his blog.

Developer Billy Hollis, a Microsoft MVP and .NET consultant, says the unfamiliar organizing principles of module-based development platforms such as CAB and Acropolis can be tough for traditional programmers to master, but the investment in time makes sense for enterprise dev shops building large internal apps such as call center software. He characterizes Acropolis as a kind of portal through which developers can organize blocks of code into an application.

"It handles the security aspect and organizes the user navigation and makes sure the application has a graceful shut down," Hollis says.

The first community technology preview (CTP) of Acropolis was released last month to start generating feedback, but the project team warns developers not to expect too much in the way of stock code blocks from this fledgling version. Most of the first year of work was spent building the underlying framework. Microsoft plans to release additional CTPs over the summer in the hopes of approaching a beta release by the end of the year.

Smart Clients Live On
While some would question the wisdom of laboring over a new platform for developing thick-client apps at a time when such apps appear in danger of being dislodged by the growth of rich Internet applications (RIAs), Microsoft says Acropolis is designed for the development of utility enterprise apps with no need of RIA flash-such as sales automation, customer care and inventory management programs.

Hollis agrees: "There's definitely still a place in the industry for smart clients, and therefore," he says, "there's a place for something to help organize them."
comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube