.Net environment opinions

..Net
This is really something I have not been involved with.
However, we are using Optim EMS and had a reports package written. It relies
on .Net 2.0. It appears to be as flaky as certain types of Cadburys
chocolate.
Is .Net a shit environment (on XP) or should I "shoot the developer"

I realise this is an overly brief and trite enquiry! buy hey it's UKRM and
I'm doing more interesting stuff. My own bias suggests it is an environment
to encourage poor programming ;o)

 

Using the patented Mavis Beacon "Hunt&Peck" Technique, Hog

<perk>

Reports, you say? I can help.

--
Wicked Uncle Nigel - "He's hopeless, but he's honest"

WS* GHPOTHUF#24 APOSTLE#14 DLC#1 COFF#20 BOTAFOT#150 HYPO#0(KoTL) IbW#41
SBS#39 OMF#6 Enfield 500 Curry House Racer "The Basmati Rice Burner",
Honda GL1000K2 (Fallen apart) Suzuki TS250 "The Africa Single"
Norton 850 Commando Kawasaki GTR1400

 

Does the developer use tools for profiling, documenting, tracking issues,
unit testing, manage development lifecycle and other quality best practices,
or does he/she generate undocumented code, keep issues in [from:Excel sheet
toiece of paper], hand test, etc?

 

On site I use an automated document scanning package that relies on the
..net framework and also just helped install a complex noise meter
results analysis package that also does.

At home my USB hard disk system back up package is .net based.

I haven't noticed any problems with them (so far).

--

+-------------------------------------------------------------+
| Pete Fisher at Home: |
| Voxan Roadster Gilera Nordwest Yamaha WR250Z |
| Gilera GFR * 2 Moto Morini 2C/375 |
+-------------------------------------------------------------+

 

Not flakier than most other frameworks IME. However, I'd recommend not
to use a gun design by the same developer if you want to go shoot him.

IME at least it doesn't stop it, and it still offers plenty of
opportunity to **** up royally.

 

Lets put it this way, I know of one major insurer using .net 2.0 for
their entire customer facing operation, dealing with several million
customers, and it all pretty much works just as it should.

So, the technology itself isn't flawed, but either how it's been
implemented or possibly deployed, would be the place to start looking.

 

Do you pronounce that as "dot net two point oh point"?

 

dot net two dot zero

 

Using the patented Mavis Beacon "Hunt&Peck" Technique, dog

Point net two period zero.

--
Wicked Uncle Nigel - "He's hopeless, but he's honest"

WS* GHPOTHUF#24 APOSTLE#14 DLC#1 COFF#20 BOTAFOT#150 HYPO#0(KoTL) IbW#41
SBS#39 OMF#6 Enfield 500 Curry House Racer "The Basmati Rice Burner",
Honda GL1000K2 (Fallen apart) Suzuki TS250 "The Africa Single"
Norton 850 Commando Kawasaki GTR1400

 

Wot 'im said.

Most of our web-based (and several of our non-web based) packages are
..Net based. It works.

Crap programmers will write crap code even in the best frameworks..

It's also pretty thoroughly tested (both by Microsoft and by the
Microsoft Dev community) before it ever makes it out into the wide wide
world. Sure - there might be the odd bug in the framework (just like
there is in any other framework or set of libraries) but it's nothing
major and nothing to cause any great instability.

Phil.

 

Thank you for all your comments. The developer is on a week holiday. The 100
litre oil bath is warming now and should reach 90degC by Monday.

 

Well it is M$ after all ;o)

 

I wish you had never mentioned it, having just frittered away an hour or
so playing with #develop.


--

+-------------------------------------------------------------+
| Pete Fisher at Home: |
| Voxan Roadster Gilera Nordwest Yamaha WR250Z |
| Gilera GFR * 2 Moto Morini 2C/375 |
+-------------------------------------------------------------+