Bonnie;

Within the last few months several developers have made statements about Dot NET technology. Some have said it is not ready for WinForms and others have said not to use it for Browser based applications. Those are absolute statements but people like you help to prove these conclusions to be incorrect. This type of information is almost like the rumors about the demise of a product from Microsoft I will not mention as the topic has passed the nauseous stage.

I think the reason we get such comments is that people have not been successful with the technology. My thought on this topic is that there is a lot to learn and you have to do your homework. Granted there are some things we would all like to have added to what we have at present but we can (in most cases) make due with the present technology and offerings.

Tom


>Mario,
>
>Hmmm ... where to start? I think I'll just comment on one aspect of your post ... you seem to think that .NET is ok to use for browser-based, WebForm, server-side apps(ASP.NET), but not ready-for-prime time for rich-client, WinForm applications. That's just not true. Our app is almost entirely a rich-client, WinForm client/server application. It's not slow. It's not that difficult to deploy. I'm not sure how you came up with the conclusions you have, but I'm betting it's not from practical experience. We don't have a lot of customers yet, but deployment to those few customers has *not* been the nightmare you make it out to be and performance of the application has been just fine as well.
>
>~~Bonnie
>
>
>
>>I never use book...web instead so...
>>
>>>> "Microsoft has admitted that their hopes for .NET haven't been realized."
>>Pretty obvious... .NET, the dev tools is the only real thing, not the other hyped .NET things.
>>
>>>>But are things looking rosey, as far as you can see, or is there cause for concern? It would be interesting to hear your opinions. Thanks!
>>
>>A lot of concern: New tools, new frameworks, at least in the MS camp, a ALL or NOTHING proposition... Low performance in client side, runtime hell, problematic deployment not because is necesary install a medium size 20MB runtime but HUGE prerequisites...A lot of code requiered for simply task..Developers have problem "get" .NET if not have previous exposure&expertise in good OO practiques...
>>
>>The plataform not move so good, Whidbey is delayed, Yukon too. Next-Hyped OS is delayed (the os that enable real .NET power). This can concern you or no. Not concern me anyway...
>>
>>Use .NET in client for uncrontroled deployment (ie: not departamental app for internal use) is a lose move. Simply not have sense.
>>
>>Like Java, .NET is wonderfull for server-side, web pages & web service.
>>
>>In the other side, ignoring .NET is not smart too. Simply be aware that .NET is the *next* MS thing and a lot of buzz apply, but no so much value away server side (that is no so bad anyway).
>>
>>We are in a inflexion point, we have this Linux movement, the Java side is strong, new directions in MS, new frameworks, new OS and a security strategy that can cause a lock more hard to break than anything else...New hardware in the road (64 bits, new motherboard&PCI, new graphic generation)...Plus the mobile, xml & webservices.
>>
>>Measure your moves. If you can IGNORE linux, java&open source you can go all for .NET more or less safely. If not, you need a mix of tools, or a capable croos dev tool like Delphi, or hope for succes of MONO...
>>
>>Plus, take in account that the large cost is in the deployment phase. Deploy to server is insignificant but deploy .NET to a lot of clients that can hurts.
>>
>>But not ignore .NET. If can, have a foot in everyplace ;)