[Mono-list] successful port of MS .net application to linux/apache/mono1.1.4

[Hubert FONGARNAND]

We've follow the same approach with porting ASP.NET application from MS.N=
ET to=20
Mono 1.16...
The application is a CRM (customer Relationship Management) application. =
It=20
use Webservices (to talk to an active directory server) and an oracle=20
Database.
The application used some 3rd party library too.
The Port is now succesfull !
I'm happy to see that i've experienced fast the same problem as you :

- The major problem was Oracle, i've contributed to the oracleclient asse=
mbly=20
in order to add correct datetime support and pooling
- trouble with multiple cookies too... But this problem only appear when =
I use=20
mod_mono, i've no problem with xsp... why? I've submitted a message in th=
e=20
mailing list two days ago, but it doesn't interest anybody...
- trouble with differences in executing path (order of including user=20
controls)...
- Some rendering problem with firefox (MS.NET doesn't render html exactly=
 the=20
same with an IE or a mozilla client)
- Problems with the French DateTime format (for mono 1/02/03 is the 3rd o=
f=20
february 2001)

- I'm doing some tests between a gentoo/mod_mono and a W2x3/.NET machine =
and=20
for instance, i can see any differences...
I can hope that our application will be put into production with mod_mono=
 may=20
be soon...

Long life to mono !!!
Hubert


Le Mardi 05 Avril 2005 11:33, simon a =E9crit=A0:
> Ive recently successfully ported an ASP.Net application from MS .net to=

> mono-1.1.4.
>
> This application was approximately 250-300 days development, is
> currently deployed and in production on windows server 2003, has 2
> external interfaces and used an MS SQL server database.
>
> As an experiment I ported it to mono and mysql in approximately 20
> hours, and had it running under apache on an ubuntu linux box.
>
> The application used a number of 3rd party libraries including
> nHibernate and wilson master pages.
>
> Some of the major problems encountered during the port were;
> - trouble with mulitple cookies and the FormsAuthentication cookie
> disappearing. - not sure what the problem was, made work around.
> - ALOT of trouble with differences in what I would call the current
> executing path of pages and the inclusion of user controls.  It appears=

> that IIS executes pages in a different path to apache/mod_mono and this=

> causes the page directives at the top of the aspx file to be incorrect.=

> Solution (really work around) - change ALL Server.Transfer calls to
> Response.Redirect (whether this is a better approach anyway is debatabl=
e)
> - problems with libraries compiled under MS .net framework not being
> compatable with those compiled under mono.  I am not sure what the
> expected compability between things compiled under mono and MS are but
> ive found that if you can get the source for something, try and compile=

> it under mono, it will cause you less trouble in the end.
>
> Apart from that the port was successful, and relatively painless.
>
> Unfortunately this forum is not the place for me to say what the
> application is (at this time).
>
> The next task is to find 2 identical boxes, deploy under both win2k3 an=
d
> linux/mono and load test both to see the results.  Only problem being i=

> dont have 2 identical boxes :(
>
> Simon
>
>
> _______________________________________________
> Mono-list maillist  -  Mono-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
_______________________________________________
Ce message et les =E9ventuels documents joints peuvent contenir des infor=
mations confidentielles.
Au cas o=F9 il ne vous serait pas destin=E9, nous vous remercions de bien=
 vouloir le supprimer et en aviser imm=E9diatement l'exp=E9diteur. Toute =
utilisation de ce message non conforme =E0 sa destination, toute diffusio=
n ou publication, totale ou partielle et quel qu'en soit le moyen est for=
mellement interdite.
Les communications sur internet n'=E9tant pas s=E9curis=E9es, l'int=E9gri=
t=E9 de ce message n'est pas assur=E9e et la soci=E9t=E9 =E9mettrice ne p=
eut =EAtre tenue pour responsable de son contenu.