Re: Can we use Unix as the server?
From: Angel Saenz-Badillos[MS] (angelsa_at_online.microsoft.com)
Date: 04/12/04
- Next message: localhost: "OLEDB Erros Enums?"
- Previous message: Bill: "Re: How do I programattically add a new row of data to a Typed DataSet?"
- In reply to: Jonathan Li: "Re: Can we use Unix as the server?"
- Next in thread: Jonathan Li: "Re: Can we use Unix as the server?"
- Reply: Jonathan Li: "Re: Can we use Unix as the server?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 12 Apr 2004 11:55:36 -0700
Jonathan,
I think everybody is on the same page here, so let me highlight the main
points:
Can you use Unix as the server? Yes, definitely. Ado.net is just a database
access lawyer and it can access data from any database for which an
available oledb or odbc provider is available.
Can your UNIX server be the application server? Not if you are using
Microsoft's version of .net, you would need a client machine running windows
to be your app server. When developing a web site for example you would use
windows 2003 server as the web server and use ado.net to connect to your
UNIX based server.
"the server side of .Net does not work under Unix" This just confuses the
issue needlessly. Most people don't run applications on database servers so
you should not be running into any issues related to this. You will have
.net running on the client or application server and use the Unix server
just to store data. You do not need any additional logic on the server.
Thanks,
-- Angel Saenz-Badillos [MS] Managed Providers This posting is provided "AS IS", with no warranties, and confers no rights.Please do not send email directly to this alias. This alias is for newsgroup purposes only. "Jonathan Li" <jonathanli888@hotmail.com> wrote in message news:ex4EOmGIEHA.3820@tk2msftngp13.phx.gbl... > > Greg, > > Thanks for your response. Actually I do not have much hands-on > experience of .Net at the moment. That's why I dropped my question > asking for advice. > > Based on the feedbacks I have received, the conclusion is that I have to > move away from Unix because the server side of .Net does not work under > Unix environment. Please refer to the earlier discussion on this thread. > > You may argue that, I can use Unix server as the database server (but > not the application server), i.e. to have the combination of VB.Net as > the clinet development environment + Unix as the database server + ODBC > connection. As for the application server, sorry I have no choice. If > that is so, I have utilized 0.1% of the power of .Net. Am I right? > > My plan was, to develop components at server side (something like EJBs). > For data entry and operation application functions, I can use C#.Net. > For reporting and enquiry functions, I can use ASP.Net. You may aware > that these two packages have a lot in common. Under J2EE environment, I > know how to it through EJBs the 'shared components'. Under .Net, what > should I do? Can I have the environment of C#.Net + ASP.Net + Unix > server (as database server as well as deployment server)? > > Best regards, > > Jonathan > > > > > *** Sent via Developersdex http://www.developersdex.com *** > Don't just participate in USENET...get rewarded for it!
- Next message: localhost: "OLEDB Erros Enums?"
- Previous message: Bill: "Re: How do I programattically add a new row of data to a Typed DataSet?"
- In reply to: Jonathan Li: "Re: Can we use Unix as the server?"
- Next in thread: Jonathan Li: "Re: Can we use Unix as the server?"
- Reply: Jonathan Li: "Re: Can we use Unix as the server?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
