lol! Thanks guys. But i would post you an error message, but there is not
one. It says all installed great on these clients and then it cannot run a
..net 2.0 app.
As an earlier post said, install it again and again and again and suddenly,
oh it works. Of course i can't have that for a client, "yes please reinstall
10 times".
So i ask you, what hardware changed in those multiple installations?
It's that exact mentality "oh they can't test everything" that leads to this
standard, yes poor Microsoft, how dare i rip into a infinite resourced
company about their poor software release. You are right i should just
accept that it will have issues and deal with it. Of course that's a better
solution.
Automatic updates do only use critical updates yes, but when you release a
NEW VERSION of something do you know any other company ANY OTHER that
doesn't give you the "installing updates" message when you load their
software? No. And .net 1.1 is a mandatory update. You have to wonder, does
MS know full well that it has issues installing and so cannot put it on
their compulsory update list?
I am astounded that rather than agreement or "well its rubbish but there is
a hack to ensure it installs right" i have had replies of a defensive
nature. I am a software developer and a realist, i understand issues can
happen. But i have worked at smaller companies and our software releases go
without a hitch after extensive testing and we didn't create the operating
system the software runs on, we don't have the resources of a company such
as MS. So i am sorry but when you have that much at your disposal YES you're
software should damn well work first time or not be released until full
comprehensive testing can be done.
So i take it i just have to bend over and take this poor quality and HOPE my
clients have the hardware that maybe MS did use for testing. Hell i'll go
get an alternate operating system and have my software run on that, oh wait
a minute that'll be tricky considering MS rules the market. So i'd love to
give you an error log but their simply isn't one.
Any other suggestions?
"Duggi" <Du************ ***@gmail.comwr ote in message
news:11******** **************@ 42g2000cwt.goog legroups.com...
Hi
""""My software requires .net 2.0, as always good old MS STILL hasn't
put this
on the essential download so it doesn't go through with an automatic
update"""
I think automatic updates are for the sake of critical system updates.
(I do not know how MS defines "Critical") and other MS software that
make sense for MS business. Say IE7. (purely my assumption).
Obviously Not all the application require .Net runtime to run.
So it make sense not to place .net runtime on "Automatic updates".
Also definetly there may be a lot of hadware issues causing the error
and taking much time.
Please post error message you see and also the configuration of machine
on which .net runtime is supposed to be installed.
Check for the minmal requirements at
http://msdn2.microsoft.com/en-us/library/aa480241.aspx
Thank
-Srinivas,
Daniel wrote:
>Hi
My software requires .net 2.0, as always good old MS STILL hasn't put
this
on the essential download so it doesn't go through with an automatic
update.
Cleary they have a lot of faith in their own work!
Sorry that rant over, i have an issue where clients are downloading .net
2.0, installing it and STILL it ays it is not installe don their machine?
Is
there a trick to ensuring it installs? Or anything i can do to ensure it
gets on their machine? My software installs over the web via click once.
Thanks
