Is .NET 3.0 RTM supposed to work on Windows 2003 Server?

Posted By: ehuna | Nov 8th, 2006 @ 8:33 PM
page 1 of 1
Comments: 4 | Views: 2347
#Nov 8th, 2006 @ 8:33 PM
ehuna
ehuna
Grand Poo-Bah

I downloaded .NET 3.0 RTM today and installed it on my Windows 2003 Server development server.

I tried double clicking on a XAML file and the system went nuts: the screen flashed, the mouse kept moving to the center and corners of the screen, etc... 

It looked like my machine was taken by the Indigo/Avalong ghost...  Finally I had to bring up task manager and kill IE.

I tried multiple times, with different XAML files.  I tried uninstalling and re-installing, downloading the fast installer and the full re-distributable (50 MB).  No luck - WPF just doesn't seem to work.

I've been using the same sample XAML files on Vista Beta2 then RC1.  I also used it with .NET RC1 on Windows XP SP2 without problems.

I never installed a beta version of WinFX/.NET 3.0 on this machine and waited until the RTM.

Is .NET 3.0 supposed to work on Windows 2003 Server or is this a bug in the installer that it allowed me to install it at all?

#Nov 9th, 2006 @ 7:26 AM
ZippyV
ZippyV
Fired Up

Have you tried to update your graphics card drivers? Which graphics card do you have?

#Nov 9th, 2006 @ 12:24 PM
Rob Relyea
Rob Relyea
Yes, .Net 3.0 RTM and WPF is supported on Windows 2003 Server.

What happens when you navigate to a xaml file in IE is that it loads PresentationHost.exe (which is a doc object that can live in a frame/iframe or at the top level of the browser).

The registered "player" for a loose xaml file is actually a XBAP...XamlViewer.xbap or the like...

To Fix
I would start with a very simple xaml file and see how that goes.
It may be a problem with the display adapter, but I would imagine that would only show up with a very complex page...but who knows.

The WPF forums would be a great place to go ask this question.

Please try:
1) a very simple xaml file
2) a wpf application - perhaps charles petzold's xamlcruncher
3) a wpf xbap - perhaps lee brimelow's examples
4) to ensure your video driver is up to date...

Would love to see the results of 1-3 before and after #4.

The WPF forum is here.
 
Thanks,
Rob Relyea
Program Manager, WPF Team
http://rrelyea.spaces.live.com
#Nov 9th, 2006 @ 12:27 PM
ehuna
ehuna
Grand Poo-Bah

I have an ATI Radeon X600:

  http://ati.amd.com/products/RadeonX600/index.html

When WPF started freaking out I uninstalled .NET 3.0 and downloaded the latest drivers from:

  http://ati.amd.com/support/drivers/xp/radeonx-xp.html

Notice that ATI does not have drivers specifically for Windows 2003 Server, but the Windows XP drivers work.

For reference, I tested DirectX.  I ran DXDIAG and there are no problems reported; I also see:

- DirectDraw Acceleration: Enabled
- Direct3D Acceleration: Enabled
- AGP Texture Acceleration: Enabled

All DirectDraw and Direct3D tests worked fine.

I also ran Google Earth and the new Microsoft Virtual Earth and all of the amazing 3D stuff works great.

Am I missing something?

page 1 of 1
Comments: 4 | Views: 2347
Microsoft Communities