Home/ Questions/Q 174009
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T13:26:41+00:00

We have an enterprise application written in asp.net c# (3.5) and SQL server that

  • 0

We have an enterprise application written in asp.net c# (3.5) and SQL server that we want to bundle and release for customers.

However, several have expressed concerns that it requires a Microsoft server due to the costs. Yes, I know… Therefore, we are considering porting it to a LAMP stack, with the ‘P’ referring to php.

What challenges can we expect to face developing on a LAMP stack coming from a Visual Studio asp.net environment?

The issues I am sure of are:

  1. Debugging: Visual Studio is awesome for both client and server side debugging.
  2. Framework: The code behind model works great, and the MVC framework is nice.
  3. Maintenance: We would like the feature set to be common on both platforms.
  4. Database layer: Code is loosely coupled to the mssql data types.

If you’ve been through this exciting process, I’d love to know what it was like with some recommendations/tips.

As a side to this, is there any way for us to run this code as is? Mono? Others?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I have more experience with .NET than the *AMP stacks, but based on my experience with XAMPP, I would offer the following observations

    1. Debugging: Visual Studio is awesome for both client and server side debugging.

      Eclipse PDT works great for design, development, and debugging. I’ve heard good things about Zend Studio but haven’t worked with it.

    2. Framework: The code behind model works great, and the MVC framework is nice.

      There are frameworks to allow you to separate presentation from logic (e.g. Smarty ) and at least one MVC framework is available (e.g. CakePHP)

    3. Maintenance: We would like the feature set to be common on both platforms.

      If you exclude Windows specific functionality (Windows Integrated Security, etc) there shouldn’t be much you can’t do in both stacks, but if you have to reproduce controls like the gridview it will be labor intensive.

    4. Database layer: Code is loosely coupled to the mssql data types.

      I am not aware of any data types that cannot be mapped between mysql and sql server and there is good documentation for handling migrations

    Mono might decrease the amount of time required to port your solution, but I am unaware of any way you could re-use all of your code ‘as is’.

    • 0