all groups > dotnet academic > june 2004 >
You're in the

dotnet academic

group:

.Net vs Lotus Notes?


.Net vs Lotus Notes? Jon Walkabout
6/15/2004 6:03:01 AM
dotnet academic:
Can anyone tell me why .Net is a superior technology over Lotus Notes? (Ie. When a new product is designed on a .Net platform and their competitors product is based upon Lotus Notes technology!)

Thanks for your help,
Re: .Net vs Lotus Notes? Steven H
6/17/2004 4:21:04 PM
[quoted text, click to view]

i cant really help with your question, but i *honestly thaught* lotus notes
was some sort of Office Application - kinda like Open Office.

ahh well i like learning things so this is a good experience for me


--
-------------------------------------------
Steven H, 3rd Year B.I.T. Otago Polytechnic

Re: .Net vs Lotus Notes? AspDotNetDeveloper
6/18/2004 8:19:24 AM
One of the biggest reasons, is that you are not limiting yourself to Lotus
Notes applications. With .Net, you can do anything, and the customer does
not have to use Lotus Notes, in order to utilize your application.

Lotus Notes is nice, if the company uses Lotus Notes, but you're kind of
stuck if they don't. It's like comparing apples to oranges really.

We use Lotus Notes 5 internally where I work. I've had some exposure to the
development environment, and although it can be a powerful RAD environment,
I find it kind of clunky. although I heard that the new LN that I think is
out already, is MUCH better!

I would go with .Net all the way, unless you want to be labeled a Lotus
Notes programmer... somewhat limiting when looking for work, but definitely
do-able, if you like LN.

[quoted text, click to view]
(Ie. When a new product is designed on a .Net platform and their competitors
product is based upon Lotus Notes technology!)
[quoted text, click to view]

Re: .Net vs Lotus Notes? Ed Kaim [MSFT]
7/3/2004 4:35:54 PM
It really depends on what your goals are. In the case of customizing Notes
to take care of lightweight needs, you're probably best off having something
that customizes Notes. I would say the same thing regarding Office
deployments, such as if you were to use VBA for customizing Office or the
Visual Studio Tools for Office to build applications that use pieces of
Office as core application functionaility. However, if you're looking at
more significant functionaility, a general purpose application platform like
the .NET Framework is probably a better bet because you won't run into the
same barriers.

[quoted text, click to view]

AddThis Social Bookmark Button