What do you like or dislike from this .NET?

  • Thread starter Thread starter Olaf Baeyens
  • Start date Start date
O

Olaf Baeyens

I am wondering what other people like or dislike about the .NET?

Like: Almost everything except below.
Dislike: The fact that the .NET is not pre-installed on all Windows machines
making it harder to deploy my software.
Dislike: Running a .NET program on a network share without enough
permissions or when the .NET is not installed blows up in your face with
some cryptic error that gives people the same scare like a blue-screen.

Wishlist: Add the .NET framework to the critical updates.
 
AFAIK this is the case (I heard that XP SP2 includes the framework and know
that newer OS does). Of course until some time people with "older" computers
will have to install .NET if they want to run .NET local applications. They
have anyway an update to do (if not the framework, they should install the
update that installs the framework).

As a side note a critial update is AFAIK one that puts security in stake.
The framework is *not* a critical update.

For the permission, AFAIK this is just the default message. You can alter
this behavior and display your own message instead of letting the runtime
pop up...

Patrice
 
AFAIK this is the case (I heard that XP SP2 includes the framework and
know
that newer OS does).
Click to expand...
As far as I know, SP2 only installs (upgrades) the .NET if it was already
installed.
As a side note a critial update is AFAIK one that puts security in stake.
The framework is *not* a critical update.
Click to expand...
You are right about this.
For the permission, AFAIK this is just the default message. You can alter
this behavior and display your own message instead of letting the runtime
pop up...
Click to expand...
I have the impression that the C# program double clicked on a network folder
does not have the ability to execute, so your custom errorbox will not even
have any rights to do something.

But even if it does, it gives a huge overhead to the beginning .NET
developer, that is struggeling to make his program run on the network drive.
It took me about 6 months before I finally understood the policy and
permission thing, so many times I just gave up on trying to program using
the .NET. Now that I finally understand the system, I like it very much. The
second biggest problem was giving rights to the program to run, without
expecting the user to have a IT diplom. I finally resolved that problem in
the installer too, but it took a lot of trials and errors to get it right.

It would be nice if the program can show a messagebox explaing what is wrong
and how to correct it. But in the case of the C# on a network folder, it
cannot do it because it cannot run, so the Windows should at least give some
user friendly way of helping the user to get it right.
 
I have the impression that the C# program double clicked on a network
folder
does not have the ability to execute, so your custom errorbox will not
even
have any rights to do something.

But even if it does, it gives a huge overhead to the beginning .NET
developer, that is struggeling to make his program run on the network
drive.
It took me about 6 months before I finally understood the policy and
permission thing, so many times I just gave up on trying to program using
the .NET. Now that I finally understand the system, I like it very much.
The
second biggest problem was giving rights to the program to run, without
expecting the user to have a IT diplom. I finally resolved that problem in
the installer too, but it took a lot of trials and errors to get it right.

It would be nice if the program can show a messagebox explaing what is
wrong
and how to correct it. But in the case of the C# on a network folder, it
cannot do it because it cannot run, so the Windows should at least give
some
user friendly way of helping the user to get it right.
Click to expand...

While I do agree that a more userfriendly display would be *very*
helpful(I've been bitten by this a couple of times myself), I have to admit
that this is probably the right policy to have.

Unfortunatly security and ease do not go hand in hand.

Perhaps you should make a recommendation for this on the feedback center?
 
While I do agree that a more userfriendly display would be *very*
helpful(I've been bitten by this a couple of times myself), I have to admit
that this is probably the right policy to have.
Click to expand...
The good point is that it gives the developer the responsibility to process
the exception.
But the big problem is that you need to be very experienced in this before
you can do it right.
Thus adding a huge learning curve before you have your first functional
program, that is bigger than a simple "Hello program".

The thing is, that we do get a dialog box with a list of assemblies and
stuff, why not enhance this dialog box with a more user friendly response
and a button "details" with the more detailed debugging stuff.

One thing I do realize is that the .NET is still in its infacy and given
enough time and experience that in the future this will become more user
friendly.
We are in a transition period, which is normal I think.
Unfortunatly security and ease do not go hand in hand.
Click to expand...
Completly right about this.
Perhaps you should make a recommendation for this on the feedback center?
Click to expand...
I think Microsoft read these news groups too, maybe they learn from this?
 
I think Microsoft read these news groups too, maybe they learn from this?
Click to expand...
Maybe, but the feedback center is more direct and you may have better luck
garnering support from other users.
 
Back
Top