468,545 Members | 1,897 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,545 developers. It's quick & easy.

Develop application with .Net + Unix



I have posted the question before but nobody have given me a solution. I
would like to rephrase my requirement and want to hear your advice.

We are developing application packages for logistics industry. The plan
is to develop two packages, one for daily operation in Client/Server
mode. The other is for reporting/enquiry in Browser/Server mode.

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.

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.

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.

Thanks.

Jonathan

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Jul 21 '05 #1
4 2277
In article <uk**************@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.
Jul 21 '05 #2
In article <uk**************@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.
Jul 21 '05 #3
On 2004-04-14, Jonathan Li <jo***********@hotmail.com> wrote:


I have posted the question before but nobody have given me a solution. I
would like to rephrase my requirement and want to hear your advice.

We are developing application packages for logistics industry. The plan
is to develop two packages, one for daily operation in Client/Server
mode. The other is for reporting/enquiry in Browser/Server mode.

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.

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.

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.

Thanks.

Jonathan


www.go-mono.com....

You might want to play with it a bit to see if it meets your
requirements. So far, they have a feature complete version of ASP.NET
running under apache via mod_mono and xsp. That would take care of your
server requirements.

Client's can use MS.NET if they are windows. If the clients apps must
be unix based as well, you can always write them using the GTK# packages
from mono.

Still, your probably going to find that .NET isn't going to work out for
you on this particular job :) Not that mono isn't nice - I've been
using it quite a bit on this Linux box over the last few months (but not
for asp).

--
Tom Shelton [MVP]
Powered By Gentoo Linux 1.4
"He dropped his voice still lower. In the stillness, a fly
would not have dared cleat its throat. "
Jul 21 '05 #4
On 2004-04-14, Jonathan Li <jo***********@hotmail.com> wrote:


I have posted the question before but nobody have given me a solution. I
would like to rephrase my requirement and want to hear your advice.

We are developing application packages for logistics industry. The plan
is to develop two packages, one for daily operation in Client/Server
mode. The other is for reporting/enquiry in Browser/Server mode.

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.

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.

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.

Thanks.

Jonathan


www.go-mono.com....

You might want to play with it a bit to see if it meets your
requirements. So far, they have a feature complete version of ASP.NET
running under apache via mod_mono and xsp. That would take care of your
server requirements.

Client's can use MS.NET if they are windows. If the clients apps must
be unix based as well, you can always write them using the GTK# packages
from mono.

Still, your probably going to find that .NET isn't going to work out for
you on this particular job :) Not that mono isn't nice - I've been
using it quite a bit on this Linux box over the last few months (but not
for asp).

--
Tom Shelton [MVP]
Powered By Gentoo Linux 1.4
"He dropped his voice still lower. In the stillness, a fly
would not have dared cleat its throat. "
Jul 21 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by aparnasinha26 | last post: by
4 posts views Thread by Jonathan Li | last post: by
15 posts views Thread by king kikapu | last post: by
reply views Thread by NPC403 | last post: by
1 post views Thread by UniDue | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.