Linked by Thom Holwerda on Fri 11th Feb 2011 11:35 UTC
Thread beginning with comment 462231
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2010-09-23
Hopefully you do realise that web-applications CAN be .NET as well!
With proper code seperation, the actual business logic is nicely put in a seperate project and then a "WinForms" front-end is made for "inhouse power use" and a "WebForms" front-end is made for "access for everyone". More and more the WebForms front-end might be made into a Silverlight front-end as well, all running on the same back-end code.
Web-applications are nice for deployment and basic use
"Real" apllications just allow much more power
and basically ALL new Microsoft development is done with .NET, allowing web/windows/smartphone apps all from the same codebase all the time. Look at SharePoint or Expression products. Of course low level development still isn't done in .NET and tools like Office aren't (completely) converted (yet)