Re: Develop application with .Net + Unix
From: Sergei Gnezdov (nouser_at_blackhole.net)
Date: 04/14/04
- Next message: Rob Oldfield: "Re: Fed up of Microsoft with its .NET 2.0 Teasers!"
- Previous message: Bill Young via .NET 247: "File.Move UNC"
- In reply to: Jonathan Li: "Develop application with .Net + Unix"
- Messages sorted by: [ date ] [ thread ]
Date: 14 Apr 2004 23:42:27 GMT
In article <uk#JbScIEHA.2592@tk2msftngp13.phx.gbl>, Jonathan Li wrote:
>
> 1. The server must be Unix
> When I say 'server' means 1) database server; 2) if possible also the
> application server.
>
> One asked why Unix instead of Windows. It is written in the bidding
> document to use Unix.
>
> If I can use Windows as the server, there is no question at all. So
> please no need to discuss on this point.
You don't want to bet your product on a product which is not officially supported,
don't you? From what I know .NET is not officially supported on *UNIX*.
So, face your requirements and go for something which is guaranteed to work.
> 2. I want to make use of the Windows/.Net powers on client side.
> The application on client has two packages, one is in C/S mode. The
> other is B/S mode. So, I would like to use C#.Net or VB.Net to develop
> the C/S package and ASP.Net to develop B/S package.
What are C/S and B/S modes? Clint mode, business mode?
If you are talking about normal GUIs (rich client), then there are other good approaces:
- Dolphin Smalltalk has exellent GUI.
- Java GUI is known to be slow and have non-native look and feel.
It is no longer true. Take a look at Eclipse SWT approach. SWT is from IBM...
SWT provides native widget support in Java apps.SWT application will not look any differnt
from .NET or native win32 app. GUI in Java with SWT is smaller and faster then Swing.
- Delphi is a good alternative.
> 3. Because the C/S package is operating on the same data set as of the
> B/S package, there are a lot functions (or components) in common for
> these two packages. Actually, I want the two packages share the
> components as much as possible.
> Under J2EE, we can have EJBs to have that. Under .Net, what should I do
> because ASP.Net cannot work under Unix.
I think you answered yourself: .NET does not fit.
J2EE is more appropriate.
- Next message: Rob Oldfield: "Re: Fed up of Microsoft with its .NET 2.0 Teasers!"
- Previous message: Bill Young via .NET 247: "File.Move UNC"
- In reply to: Jonathan Li: "Develop application with .Net + Unix"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
