Are there main applications in .net

[Kevin]

We are trying to decide if we should be porting our applictions to
..net. Are there main stream applications that are .net?

We like the framework, but worry that if Microsoft decides to go
another direction we would have wasted our time moving to .net.

Are there any real world examples of current main stream applictions
that are written for .net.

Also: Is there a big performance hit moving applications to .net?

[John A. Bailo]

Kevin wrote:

We are trying to decide if we should be porting our applictions to
.net.

From what?
Are there main stream applications that are .net?
You mean like word processors?

No.

Web services?

Yes.

Web applications?

Yes.
Games?

None that I've seen.
Internal business applications?

TONS.

We like the framework, but worry that if Microsoft decides to go
another direction we would have wasted our time moving to .net.
Yes, you can sit at the bar with those VB6 programmers.
Are there any real world examples of current main stream applictions
that are written for .net.
Who uses real world applications any more? Most people spend 90
percent of their computer time filling out HTML forms.
Also: Is there a big performance hit moving applications to .net?

From logo?

No.

From vc++ native win32 api?

....mmmm...

[Kevin]

Our code is delphi (win32) and vc++ native win32. So mainly we are
concerned about moving our code from native win32 to .net.

suggestions? Things we should consider? Should we wait to see .net
mature or wait to see if it is here to stay for more than a few more
years?

Are there performance issues we should worry about?

Kevin

[Kevin Spencer]

Yes, there are a number of main stream apps that are written for the .Net
platform.

Also: Is there a big performance hit moving applications to .net?
Not a big one. The platform is very well optimized. I believe the trade-off
in terms of security and memory management, not to mention the absence of
the "DLL Hell" factor, more than make up for it.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Hard work is a medication for which
there is no placebo.

"Kevin" <we******@campbellsci.com> wrote in message
news:11**********************@g10g2000cwb.googlegr oups.com... We are trying to decide if we should be porting our applictions to
.net. Are there main stream applications that are .net?

We like the framework, but worry that if Microsoft decides to go
another direction we would have wasted our time moving to .net.

Are there any real world examples of current main stream applictions
that are written for .net.

Also: Is there a big performance hit moving applications to .net?

[Shaun McDonnell]

I honestly wouldn't worry about Microsoft moving away from .NET. It's there
niche.

Microsoft BizTalk Server is written in .NET as is Microsoft Operations Manager.

I think moving to .NET is good decision.

Performance hits are barely even noticeable (if there are any).

Shaun McDonnell

We are trying to decide if we should be porting our applictions to
.net. Are there main stream applications that are .net?

We like the framework, but worry that if Microsoft decides to go
another direction we would have wasted our time moving to .net.

Are there any real world examples of current main stream applictions
that are written for .net.

Also: Is there a big performance hit moving applications to .net?

[Nick Malik [Microsoft]]

"Kevin" <we******@campbellsci.com> wrote in message
news:11**********************@e56g2000cwe.googlegr oups.com...

Our code is delphi (win32) and vc++ native win32. So mainly we are
concerned about moving our code from native win32 to .net.
You are worried about moving off of delphi? Borland still supports Delphi,
and it is a fast platform, but it doesn't have much marketshare and Borland
has been pushing their Java products much more for a very long time. I can
see a good reason to move off of Delphi. It just isn't the main focus of
its vendor.

..Net is the main focus of Microsoft platform tools.

..Net 2.0 is fairly fast. That said, any language that requires a two-step
compile can suffer some performance hits. Java has the same concerns.
Between Java and .Net, you have probably 80% of new software development, so
I think we are safe to say that the idea has legs. :-)

suggestions? Things we should consider? Should we wait to see .net
mature
LOL! .Net was rolling out generic support before Java was. It is a fully
mature, fully vetted, wildly popular, extraordinarily stable platform.
Waiting will give you grey hair... not much else.

or wait to see if it is here to stay for more than a few more
years?
Did you say you were still using Delphi?

Are there performance issues we should worry about?

That depends on your app. Some users will experience some loss in
performance if you make a one-to-one conversion of the app. The techniques
needed to optimize .Net are different than the ones used to optimize Delphi
or C++, so apps that are ported often have some initial hiccups because the
'tricks' used to speed up Win32 apps can slow down a .Net app, and because
the dev team familiar with Win32 apps isn't familiar with how to optimize
for .Net.

Fortunately, this can be solved for the price of an ebook.

http://msdn.microsoft.com/library/de...l/ScaleNet.asp

Kevin

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--