Geek Answers Handbook

How to create a SaaS application for existing software in asp.net c # mvc

I want to offer a software product using the SaaS model. This, of course, will require me to create a website on which clients can register, register, manage their membership and billing options.

Now suppose I have software like a calculator (just an example), which is basically an asp.net WPF application. Now I want to offer this software (application) as a service for my clients.

So, now up to this point I have:

  • A website having the above functionality (developed by Asp.Net MVC-5).
  • The software I want to offer as SaaS (development in asp.net WPF, desktop application)

Now I want to know how I will integrate these two things to create a good SaaS service with several tenants? How to publish this? What platform should I use to publish this window to Azure, Amazon, etc.?

or

What I think is impossible, do I need to develop software (which I want to offer as SaaS) using web technologies? Is that the case?

I am studying multi-user work, so please let me know if I am completely mistaken and direct me on the right path. Thanks!

+6
source share
3 answers

WPF is a desktop client application technology. It is not intended to be distributed as a service. You will have to rewrite the application so that it is a web application (ASP.NET or another platform if you do not want to use .NET).

Then you will have to make it multi-user, so that each client can run it in isolation, without interfering with other client data, and you get into the SaaS business. If your application depends on the database, you will have to decide how to make this isolation: whether you add it at the database level or in the database schema.

Obviously, you will need to choose a hosting for your service. Windows Azure, Amazon, Rackspace, ... are a popular choice, to name a few. Depending on your specific needs, you can choose one or the other.

+5
source

You cannot offer a WPF application as a SaaS unless you offer it in a user virtual machine, which will be a “really” expensive solution. Since this is a WPF application, your classes will easily convert MVC5 solutions.

I highly recommend you switch to Windows Azure since you are a .NET developer, and they offer really great products that you'll need on the go.

  • MVC with EF
  • Windows azure
  • Paypal || Refund (for accepting CC payments)
  • Twilio (if you need to send SMS to your client)
0
source

I agree with darin-dimitrov and cilerler where a WPF application (not a web application) cannot be directly converted as a SAAS application.

SAAS, it should be ONLINE, without compromising the availability of 99.99%, with a faster response to the notification BILL, ENROLLMENT, i.e. subscription, change of PLAN, notification of the choice of payroll agents, as well as the choice of communication channels for tenants and users under tenants, too.

If you do not want to create software at all that should be able to convert your Onpremise application to SAAS, it should adhere to the above functions.

And when you choose the platform to start your SAAS business, your application should be flexible enough for SIT on any platform that will handle Windows AZURE, AMAZON or RackSpace. At least to avoid the disaster that happened in history.

Your application should be simple, stable, flexible to withstand weekly updates or versions.

0
source

More articles:


All Articles