i have run four laptops and two desktops that have all had one issue or another with the .net framework and accessibility. it always tends to be the gui side of things. i was running che's railracer game fine before i got this new system, although it was the registration dialogs and the track editor programs that i had problems with. on this system whenever i run any .net based app it comes up with one of those annoying error dialogs claiming that the program has encountered a problem and needs to close.
as for the vs.net, again, on all systems of running it except on one of my friend's computers, it would always crash and say it wasn't responding, whereas on the friend's computer jaws was having a problem with it, saying that there were errors in the script and acting up that way. so on the six computers i've been using to run .net apps in general, and the four computers i used to try out vs.net, it has always acted up one way or another. regards, damien ----- Original Message ----- From: "Thomas Ward" <[EMAIL PROTECTED]> To: "Gamers Discussion list" <[email protected]> Sent: Thursday, February 22, 2007 11:28 PM Subject: Re: [Audyssey] Important notice. > Hi Damien, > I have no idea where you have gathered your information about the .NET > Framework, but it is very much incorrect. The .NET Framework itself is > completely accessible. As for the development ides VS 2003 and VS 2005 > are also accessible provided you are using a fairly modern version of > Jaws or Window Eyes. If you are using something like Jaws 4 or 5 forget > it. With Jaws 7-8 or Window Eyes 5.5-6.0 then VS .NET is fine. I'd say > through end user experience Window eyes support for Visual Studio .NET > is superior to the half-hearted attempt Jaws is using. > As far as stibility from .NET Framework 2.0 onward it has been pretty > stable. Just because you may have had some end user bad experiences, can > happen with any piece of software, doesn't make it true the software is > deffective or buggy most of the time. > In fact, my experience in the field is I have very little problem with > the framework when end users were not running mised matched versioning, > and wasn't awareyt he framework needed to be installed prier to > installing a managed component for DirectX, SAPI, and some of the newer > technologies MS has come out with. > Bottomline I don't know what flaws you speak of, and I run several > Framework based apps with absolutely no trouble at all. > As for Vista's classic option it resorts to a XP style desktop. The > truly classic desktop option you are thinking of no longer really exists > as far as I am awayre. However, you can turn off the Windows Arrow 3D > desktop which is a major accessibility hangup at the moment which I will > certainly be doing. > > > damien c. sadler - head of x-sight interactive wrote: >> i don't know why everyone is getting so uptight about .net. i mean, it's >> new >> technology, so it'll probably have many flaws until at least two or three >> years of upgrading, and like xp, vista should have a classic option. yes, >> speech technology may advance, but with the new accessibility engine >> people >> are having to learn from scratch again, not to mention also having to >> switch >> to .net which is already not accessible. >> > > > _______________________________________________ > Gamers mailing list .. [email protected] > To unsubscribe send E-mail to [EMAIL PROTECTED] You can > visit > http://audyssey.org/mailman/listinfo/gamers_audyssey.org to make > any subscription changes via the web. _______________________________________________ Gamers mailing list .. [email protected] To unsubscribe send E-mail to [EMAIL PROTECTED] You can visit http://audyssey.org/mailman/listinfo/gamers_audyssey.org to make any subscription changes via the web.
