This release of the WinFX RC and Windows SDK works with Windows Vista
(February CTP), Windows XP SP2 and Windows Server 2003 SP1.
On the Windows SDK download page, it only mentions Vista support in the
title:
http://www.microsoft.com/downloads/details.aspx?FamilyId=9BE1FC7F-0542-47F1-88DD-61E3EF88C402&displaylang=en.
I'd like to build some of the Avalon UI features onto existing .NET 2.0
apps running on WinXP. Is that possible? Besides .NET 2.0, what will
a client machine need?
Thanks,
Brett
it works well on the XP.
besides .net u need WinFX as well :)
>> From this page:
>>
BR> http://msdn.microsoft.com/windowsvista/downloads/getthebeta/default.
BR> aspx, it seems I can develop with Avalon (WinFX) using VS.NET 2005,
BR> WinFX SDK and Windows SDK on WinXP. Specifically it says:
BR>
BR> This release of the WinFX RC and Windows SDK works with Windows
BR> Vista (February CTP), Windows XP SP2 and Windows Server 2003 SP1.
BR>
BR> On the Windows SDK download page, it only mentions Vista support in
BR> the
BR>
BR> title:
BR>
BR> http://www.microsoft.com/downloads/details.aspx?FamilyId=9BE1FC7F-05
BR> 42-47F1-88DD-61E3EF88C402&displaylang=en.
BR>
BR> I'd like to build some of the Avalon UI features onto existing .NET
BR> 2.0 apps running on WinXP. Is that possible? Besides .NET 2.0,
BR> what will a client machine need?
BR>
BR> Thanks,
BR> Brett
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour
"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
Brett
WinFX Runtime http://www.microsoft.com/downloads/details.aspx?FamilyId=61DD9CA7-1668-42E4-BD37-03716DD83E53&displaylang=en
But check the last version
BR> Thanks Michael but that doesn't really answer my question. I know
BR> WinFX isn't needed but is the 1G Windows SDK downloaded needed?
BR> What is needed for the client?
BR>
BR> Brett
BR>
No, you *do* need WinFX to use Avalon - Avalon is part of WinFX.
However, you will only need the runtime, not the SDK. See
http://www.microsoft.com/downloads/details.aspx?FamilyId=F51C4D96-9AEA-
474F-86D3-172BFA3B828B&displaylang=en
for the download of the February CTP. Note that none of this is
shipping yet, so actual sizes etc will no doubt change.
--
Jon Skeet - <sk...@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
http://schemas.microsoft.com/winfx/xaml/2005' is not a recognized
namespace. Line 21, position
5. C:\WPF\Project\MainPage.xaml 21 5 SdkViewer
I'm also missing these DLLs:
System.Security.Authorization
System.Transaction.Indigo
Any ideas?
Thanks,
Brett
Idea is that you call some SDK libs, that leeds from the name of what u run.
And u need SDK.
Look at the gotdotnet.com for the Avalon ClickOnce samples - they only require
WinFX Runtime, not SDK.
BTW, there are microsoft.public.windows.developer.winfx.* groups where WinFX
guys give u more detailed description
why CTF version could not work properly and how to fix it.
I've been playing with winFX for a half of year and could say it's a tricky
way to start working it normaly.
The best idea is to have the single machine where you can experiment and
reinstall the system in case smth go down.
BR> I've already downloaded an installed WinFX from the above link. I'm
BR> trying to run the SdkViewer stand alone app and compile the project:
BR> http://msdn.microsoft.com/winfx/learning/presentation/sdk_viewer/def
BR> ault.aspx.
BR> Neither work. The project throws this error multiple times:
BR> http://schemas.microsoft.com/winfx/xaml/2005' is not a recognized
BR> namespace. Line 21, position
BR> 5. C:\WPF\Project\MainPage.xaml 21 5 SdkViewer
BR> I'm also missing these DLLs:
BR> System.Security.Authorization
BR> System.Transaction.Indigo
BR> Any ideas?
You need to set a reference to the WinFx assemblies. The latest CTP build
have them installed in:
?:\Program Files\Reference Assemblies\Microsoft\WinFX\v3.0\WindowsBase.dll
where ? is your system drive letter.
csc /r:"C:\Program Files\Reference
Assemblies\Microsoft\WinFX\v3.0\WindowsBase.dll" /r:....
Note that to take full advantage of WinFx development you will need to
download the SDK. VS2005 user will need the "Orcas" extentions installed.
Willy.
Thanks,
Brett
Thanks,
Brett
"Brett Romero" <acc...@cygen.com> wrote in message
news:1145218004....@u72g2000cwu.googlegroups.com...
http://channel9.msdn.com/Search/SearchResults.aspx?q=avalon&f=MzE=&u=MA==
BR> Do you have a URL to the Avalon ClickOnce samples? I can't find
BR> anything on that at gotdotnet.com.
BR>
BR> Thanks,
BR> Brett
WeatherForecaster: http://channel9.msdn.com/ShowPost.aspx?PostID=117863
Chess: http://channel9.msdn.com/ShowPost.aspx?PostID=86834
Clock: http://channel9.msdn.com/ShowPost.aspx?PostID=73368
I also compiled Chess and DesktopClock. I get this error:
'http://schemas.microsoft.com/winfx/xaml/2005' is not a recognized
namespace.
Which is part of the original post from compiling the
SDKViewerApplication. Seems there is some component or framework piece
these all need that I'm missing. This is what I have installed:
http://www.microsoft.com/downloads/details.aspx?FamilyId=F51C4D96-9AEA-474F-86D3-172BFA3B828B&displaylang=en,
which is titled 'Microsoft Pre-Release Software WinFX Runtime
Components - February Community Technology Preview (CTP)'
Any ideas what is going on?
Brett
It fixes the errors about references. Hope this helps.
Sameer
Chess app:
The 'http://schemas.microsoft.com/winfx/2006/xaml' namespace attribute
named 'CodeBehind' is not recognized.
Desktop Clock app:
Unrecognized property 'StartingUp' found in XML namespace
'http://schemas.microsoft.com/winfx/2006/xaml/presentation'. Note that
property names are case sensitive and attached dependency properties
must have an associated static setter method.
Just wondering if all of those people on the Channel9 forum had to go
through this. They seem to have had no issues.
Brett
Willy.
Brett