R
Rob R. Ainscough
VS 2005 I have:
ClickOnce deployment
User's that hate and or don't want to use an IE Client (don't blame them)
I don't see how ASPX web pages are going to survive? With .NET 2.0 and
clickonce deployment my app is 427KB (even with modem dialup speed it
doesn't take long to download) -- the user gets a very friendly secure
WindowsForm app (most of them don't even notice they're not under IE
anymore) that performs considerably faster than any ASP.NET app.
The road map as I see it:
IE client -- back to static just clickonce links that open up
WindowsForms apps
Vista -- .NET 2.0 built in (no need to download)
WebServices -- called from WindowsForms apps (keeps it secure and
firewall friendly)
WindowsForms are a HELL of a lot more secure (no IE attached activex
components, no data miners, click monitors, etc. etc.)
The way I see it -- user interaction is going to move back to WindowsForms
since the IE client by definition is just NOT user friendly, NOT programmer
friendly, and has a ton of other issues surrounding it in terms of security
and performance and flexibility.
Don't get me wrong, web development will still exist (web services and basic
static content), but I believe anyone doing serious business applications
using the web will migrate to this approach -- it really is a win win.
ClickOnce deployment
User's that hate and or don't want to use an IE Client (don't blame them)
I don't see how ASPX web pages are going to survive? With .NET 2.0 and
clickonce deployment my app is 427KB (even with modem dialup speed it
doesn't take long to download) -- the user gets a very friendly secure
WindowsForm app (most of them don't even notice they're not under IE
anymore) that performs considerably faster than any ASP.NET app.
The road map as I see it:
IE client -- back to static just clickonce links that open up
WindowsForms apps
Vista -- .NET 2.0 built in (no need to download)
WebServices -- called from WindowsForms apps (keeps it secure and
firewall friendly)
WindowsForms are a HELL of a lot more secure (no IE attached activex
components, no data miners, click monitors, etc. etc.)
The way I see it -- user interaction is going to move back to WindowsForms
since the IE client by definition is just NOT user friendly, NOT programmer
friendly, and has a ton of other issues surrounding it in terms of security
and performance and flexibility.
Don't get me wrong, web development will still exist (web services and basic
static content), but I believe anyone doing serious business applications
using the web will migrate to this approach -- it really is a win win.