This is more of a conceptual question:
1. More and more companies are using VPN's and locking out internet
connectivity (for a host of reasons, security, productivity, etc.).
2. ASP.NET requires a web server and has more layers than a .NET Windows
application
3. a .NET windows app .DLL's and .EXEs are very small
So which is better, offer a Windows .NET component ("managed") that can be
downloaded installed from a web site or distributed in some other manner
(CD, ftp, VPN) that runs faster and has a much more responsive user
interface OR an ASP.NET web server based that has a slow IE client - many
more layers & configuration dependancies. Both can commuincate with a host
of databases backends.
Since .NET framework is multi-platform and a managed .NET app can operate on
multiple platforms, it seems to me that .NET windows forms apps are actually
a better solution than ASP.NET approach (with it's host of other
requiresments and security issues).
The downside is that the component needs to be installed on the client PC,
but the reality is that most people work on a one or two, maybe 3 PC's.
Since these .NET app components are small (most of my .NET apps are well
below 1MB, most around 500KB or less) a single download will often be a lot
faster than processing ASP.NET pages.
Sooo...where does this go? I'm thinking that .NET windows apps are indeed a
better solution (in most cases) than ASP.NET web apps -- certainly a LOT
faster in execution and have less layers, more secure, and much easier to
maintain.
I think the automatic distribution of .NET framework is now changing the
decisions to go Windows Form or ASP/web server. Both worlds are now open,
perhaps the era of the IE client is numbered?
rob. 5 1723
The days of IE are not numbering simply because of security concerns: a .NET
windows component can do anything on your machine. Of course, you can
always say that you can start playing around with the security settings but
that doesn't change an iota to the real problem; as we have all learning
from the Java experience: you can take the time of doing a full security and
background check (minutes, hours, days, months, ...) on each site when you
are navigating the internet and touring many dozens of sites a day.
S. L.
"Rob R. Ainscough" <ro*****@pacbel l.net> wrote in message
news:Om******** ******@TK2MSFTN GP09.phx.gbl... This is more of a conceptual question:
1. More and more companies are using VPN's and locking out internet connectivity (for a host of reasons, security, productivity, etc.). 2. ASP.NET requires a web server and has more layers than a .NET Windows application 3. a .NET windows app .DLL's and .EXEs are very small
So which is better, offer a Windows .NET component ("managed") that can be downloaded installed from a web site or distributed in some other manner (CD, ftp, VPN) that runs faster and has a much more responsive user interface OR an ASP.NET web server based that has a slow IE client - many more layers & configuration dependancies. Both can commuincate with a host of databases backends.
Since .NET framework is multi-platform and a managed .NET app can operate on multiple platforms, it seems to me that .NET windows forms apps are actually a better solution than ASP.NET approach (with it's host of other requiresments and security issues).
The downside is that the component needs to be installed on the client PC, but the reality is that most people work on a one or two, maybe 3 PC's. Since these .NET app components are small (most of my .NET apps are well below 1MB, most around 500KB or less) a single download will often be a lot faster than processing ASP.NET pages.
Sooo...where does this go? I'm thinking that .NET windows apps are indeed a better solution (in most cases) than ASP.NET web apps -- certainly a LOT faster in execution and have less layers, more secure, and much easier to maintain.
I think the automatic distribution of .NET framework is now changing the decisions to go Windows Form or ASP/web server. Both worlds are now open, perhaps the era of the IE client is numbered?
rob.
You should watch the MS webcast on "Smart Clients"
Rob R. Ainscough wrote: This is more of a conceptual question:
1. More and more companies are using VPN's and locking out internet connectivity (for a host of reasons, security, productivity, etc.). 2. ASP.NET requires a web server and has more layers than a .NET Windows application 3. a .NET windows app .DLL's and .EXEs are very small
So which is better, offer a Windows .NET component ("managed") that can be downloaded installed from a web site or distributed in some other manner (CD, ftp, VPN) that runs faster and has a much more responsive user interface OR an ASP.NET web server based that has a slow IE client - many more layers & configuration dependancies. Both can commuincate with a host of databases backends.
Since .NET framework is multi-platform and a managed .NET app can operate on multiple platforms, it seems to me that .NET windows forms apps are actually a better solution than ASP.NET approach (with it's host of other requiresments and security issues).
The downside is that the component needs to be installed on the client PC, but the reality is that most people work on a one or two, maybe 3 PC's. Since these .NET app components are small (most of my .NET apps are well below 1MB, most around 500KB or less) a single download will often be a lot faster than processing ASP.NET pages.
Sooo...where does this go? I'm thinking that .NET windows apps are indeed a better solution (in most cases) than ASP.NET web apps -- certainly a LOT faster in execution and have less layers, more secure, and much easier to maintain.
I think the automatic distribution of .NET framework is now changing the decisions to go Windows Form or ASP/web server. Both worlds are now open, perhaps the era of the IE client is numbered?
rob.
--
Incognito Blog { Updated Almost Daily } http://incognito.texeme.com
Security wasn't really my point -- IE client is slow & layered -- many large
corporations (and smaller ones too) go the VPN route. And I wasn't really
suggesting a problem -- just questioning the concept of IE vs. the reality
of what people need, what businesses need, and how IE has seemed to gone
full circle (getting fatter along the way) only to be a slower & less secure
solution.
I realize IE will never go away because of it's advertisement potential
entering into the homes of millions -- but when you think about it --
Cookies and host of other components needed by IE and one web server based
net App, it really seems just like a bloated slower version of what can be
contained in .NET framework with very small distribution .NET windows
apps -- you cut out the web server, you cut out the IE translation, and you
cut out the execution of malicious code the end user never wanted or needed
(such as data miners, trackers, etc. etc.).
What I am noticing is that more and more businesses are moving away from IE
(for whatever reasons) based projects.
Rob.
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:OY******** **********@TK2M SFTNGP11.phx.gb l... The days of IE are not numbering simply because of security concerns: a .NET windows component can do anything on your machine. Of course, you can always say that you can start playing around with the security settings but that doesn't change an iota to the real problem; as we have all learning from the Java experience: you can take the time of doing a full security and background check (minutes, hours, days, months, ...) on each site when you are navigating the internet and touring many dozens of sites a day.
S. L.
"Rob R. Ainscough" <ro*****@pacbel l.net> wrote in message news:Om******** ******@TK2MSFTN GP09.phx.gbl... This is more of a conceptual question:
1. More and more companies are using VPN's and locking out internet connectivity (for a host of reasons, security, productivity, etc.). 2. ASP.NET requires a web server and has more layers than a .NET Windows application 3. a .NET windows app .DLL's and .EXEs are very small
So which is better, offer a Windows .NET component ("managed") that can be downloaded installed from a web site or distributed in some other manner (CD, ftp, VPN) that runs faster and has a much more responsive user interface OR an ASP.NET web server based that has a slow IE client - many more layers & configuration dependancies. Both can commuincate with a host of databases backends.
Since .NET framework is multi-platform and a managed .NET app can operate on multiple platforms, it seems to me that .NET windows forms apps are actually a better solution than ASP.NET approach (with it's host of other requiresments and security issues).
The downside is that the component needs to be installed on the client PC, but the reality is that most people work on a one or two, maybe 3 PC's. Since these .NET app components are small (most of my .NET apps are well below 1MB, most around 500KB or less) a single download will often be a lot faster than processing ASP.NET pages.
Sooo...where does this go? I'm thinking that .NET windows apps are indeed a better solution (in most cases) than ASP.NET web apps -- certainly a LOT faster in execution and have less layers, more secure, and much easier to maintain.
I think the automatic distribution of .NET framework is now changing the decisions to go Windows Form or ASP/web server. Both worlds are now open, perhaps the era of the IE client is numbered?
rob.
For an Intranet, you're totally right; but for the Internet, many Extranets
and B2B, .NET client applications and even Smart Clients are totally out of
consideration at this moment for security reason.
I've myself be punched on that subject by a potential client and the simple
mention of it in a free discussion has been sufficient to get me out of the
course definitely.
S. L.
"Rob R. Ainscough" <ro*****@pacbel l.net> wrote in message
news:%2******** *******@TK2MSFT NGP09.phx.gbl.. . Security wasn't really my point -- IE client is slow & layered -- many large corporations (and smaller ones too) go the VPN route. And I wasn't really suggesting a problem -- just questioning the concept of IE vs. the reality of what people need, what businesses need, and how IE has seemed to gone full circle (getting fatter along the way) only to be a slower & less secure solution.
I realize IE will never go away because of it's advertisement potential entering into the homes of millions -- but when you think about it -- Cookies and host of other components needed by IE and one web server based net App, it really seems just like a bloated slower version of what can be contained in .NET framework with very small distribution .NET windows apps -- you cut out the web server, you cut out the IE translation, and you cut out the execution of malicious code the end user never wanted or needed (such as data miners, trackers, etc. etc.).
What I am noticing is that more and more businesses are moving away from IE (for whatever reasons) based projects.
Rob.
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> wrote in message news:OY******** **********@TK2M SFTNGP11.phx.gb l... The days of IE are not numbering simply because of security concerns: a .NET windows component can do anything on your machine. Of course, you can always say that you can start playing around with the security settings but that doesn't change an iota to the real problem; as we have all learning from the Java experience: you can take the time of doing a full security and background check (minutes, hours, days, months, ...) on each site when you are navigating the internet and touring many dozens of sites a day.
S. L.
"Rob R. Ainscough" <ro*****@pacbel l.net> wrote in message news:Om******** ******@TK2MSFTN GP09.phx.gbl... This is more of a conceptual question:
1. More and more companies are using VPN's and locking out internet connectivity (for a host of reasons, security, productivity, etc.). 2. ASP.NET requires a web server and has more layers than a .NET Windows application 3. a .NET windows app .DLL's and .EXEs are very small
So which is better, offer a Windows .NET component ("managed") that can be downloaded installed from a web site or distributed in some other manner (CD, ftp, VPN) that runs faster and has a much more responsive user interface OR an ASP.NET web server based that has a slow IE client - many more layers & configuration dependancies. Both can commuincate with a host of databases backends.
Since .NET framework is multi-platform and a managed .NET app can operate on multiple platforms, it seems to me that .NET windows forms apps are actually a better solution than ASP.NET approach (with it's host of other requiresments and security issues).
The downside is that the component needs to be installed on the client PC, but the reality is that most people work on a one or two, maybe 3 PC's. Since these .NET app components are small (most of my .NET apps are well below 1MB, most around 500KB or less) a single download will often be a lot faster than processing ASP.NET pages.
Sooo...where does this go? I'm thinking that .NET windows apps are indeed a better solution (in most cases) than ASP.NET web apps -- certainly a LOT faster in execution and have less layers, more secure, and much easier to maintain.
I think the automatic distribution of .NET framework is now changing the decisions to go Windows Form or ASP/web server. Both worlds are now open, perhaps the era of the IE client is numbered?
rob.
<"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam
please)>> wrote: The days of IE are not numbering simply because of security concerns: a .NET windows component can do anything on your machine.
I don't think it can by default. You can make it *insecure* by playing
around with security, but I believe that by default it's in a
relatively low trust environment.
--
Jon Skeet - <sk***@pobox.co m> http://www.pobox.com/~skeet
If replying to the group, please do not mail me too This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: Az Tech |
last post by:
Hi people,
(Sorry for the somewhat long post).
I request some of the people on this group who have good experience
using object-orientation in the field, to please give some good ideas
for topics to include in a course on object-orientation that I'm going
to conduct.
(I will later summarize all the replies and discussion, for the
|
by: Rob R. Ainscough |
last post by:
This is more of a conceptual question:
1. More and more companies are using VPN's and locking out internet
connectivity (for a host of reasons, security, productivity, etc.).
2. ASP.NET requires a web server and has more layers than a .NET Windows
application
3. a .NET windows app .DLL's and .EXEs are very small
So which is better, offer a Windows .NET component ("managed") that can be
downloaded installed from a web site or...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
| |
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
|
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...
| |