.NET and Longhorn

[Guest]

I have heard that your existing applications written in .NET will not work on Longhorn unless you recompile them or retouch them in some matter

Is this correct

If so, why would anyone start to write application in .NET until Longhorn becomes available

Thanks

 

[Jon Skeet [C# MVP]]

I have heard that your existing applications written in .NET will not
work on Longhorn unless you recompile them or retouch them in some
matter?

Is this correct?

As Longhorn hasn't been released yet, who can say? They may well not
work with the builds which people are testing (I don't know, not having
tried it myself), but don't forget it's not even an alpha build yet. I
would *expect* MS to sort that out before release.

If so, why would anyone start to write application in .NET until
Longhorn becomes available?

Well, Longhorn is quite a way off yet, and not everyone is going to
upgrade immediately anyway. I expect it'll be at least mid to late 2007
before even half of Windows users have Longhorn. Just how long is your
product lifecycle?

 

[Nick Holmes]

I've not heard that, and frankly I sceptical, but it might be true. What I
would really like to address is:

If so, why would anyone start to write application in .NET until Longhorn

becomes available?

The answer is simply that .Net is a great development plaform that works
right here, right now. If there are issuse with Longhorn in 18-24 months
time, I'll worry about those then. For me, 18-24 months represents about 3
major project lifecycles.

Nick Holmes.