Home/ Questions/Q 4555028
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T17:10:04+00:00

we have a rich client application written in WPF/WCF and are intending to create

  • 0

we have a rich client application written in WPF/WCF and are intending to create a companion website in ASP.net (using MVC if possible).

I’ve been asked to figure out how much of our current codebase, we can reuse (by a separate team) – and I have little to no experience with ASP.net.

We will reuse our domain model, but is there any point in separating out the WPF-specific parts of our ViewModels and reuse the WPF-agnostic parts in MVC? Does it even follow the same paradigms? We use RelayCommands exclusively for commanding, so it would be easy to wrap the contained methods in something ASP.net specific… But how about UI-specific things – e.g. does ASP.net use INotifyPropertyChanged – or how does it handle UI-updates?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    For me it wouldn’t make any sense. Your models should contain all of your important business logic code and should be the point of greatest reuseability. Your view models should contain presentation logic only, and as this is so different for a desktop and web app, it doesn’t make sense to reuse these.

    MVC does not use any binding mechanism for UI updates, as web apps are stateless by nature. You will actually most likely end up using view models for your MVC app, but in MVC these act as simple data transfer objects (DTOs) for providing data to the views for rendering for each HTTP request. Once the view is rendered, you would need to go back to the server to update the view model and rerender the view.

    Alternatively, you can of course update the UI client side with scripting. Knockout.js is a nice JS library for client side view model/view binding.

    • 0