Re: Is .NET going to be dropped by Microsoft?
From: Mike McIntyre (mikemc_at_dotnetshowandtell.com)
Date: 11/10/04
- Next message: Mike McIntyre: "Re: Is .NET going to be dropped by Microsoft?"
- Previous message: Ken Dopierala Jr.: "Re: Casting?"
- In reply to: Rob R. Ainscough: "Re: Is .NET going to be dropped by Microsoft?"
- Next in thread: Brian Henry: "Re: Is .NET going to be dropped by Microsoft?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 10 Nov 2004 15:50:13 -0800
Rob,
>Performance is more GUI specific, slow redraws/repaints of forms/controls
>as compared to VB6 or VC or C++.
For line-of-business applications using .NET's paint optimization features
will beat VB6 and be close enough to C++ that business users will not be
able to tell the difference. Under the most extreme situations a .NET
programmer may need to use some C# unsafe code, nGen'd MC++ or Windows API -
all of which are allowed in .NET.
----------------------
>Data gathering is pretty quick (from SQL server or Access or whatever
>else), but control population is VERY slow.
Asynchonous delegates and/or threading should be used here. Very fast by all
benchmarks published the past two years. Its always possible to immediately
populate the controls in context (in play on the form), give the user
control, and flow the remainder of the data asynchronously in the
background.
----------------------
>Security in regards to the fundamental implementation of .NET -- since it
>is one level removed interpreted (albeit, highly optimized interpretation)
>it is pretty easy to swap in "rogue" code.
I have seen a few claims that this was possible the past three years but I
havn't seen a case where someone could do this against a properly
implemented .NET application running on a properly configured (security)
computer.
Right now it is possible to create some of the most secure code ever
possible with .NET.
---------------------
>Another issue is the missing features in the current .NET release that make
>it hard for developers to remain in the "managed" world of .NET.
Personally I have never had this problem developing enterprise
line-of-business applications for my clients - one of which is Bank of
America.
--------------------
>My sources are from some relatively large organizations such as Bank of the
>West, Bank of America, SBC, ATI, and a few others -- from senior management
>and developers influential in the decision process.
I can't dispute what you heard. What you heard is what you heard.
>From my enterprise customers, others I know in the industry, and what
Gartner claims - I havn't heard anything about plans to drop .NET or that
there is some sort of wholesale issue with it.
The latest Gartner results show .NET has reached critical mass (57%) in
large to medium enterprises and that intentions for those who have not moved
yet to move to .NET in the coming 18 months is at a all time high.
My company, aZ Software Developers, has seen its JAVA contracts go from of
3/4 of our business in 2001 to about 1/5 today. Our customers mostly require
we develop new applications with .NET now.
--------------
>Can YOU be more specific in addressing where Microsoft plan to take .NET in
>the next 5 years?
Most Microsoft embedded device development has or is transtitioning to .NET
Framework based development.
Visual Studio 2005 - .NET Framework 2.0 In beta, release sometime after
middle of 2005.
Sql Server 2005 - In beta, release after middle of 2005. Has deep support
for Microsoft .NET Framework.
Longhorn (next generation of Windows operating system). .NET is embedded in
this, the next generation of the Windows OS slated for release in 2006.
"Longhorn" will expose APIs that are a completely managed set of class
libraries built with the .NET Framework. These APIs expose functionality
that covers the full range of interactions with the operating system,
including the user interface, graphics, storage, communications, documents,
and multimedia. The majority of "Longhorn"-based applications can be
entirely written using these new "Longhorn" managed APIs. Developing managed
code applications now positions your company to take advantage of "Longhorn"
once it is released and also offers immediate advantages.
For an indepth look at where Microsoft is taking .NET over the next five
years and beyond:
http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx
------------------
While nothing is impossible, dropping .NET at this point would be like
ripping the engine out of a fighter jet in mid-air IMHO. ;-)
-- Mike Mike McIntyre Visual Basic MVP www.getdotnetcode.com "Rob R. Ainscough" <robains@pacbell.net> wrote in message news:udP7Hb1xEHA.1452@TK2MSFTNGP11.phx.gbl... > Performance is more GUI specific, slow redraws/repaints of forms/controls > as compared to VB6 or VC or C++. Data gathering is pretty quick (from SQL > server or Access or whatever else), but control population is VERY slow. > > Security in regards to the fundamental implementation of .NET -- since it > is one level removed interpreted (albeit, highly optimized interpretation) > it is pretty easy to swap in "rogue" code. > > Another issue is the missing features in the current .NET release that > make it hard for developers to remain in the "managed" world of .NET. > > My sources are from some relatively large organizations such as Bank of > the West, Bank of America, SBC, ATI, and a few others -- from senior > management and developers influential in the decision process. > > Can YOU be more specific in addressing where Microsoft plan to take .NET > in the next 5 years? > > Thanks, Rob. > > "Mike McIntyre" <mikemc@dotnetshowandtell.com> wrote in message > news:O9TKxS1xEHA.3168@TK2MSFTNGP15.phx.gbl... >> No, it is not being dropped. Where did you hear such a thing? >> >> Performance issues will be in the way you implement .NET, not in the >> technology itself. >> >> Same with security. >> >> Feel free to post your specific problems here - or write to me directly >> if you like. >> >> >> -- >> Mike >> >> Mike McIntyre >> Visual Basic MVP >> www.getdotnetcode.com >> >> >> >> "Rob R. Ainscough" <robains@pacbell.net> wrote in message >> news:OgMaTO1xEHA.2568@TK2MSFTNGP11.phx.gbl... >>>I keep hearing persistant rumors (along with my own experience) that .NET >>>is going to be abandon by Microsoft due to performance & security issues? >>>I realize no one from Microsoft is likely to confirm this publically, but >>>if anyone that does have insider knowledge, could you provide some >>>feedback (private or public). My company is on the verge of migrating to >>>.NET, but we've ran into several performance issues (mostly on the GUI >>>side) and some big security issues and we're not sure they can be >>>resolved without a fundamental "shift" from Microsoft. I've very >>>hesitant to migrate all our code over until I can get a firm grasp on >>>where .NET is going and for how long and what issues are going to be >>>resolved. >>> >>> Thank you. >>> >>> Rob. >>> >> >> > >
- Next message: Mike McIntyre: "Re: Is .NET going to be dropped by Microsoft?"
- Previous message: Ken Dopierala Jr.: "Re: Casting?"
- In reply to: Rob R. Ainscough: "Re: Is .NET going to be dropped by Microsoft?"
- Next in thread: Brian Henry: "Re: Is .NET going to be dropped by Microsoft?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
