WinFX and ASP.NET

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Does WinFX (.net framework 3.0) provide any benefits for asp.net
applications? I'm reading up on WinFX and it sounds like it's specifically
geared for Windows Vista. If I want to upgrade my asp.net apps from
framework 1.1 should I migrate to 2.0 or 3.0?

Thanks.
 
Hello Mike,

Firstly, WinFX is not a .NET 3.0, it's just WinFX or .NET 3.0 Services.
..NET 3.0 is just .NET 2.0 + WinFX

M> Does WinFX (.net framework 3.0) provide any benefits for asp.net
M> applications?

Nope.

m> I'm reading up on WinFX and it sounds like it's specifically geared for
Windows Vista.

The power of WinFX is in WPF,WCF,WF,CardSpace.
Probably you meant WPF. WinFX provide XBAP to use XAML in browsers.
The real shortcoming of XBAP is that client need to have .NET 3.0 on his
machine.

To avoid this MS is working on WPF/E ("WPF everywhere" with cross-platform-browsers
fearures), but this is too young product, no CTP is even available

M> If I want to upgrade my
M> asp.net apps from framework 1.1 should I migrate to 2.0 or 3.0?

To 2.0 (.NET 3.0 redistributive is just 2.0 + WinFX Services)
---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
 
Thank you very much for taking the time to articulate such a thorough
response. You gave me a much better understanding of this concept.

Mike
 
Hi,

Michael said:
Hello Mike,

Firstly, WinFX is not a .NET 3.0, it's just WinFX or .NET 3.0 Services.
.NET 3.0 is just .NET 2.0 + WinFX
Click to expand...

It's not totally correct.

WinFX was a code name, and is now called .NET 3.0. You can see here what
..NET 3.0 contains:

http://blogs.msdn.com/somasegar/archive/2006/06/09/624300.aspx

M> Does WinFX (.net framework 3.0) provide any benefits for asp.net
M> applications?
Nope.

m> I'm reading up on WinFX and it sounds like it's specifically geared
for Windows Vista.
Click to expand...

Mike: .NET 3.0 will be installed on Vista, and it is available as a
separate setup for WinXP (SP2) and Windows 2003 Server.
The power of WinFX is in WPF,WCF,WF,CardSpace. Probably you meant WPF.
WinFX provide XBAP to use XAML in browsers.
Click to expand...

Actually, XBAP are a part of WPF (which in turn is a part of WinFx, but
WinFx doesn't exist anymore, so...)
The real shortcoming of XBAP is that client need to have .NET 3.0 on his
machine.
To avoid this MS is working on WPF/E ("WPF everywhere" with
cross-platform-browsers fearures), but this is too young product, no CTP
is even available
Click to expand...

WPF/E CTP will be available before the end of 2006 according to
Microsoft. The GoLive version should be ready at Mix07 in May 07.

Note however that WPF/E will not be a replacement for WPF. The
application model is totally different. WPF/E will run in plugins
embedded in a HTML framework.
M> If I want to upgrade my
M> asp.net apps from framework 1.1 should I migrate to 2.0 or 3.0?

To 2.0 (.NET 3.0 redistributive is just 2.0 + WinFX Services)
Click to expand...

HTH,
Laurent
 
Does WinFX (.net framework 3.0) provide any benefits for asp.net
applications?
Click to expand...

None whatever in its current form...
I'm reading up on WinFX and it sounds like it's specifically
geared for Windows Vista.
Click to expand...

Not exclusively.
If I want to upgrade my asp.net apps from
framework 1.1 should I migrate to 2.0 or 3.0?
Click to expand...

To 2. v3.0 is a *really* confusingly named product, as it's not really
version 3 of the Framework at all.
 
Hello Laurent,
LB> It's not totally correct.
LB> WinFX was a code name, and is now called .NET 3.0. You can see here
LB> what .NET 3.0 contains:

Yep, and this is confused for everybody, by "what's new in .NET 3.0 framework?!"
There is nothing new in FW, there is new in additional technologies as WPF,
WCF, WF and WCS
as mentioned in the article your pointed

LB> Mike: .NET 3.0 will be installed on Vista, and it is available as a
LB> separate setup for WinXP (SP2) and Windows 2003 Server.

Yep, which only add new .NET 3.0 features, not changing already installed
..NET 2.0

LB> WPF/E CTP will be available before the end of 2006 according to
LB> Microsoft. The GoLive version should be ready at Mix07 in May 07.

Yep, and we can end up with the same stuff as was on the Mix'06 "WPF/E CTP
on fall" ;)

LB> Note however that WPF/E will not be a replacement for WPF.

It is, but in gives the real live of XAML, because in the current situation
years are required to make WPF popular.

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
 
Hi Michael,

Michael said:
LB> WPF/E CTP will be available before the end of 2006 according to
LB> Microsoft. The GoLive version should be ready at Mix07 in May 07.

Yep, and we can end up with the same stuff as was on the Mix'06 "WPF/E
CTP on fall" ;)
Click to expand...

Well, to be fair, they first said the CTP would be in July ;-)
LB> Note however that WPF/E will not be a replacement for WPF.
It is, but in gives the real live of XAML, because in the current
situation years are required to make WPF popular.
Click to expand...

Allow me to insist ;-) WPF/E is really not intended as a replacement for
WPF. It will be complementary to it, but the use cases are very different.

Greetings,
Laurent
 
Hello Laurent,

LB> Allow me to insist ;-) WPF/E is really not intended as a replacement
LB> for WPF. It will be complementary to it, but the use cases are very
LB> different.

I don't object. I'd like to point OP that if we want to use XAML for web
developments WPF/XBAP is not good approach.
WFP/E will do it better

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
 
M> Does WinFX (.net framework 3.0) provide any benefits for asp.net
M> applications?
Nope.
Click to expand...

You can't really dismiss WCF like that. You can host WCF servcies with your
ASP.NET applications.
Benefits include being able to host WS-* compliant Web Services from your
Web apps, while still providing
plain SOAP 1.2 services at the same time.

That's not exactly nothing... <s>

+++ Rick ---
 
Back
Top