Mobilize Blog

Application Modernization

Recent Posts

Posts by Topic

see all

Updating an ASP.NET Core 2.2 Web Site to .NET Core 3.1 LTS

Posted by Mauricio Rojas on Dec, 12, 2019 @ 07:12

Scott Hanselman is one of my geek heros. So when I so his excellent post I said to myself "it is useless to resist"!!

Read More

Topics: Visual Basic Upgrade Companion, VB6, convert Windows to Web, .NET, C#, Web Application Development, .NET Core, webapps, NETCORE3.1

Accessing local devices from a Web Application

Posted by Mauricio Rojas on Nov, 26, 2019 @ 10:11

Usually when we modernize legacy VB6, Delphi or PowerBuilder apps some parts of the migrated application depend on using a device which is attached to the client using the app.

Read More

Topics: application modernization, Visual Basic, VB6, convert Windows to Web, AngularJS, PowerBuilder, WebMAP, internet explorer, Helpers, migration services, desktop, devices

WebMAP app architecture part 2

Posted by John Browne on May, 12, 2016 @ 10:05

In the first part of this series, we spent some time discussing how complex web application coding can be. Web sites are simple; web apps are hard. 

Read More

Topics: convert Windows to Web, Web Application Development, WebMAP, ASP.NET/MVC


Posted by John Browne on Dec, 21, 2015 @ 15:12

Today's word of the day is brought to you by the letter "W". And that word is "webification."

No, don't bother calling up for this one, we just made it up. (Of course, I had to go try and suggested verification, vilification, vivification, and my favorite: vinification (pours glass of wine).

Having given birth to this neologism (clearly today is the day to throw $5 words around), we have high hopes for it. As we gaze fondly on it lying in its little crib, hoping we don't have to change its diaper any time soon, we foresee it attending all the best schools, excelling in sports, and achieving widespread renown and recognition.

But what exactly is this new creation, this spawn of ours? 

You know all those really really old desktop apps cluttering up your c: drive? The ones the IT department made long before you were hired? The ones with a user interface that makes you think of that sport coat Uncle Larry has worn for Thanksgiving dinner since you were four? The ones were you can almost smell your Grandfather's attic when they start up? 

Yeah, those apps.

Let's briefly look at three relevant points:

  1. Those Really Old Apps are written in Really Old Languages now understood only by Really Old Developers who, if they haven't already retired, are about to.
  2. Users are not just using Windows desktop and laptop computers to do real work anymore. They're also using Nexus phones, iPads, MacBooks. 
  3. Despite years of work improving sofware engineering practices (Agile, Scrum, TDD, etc), writing software from scratch is still a failure-prone, high-risk endeavor (yes, I know your code is always on time and on-budget, and your users never change the requirements on the fly, but other's do).

Some of those old apps will stick around forever, just as they are or perhaps wrapped in a thin layer of services that can be consumed by something else. 

Some of those old apps can be replaced by Excel, or Dynamics, or SAP, or Salesforce.

Some of those apps are so terrible but necessary they should be rewritten from scratch (see point 3 above and best of luck buddy).

But some of those old apps should be webified. 

Having successfully avoid actually defining our new word for the last dozen paragraphs or so, let's cut to the chase. Taking an existing app and getting a browser-based client so it's no longer captive to a Windows desktop is what I mean by webification. 

What kind of apps are we walking about?

First of all, they need to have real business value to the organization. If you are still running this app, it's because it does something useful for someone. It might have dozens, or thousands of users; it might represent some proprietary formula, algorithm, or process that provides competitive advantage; it might be the thing that gives the CEO a dashboard she's very very fond of. But it has value.

Second, the code isn't terrible. Yeah, I get that every piece of code, looked at later, is crap. But even mediocre code that has been running for years is probably pretty thoroughly debugged and reliable. And if it has business value, arguably that also means it has encoded algorithms and business logic that's important and functional. 

Third, the app needs modifications on a regular basis--either to implement new functionality supporting the users or to stay current with external changes (regulations for example). 

Webifying those kinds of apps--valuable, reasonable code quality, periodic updates required--should get you two payoffs: First, you should get a code base that's maintainable (remember those periodic updates?). If it's not now in a  reasonably modern language and platform, you'll continue to struggle to find gray-bearded developers who can work on it. It's not like recent graduates with CS degrees are fluent in COBOL or VB6. Second, you get something that is unshackled from the chains of the Windows desktop because it now runs inside a browser (and to be clear, it should be any browser, not one that supports some weird plugin--so we're talking about nice clean HTML with JavaScript). 

Once webified (webificated?), your users can use any ol' device they want to access the app, including the ubiquitous smart phones et al since it now runs on a browser. (Of course, if you have control-rich forms in the original Windows version, some thought will be needed to consider how to make them usable on a smaller form factor. We leave that exercise to the reader.)

How does this webification take place? My recommendation is to look into WebMAP, which can avoid the costs, perils, and time needed to do a rewrite while still meeting the goal of maintainable code at an affordable investment. 

Read More

Topics: convert Windows to Web

C# to HTML (or Windows vs the Web) Part 1

Posted by John Browne on Sep, 30, 2015 @ 12:09

If you’re used to developing for Windows (or MacOS or Linux or really any desktop OS) and you are contemplating a Web version of your application, there are a variety of things to consider. Moving from C# to HTML is more than just learning some different syntax and related frameworks. It's a whole new world.

Read More

Topics: convert Windows to Web, C#, Web Application Development, WebMAP2


Posted by DeeDee Walsh on May, 05, 2015 @ 08:05

Who's using WebMAP2 and what's the ROI?

The most common question we get at Mobilize.Net is "Can you show me a customer like me who's using it?" That's an easy question for us to answer since we have thousands of customers - from all industries including healthcare, financial services, manufacturing, and more. And the flexibility of WebMAP2 makes it valuable to large enterprises and ISVs as well as SMBs and mid-size companies.

Read More

Topics: manual rewrite, application modernization, application migration, HTML5, convert Windows to Web, Affordable Care Act, healthcare,, meaningful use

Migrating to HTML5 Part 2

Posted by John Browne on Feb, 03, 2015 @ 08:02

Ok, it's all very fine and dandy to talk about the case for automated migration from .NET to HTML5 as a way to reuse proven code, but what are the real economics here? Are we talking about a lot of savings, or just a tiny improvement?

Read More

Topics: manual rewrite, software development, application modernization, application migration, HTML5, Mobile Application Development, MVVM, MVC, convert Windows to Web

Adding it all up: the case for migrating to HTML5 (Part 1)

Posted by John Browne on Jan, 29, 2015 @ 16:01


Let's say you've got a line of business (LOB) application that just chugs along, doing its line of business thing, day after day, week after week, year after year. Every big company has at least one of these, often dozens and dozens. 

Read More

Topics: manual rewrite, software development, application modernization, application migration, HTML5, MVVM, MVC, convert Windows to Web