Re: In need of .NET advocacy
- From: "Alex" <inssup35@xxxxxxxxxxxxx>
- Date: Mon, 4 Apr 2005 23:08:57 -0400
Hello Olaf,
"Olaf Baeyens" <olaf.baeyens@xxxxxxxxxx> wrote in message news:42512e3b$0$20676$ba620e4c@xxxxxxxxxxxxxxxxx
> Although I am a big favour of .NET it has also cons sides.
> And it would morally be not right if I would hide these negative sides.
>
> * The resistance of people to install the .NET framework. You would not
> believe what stories they come up in order not to install it. Typical would
> be: It slows down my computer, It is too big, I don't believe in it,....
Not an issue in our case.
The customer gets a "black box", they should not care if it uses the CLR, the JVM or P-Code...
> * At this moment installing the .NET framework is far too complicated. New
> distributions of Windows XP seems to contain the .NET framework, but from
> the summer on we will have a new one the v2.0. So I hope the installation
> becomes a one click situation. The situation through critical updates is
> currently too complicated for my grandmother that wants to browse the
> Internet and read email.
Did I mention that our company makes money on support as well? :-)
> * Installation is a bit complicated because of the security issuses if the
> program needs internet and/or LAN access. Luckily this can be easily fixed
> by creating a managed dll that contains registration code to give your
> program enough access to access the LAN and Internet. You cannot grant
> access rights from inside your program, but you can make the setup run that
> managed code to give program user rights. The setup.exe is not a managed
> code so it does have access to the user rights. And if people double click
> on a setup then we assume that they know what they are doing.
Not relevant at this time but good to know.
> * The resistance of the VB and C++ programers since they have to relearn
> everything, becoming a newbie.
Nah, some our developers *want* to switch and the rest will be pigeonholed into maintaining old C++/COM/MFC/ATL code.
> * The error reporting that would give a user a heart attack when something
> goes wrong like no LAN access, or when you try to run the program from a
> networkdrive by double clicking on it. You get an error like the "access
> violation" type with a list of all assemblies loaded, where even normal
> programmers have no idea what it all means. This is very user-unfriendly.
Looks like an uncaught exception to me (and we know what to do with those in any language).
> These are the ones that comes to my mind...
So far, they all seem to have reasonable workarounds.
Best wishes,
Alex.
--
Address email to user "response" at domain "alexoren" with suffix "com"
.
- References:
- Re: In need of .NET advocacy
- From: Alex
- Re: In need of .NET advocacy
- From: Olaf Baeyens
- Re: In need of .NET advocacy
- From: Alex
- Re: In need of .NET advocacy
- From: Olaf Baeyens
- Re: In need of .NET advocacy
- From: Alex
- Re: In need of .NET advocacy
- From: Olaf Baeyens
- Re: In need of .NET advocacy
- Prev by Date: Re: Visual studio denying access to database in Server Explorer
- Next by Date: Re: In need of .NET advocacy
- Previous by thread: Re: In need of .NET advocacy
- Next by thread: Re: In need of .NET advocacy
- Index(es):
Relevant Pages
|