 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / New Users / March 2007Test a XAML in XP, service pack 2
Hi folks, I have installed .net 3.0 framework sucessfully in a machine with XP, service pack 2. In the window explorer, I clicked a simplest XAML file, I got error message, "...msctf.dll not found...." . Then, I copied it into the local web server, and I tried to access it, I got the similar error. The xaml is as below: <Page xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" WindowTitle="Xaml Page"><StackPanel> <Button HorizontalAlignment="Center" Margin="24">Hello, XAML!</Button> </StackPanel></Page> Please advise, Thanks. Peter Hi Peter, > Hi folks, I have installed .net 3.0 framework sucessfully in a machine with > XP, service pack 2. In the window explorer, I clicked a simplest XAML [quoted text clipped - 6 lines] > XAML!</Button> </StackPanel></Page> > Please advise, Thanks. Peter We're seeing this same problem on some of our development machines. Are you by chance working with so called CAT PCs? Greetings, Laurent  SignatureLaurent Bugnion [MVP ASP.NET] Software engineering, Blog: http://www.galasoft-LB.ch PhotoAlbum: http://www.galasoft-LB.ch/pictures Support children in Calcutta: http://www.calcutta-espoir.ch Hi Laurent, Thanks for your reply. Then, I know that I might not process wrong. I asked around my colleagues, and nobody can tell my machine is Cat PC or not. Thanks again. Peter > Hi Peter, > [quoted text clipped - 14 lines] > Greetings, > Laurent Hi, > Hi Laurent, > Thanks for your reply. Then, I know that I might not process wrong. > I asked around my colleagues, and nobody can tell my machine is Cat PC or > not. Thanks again. > Peter CAT PCs are used at Siemens, so I take it that you're not working for them, are you? Sorry, I should have precised this earlier. I am trying to find out what faulty PCs have in common, in order to try and solve the problem. We have our IT looking into it too, I'll try and follow up here if we find the problem. Greetings, Laurent SignatureLaurent Bugnion [MVP ASP.NET] Software engineering, Blog: http://www.galasoft-LB.ch PhotoAlbum: http://www.galasoft-LB.ch/pictures Support children in Calcutta: http://www.calcutta-espoir.ch Do you have the Window declared outside the page? I put this into XAML in a WPF project, and it works. Here's my XAML: <Window x:Class="TestXaml.Window1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" Title="TestXaml" Height="300" Width="300" > <Page WindowTitle ="Xaml Page"> <StackPanel> <Button HorizontalAlignment="Center" Margin="24">Hello,Xaml!</Button> </StackPanel> </Page> </Window> I've actually not used the Page object, but I'm only halfway through the gigantic WPF book. Robin S. ------------------------- > Hi Peter, > [quoted text clipped - 14 lines] > Greetings, > Laurent I would also point out that when I save this as a .xaml file and double-click on it in Windows Explorer, it tries to open it in Internet Explorer, and doesn't work. There are a ton of messages about permissions. Is this the problem you are experiencing? Robin S. ---------------------------------- > Do you have the Window declared outside the page? I put this into XAML in > a WPF project, and it works. Here's my XAML: [quoted text clipped - 34 lines] >> Greetings, >> Laurent Hi Robin, I copied and pasted your code, and double-click the XAML file, it idid not work on my machine with window XP, Service pack 2.0, a typical Dell machine. Even my machine experienced one automatic window update before I tested your code. I tried out WPF examples smoothly at home in Vista . It is kind of strange. Thanks. Peter March 6, 2007 > I would also point out that when I save this as a .xaml file and > double-click on it in Windows Explorer, it tries to open it in Internet [quoted text clipped - 41 lines] > >> Greetings, > >> Laurent I can't double-click on the xaml file either. I didn't know you could do that in Vista. I stuck it in a WPF project in Visual Studio to try it out. Odd. Robin S. --------------------------------- > Hi Robin, > I copied and pasted your code, and double-click the XAML file, it [quoted text clipped - 60 lines] >> >> Greetings, >> >> Laurent Hi Robin, Thanks for your response for clarity. When I tried out most of the WPF examples, I created a proj file to build it by msbuild, defining the source as *.cs. Then I double-click the exe file to see the application product first. Then, I walked through the code. Finally, I did the reading. This is my personal learning style. I have not installed the SDK at work yet. I copied a SayHello.exe file from home to my computer at work, I double-clicked it, it works. It is the environment with only .net 3.0 runtime installed. Now I feel much more comfortable that I am potentially able to use WPF technology for the client mahcines with XP. Thanks again. PeterK March 7, 2007 > I can't double-click on the xaml file either. I didn't know you could do > that in Vista. I stuck it in a WPF project in Visual Studio to try it out. [quoted text clipped - 66 lines] > >> >> Greetings, > >> >> Laurent So here's what I found out about this. You can double-click on a XAML file in Vista, and it will run it. However, if you double-click on a XAML file on a Windows XP machine, it will not run it. In order to run it on an XP machine, you have to compile and build it first, which is what Visual Studio does. That's the official word. I read that in the first chapter of the XAML reference put out by O'Reilly in 2006. So apparently there's something in Vista that's not in XP. You can get something to compile and build XAML w/o Visual Studio, but it's not as simple? Also, Petzold (who wrote the definitive book on WPF) has a XAML Cruncher I think on his website that you can use to write and run XAML. So that's the story on that. HTH. Robin S. ----------------------------------- > Hi Robin, > Thanks for your response for clarity. When I tried out most of the [quoted text clipped - 95 lines] >> >> >> Greetings, >> >> >> Laurent Hi Robin, Thanks for the idea of Xaml Cruncher. For security reason, I could not download a executable file directly in my office. Instead, I found the XamlPad is one of the tool for .net 3.0 SDK in March 2007 CTP. It seems that it serves the same purpose. Now I can render a standalone Xaml file in a machine with XP. Thanks again. peterk 3/16/2007 > So here's what I found out about this. You can double-click on a XAML file > in Vista, and it will run it. However, if you double-click on a XAML file [quoted text clipped - 114 lines] > >> >> >> Greetings, > >> >> >> Laurent You're welcome. By the way, I have found that some xaml files will open in my WinXP, and some won't. Someone I know who teaches a WPF class said xaml files will open on one of his computers, but not the other one, both running WinXP, and we're talking about trying to open the same xaml file on both computers. So there's something wonky going on there. BTW, the XAML cruncher's code is in the code download for Charles Petzold's book, on his website. I installed it originally from his website, but having no exe, couldn't create a OpenWith entry, then realized I had the darn code. It's a little more elegant than XamlPad, with a few more features. And it's a WPF application itself. Interesting. Good luck. Robin S. -------------------------------------------- > Hi Robin, > Thanks for the idea of Xaml Cruncher. For security reason, I [quoted text clipped - 143 lines] >> >> >> >> Greetings, >> >> >> >> Laurent Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.