How to convert VB.NET windows form application to a browser based web application

Question

0.00/5 (No votes)

See more:

, +

I built a real-time ERP software for a client that has been running since the last 3 years.

The front end of the project is a Windows Forms desktop application built in VB.NET (in Visual Studio 2017). And the back-end is in MS SQL Server 2016.

The project has around a hundred reports developed in SAP Crystal Reports and the output dataset of each report comes from a stored procedure created in the back-end SQL Server database.

Now I want to convert this project into a web application that will run in a web browser. While the database will remain the same, no change is required in database.

I know that a Windows Forms desktop application cannot be converted directly to a browser-based web application, I will have to do a new development and coding.
But there will be no change in algorithm and business logic as this project meets the client's requirement 100%, so the only thing is to convert the project to a browser-based web application from a Windows Form desktop application. All the modules, features and functions will remain the same with appropriate interface changes and enhancements.

And I also want all the reports in the new web application to be designed in the same way as they are in the old desktop application because the client runs all their business on the basis of these reports.

Now what would be the best platform for me to convert (redevelop) the front-end interface of my Windows Form desktop application into a web application including all reports without making any changes to the database.

What I have tried:

I did not try for my required conversion.

Posted 28-Sep-23 23:41pm

Solution Hall

Updated 2-Oct-23 2:41am

Deeksha Shenoy

v3

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2023-09-29T00:38:00

It really depends now how you wrote the original application - if it's organised as separate modules: Presentation Layer, Business Layer, and Data Layer as separate Assemblies for example then it should be pretty simple to just respecify the PL and recode for the Client browser instead of Winforms.

If it isn't, and all the code is mixed together in one assembly then it's probably going to be a PITA to separate out the BL and DL stuff as it's likely to be very dependant on the PL controls and often is coded into the control event handlers directly.

In the later case, I'd start with a conversion of the existing app into a modular form still running as a WinForms application (so it's easy to both test and "parallelize" the eventual Web and Windows applications with regard to changes mods and bug fixes.

When that's sorted, you are in a good position to add a second PL for your web version to the new specification.

The alternative is to just spec up and write a new app from scratch, with "glances" at the original code as needed to sort out the algorithms and data use. But that would be a pretty major job for any significant sized existing app.

But ... you know your code, and we have no access - so it's going to be your decision.