Common code base for windows and web

Question

0.00/5 (No votes)

See more:

Is there a robust and stable technology stack, cantered around Microsoft Technologies, where ideally I could have a single code base and two User interfaces - one for Desktop and the other for the Web.

What I have tried:

Have tried with Electron, but was not happy with the duplication required in UI design.

Posted 1-Mar-21 7:27am

Archimedes24

Updated 1-Mar-21 9:00am

Add a Solution

Comments

Maciej Los 1-Mar-21 15:03pm

What about Python?
WebFrameworks - Python Wiki[^]
Using Forms and Python — PyperCard 0.0.1-alpha.4 documentation[^]

2 solutions

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)

RickZeeland · Answer 1 · 2021-03-01T08:52:00

Solution 1

See: best-tools-for-building-cross-platform-desktop-apps-with-web-technologies[^]

And: cross-platform-tools-for-c-developers[^]

Posted 1-Mar-21 8:52am

RickZeeland

Comments

Archimedes24 30-Apr-21 3:02am

Thanks RickZeeland....will have a look

#realJSOP · Answer 2 · 2021-03-01T09:00:00

Your best bet is to shove as much code as possible into a common assembly, and then write code the two UI's around that. At some point though, you'll run into UI situations that call for the data to be used in a completely different way.

We have an assembly with all of our DAL, BLL, and connection string management (we don't put connection strings in config files 0- we build them on the fly based on the environment the app is running in), as well as common utility methods/classes. We have services, desktop apps (command line and UI), and web apps that consume this assembly.

Then we have a UI-specific assembly for WPF apps, and another for web apps, as well as middle-m,an assemblies that inherit certain classes in the first assembly I described.

BTW, all of our database code is in the form of stored procs in a SQL server database.

Changes become fairly localized and tend not to impact the opposing UI's.

That's the best we could do, but it's still kinda messy.