|
Let me balance out the 1 that somebody has voted you with a 5.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
How do you generate classes from XAML in Visual Studio 2008?
I have a Silverlight project. The XAML has been written in Expression Blend. I am told that I can use Visual Studio to use the grid classes in the Page.xaml file (the whole solution is loaded into Visual Studio) to generate the .CS (C#) files in Visual Studio 2008 that correspond to the several <grid> classes in the XAML. How is this done? Is there a wizard somewhere that will do this for me? Do I have to do this by hand?
When I open the Page.Xaml file and click on the name of the <grid> node, (x:Name) and select, to view code, it takes me to a file without much meat on it:
public partial class Page : UserControl
{
public Page()
{
InitializeComponent();
}
}
Since each <grid> contains a lot of components, I was expecting more.
Am I supposed to expand on this class by hand and code all the methods for this "Page" class? Is there a tutorial that shows how to do this?
There are so many videos to look at http://expression.microsoft.com/en-us/cc197141.aspx but they all seem to be focused on Expression Blend rather than how to use the XAML from Expression Blend to make Classes or to build on these classes.
On the other hand, are their example or sample code of how to take a "public partial class Page : UserControl" in C# and build from it?
|
|
|
|
|
Xarzu wrote: Am I supposed to expand on this class by hand and code all the methods for this "Page" class? Is there a tutorial that shows how to do this?
Yes. The Xaml represents the UI design - but if you need to add your own business logic, you still need to write code.
The code you need to write depends on what you intend to do - but do a search on the internet and you will find quite a few samples.
|
|
|
|
|
You should give your components names (x:Name=...). At that point you can refer to them in your cs code. So, if you did this in your XAML:
<Grid x:Name="LayoutRoot" />
You could do this in your cs code:
this.LayoutRoot.Background = new SolidColorBursh(Colors.Red);
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
When you design something in XAML, no real code gets added into this Page class until compile time. Then a hidden .g.cs file is created which adds the definitions of the components in.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
Hi all,
I found several links for this but no definitive answer. Could you please tell me the reason
|
|
|
|
|
AFAIK, wsHttpBinding is not supported in silverlight - Silverlight supports the WS basic profile, which uses basicHttpBinding and not wsHttpBinding.
|
|
|
|
|
Something happened in the last week that prevents VS2008 from being able to debug ANY Silverlight apps (non-Silverlight can still be debugged normally). Last weekend, it worked fine. I did notice there was an update to .Net 3.5 and it also pushed the .Net4 Client Profile in the latest rounds of Microsoft updates (last week) but I don't know if this is the cause.
SOLUTION ============================
I found out what was wrong - I had an out-of-date pdb file in a 3rd party folder. When I replaced it with the appropriate file, everything was fine.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
modified on Monday, June 28, 2010 7:42 AM
|
|
|
|
|
Maybe this can help -
Goto the web project of your SL solution, right click on it and view the project properties.
Goto the Web option and ensure the Silverlight debugger is checked.
|
|
|
|
|
Hi, this thing is killing me..
I have object drag of type Field and I would like to bind it to a productsDataGrid's property Drag in XAML. In codebehind it all works well :
public class Field : INotifyPropertyChanged
{
...
public string Value
...
}
public partial class MainPage : UserControl
{
public Field drag;
public MainPage()
{
drag = new Field();
drag.Value = "true";
productsDataGrid.Drag = drag;
but in XAML it's not.
<cont:DragGrid Name="productsDataGrid" Drag="{Binding drag, Path=Value}"/>
How to set this binding correct ?
|
|
|
|
|
Make Value a property, not a field.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
Hi, sorry I didn't paste complete code of Field class, but Value is already a property
public class Field : INotifyPropertyChanged
{
private string _value;
public string Value
{
get {return _value;}
set
{
_value = value;
NotifyPropertyChanged("Value");
}
Edit: I deleted my last message, because I thought I worked the solution, so the question is still unanswered.
modified on Saturday, June 26, 2010 9:50 AM
|
|
|
|
|
ekimpl wrote: <cont:draggrid name="productsDataGrid" drag="{Binding drag, Path=Value}">
I did not see you setting the Datacontext for the xaml anywhere.
What is it set to?
|
|
|
|
|
I set DataContext in LayoutRoot
<UserControl x:Class="MFP.MainPage" ..... >
<UserControl.Resources>
<my:MainPage x:Key="mainpage"/>
</UserControl.Resources>
<Canvas x:Name="LayoutRoot" DataContext="mainpage" ...
|
|
|
|
|
private string _value; <br />
public string Value <br />
{ <br />
get {return _value;<br />
} <br />
set <br />
{ <br />
_value = value; <br />
NotifyPropertyChanged("Value"); <br />
}<br />
Move the property code to mainpage and try....
|
|
|
|
|
But the Value property is inside of class Field, so I can't move it.
|
|
|
|
|
In order to use Value, the DataContext must be set to an instance of your Field class. That's the only way it can find it.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
I think I am missing something in XAML, because from .cs it all works ok. Let's forget about the Field class and stick to a simpler example like binding MyValue to a TextBlock.
public String MyValue { get; set; }<br />
<br />
public MainPage()<br />
{<br />
InitializeComponent();<br />
MyValue = "test text";<br />
txtTest.DataContext = MyValue;<br />
.....<br />
<br />
<TextBlock Grid.Row="1" Name="txtTest" Text="{Binding}"/>
Above code works fine, but when i try to set DataContext in XAML it fails.
<TextBlock Grid.Row="1" DataContext={Binding MyValue} Name="txtTest" Text="{Binding}"/>
Fail
<TextBlock Grid.Row="1" Name="txtTest" Text="{Binding MyValue}"/>
Fail
Maybe I should add something to resources ?
|
|
|
|
|
ekimpl wrote: Maybe I should add something to resources ?
No. Drop the DataContext from your XAML, and then add something like this in the code behind the view:
private Field _field;
private void SetContext()
{
_field = new Field();
DataContext = Field;
}Then call this method from immediately after the call to InitializeComponent();
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
Pete O'Hanlon wrote: No. Drop the DataContext from your XAML
He could alsways set the datacontext via the xaml.
However, here this solution is perfect.
|
|
|
|
|
Pete, I could use Your solution, but as I wrote, there is no problem when setting DataContext form .cs. I just wanted to find the reason why I could not bind my Properties in XAML.
And I found the reason, with Your (both Pete and Abhinav) clues. It was because my declaration of DataContext for LayoutRoot was wrong. I moved it from XAML to .cs
LayoutRoot.DataContext = this;
so now it points to my MainPage class, and now, I can bind local properties with no need to set the context for each control in XAML
public Field Val { get; set; }
<TextBlock Grid.Row="1" Name="txtTest" Text="{Binding Val.Value}"/>
So, thanks for Your help guys, I think the problem is solved.
|
|
|
|
|
ekimpl wrote: So, thanks for Your help guys
You are welcome.
|
|
|
|
|
Hi Experts,
I have a user control. I am dynamically adding controls to this user control using Children.Add. I want to change their location on some event in code. Like we can do in winform using Location. Is there anything similar to this?
Please help!
Thanks in advance!
Regards,
Samar
|
|
|
|
|
You could always set the Margin of the control to move/size it. Without knowing what exactly you are trying to achieve, it's hard to add any more detail.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
Hi,
I think i was a little too generic in explaining my problem. I will give my current scenario.
I am trying to build an MDI in WPF. As you know there is no concept of MDI in WPF but i got a simulated MDI code from codeplex. The link for the same is given here. Now i want to tile the child controls in the mdi either horizontally, vertically or cascade in the way similar to windows MDI like this.LayoutMdi(MdiLayout.TileHorizontal);.
Please help!
Thanks in advance.
Regards,
Samar
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
