Knyteguy posted:

No luck unfortunately. Thanks though.

I feel like Windows 8.1 Phone development is still in beta stages or something. Not a whole lot of helpful debugging information.

ljw1004 posted:

Sorry, that was partly my doing. The reason for not doing them in VB is:

* We foresee something nicer coming along, e.g. https://roslyn.codeplex.com/discussions/560339
In C# the primary constructor syntax will already be taken, so C# would have to express "plain old data" objects with some kind of other syntax e.g. "record class Point(int x, int y);" and there'll be several similar kinds of things. In VB, if we don't do primary constructors now, then we'll leave the syntax free for the something nicer in the future.

quote:

And how to convert it from (presumably a string) to a double?

A Tartan Tory posted:

A Tartan Tory posted:

Dumlefudge posted:

The conversion can be done using Double.Parse or Double.TryParse e.g.

Ithaqua posted:

Have you read this link in the OP?

http://msdn.microsoft.com/en-us/magazine/dd419663.aspx

Have you implemented INotifyPropertyChanged on your viewmodel? You're not giving a lot of information to help point you in the right direction. Do you have any code you can post?

Che Delilas posted:

How much do you want to learn? I ask because what you're talking about doing is more or less the essential foundation of good WPF coding. If this is just a one-off project and all you care about is getting it to work, there are quick and dirty ways. If you actually want to learn WPF and how to do things the "right" way, you're going to need to learn and understand the design pattern called MVVM, which is not an easy thing to wrap your mind around if you haven't seen it or something like it before.

Edit: Ithaqua may organize a lynch mob for me if I teach you the quick and dirty way

Gul Banana posted:

https://github.com/gulbanana/wpfbinding
here's a demo of something similar to what you describe - using data-binding from a textbox to trigger a calculation in code.

i've implemented it in two different ways
1) using an ICommand binding on a Button to explicitly run the calculating code
2) using a property setter to modify another property, which notifies the UI (using INotifyPropertyChanged, as Ithaqua says)

mvvm really doesn't involve a lot of work - check it out and you might be pleasantly surprised

Che Delilas posted:

It could be a Visual Studio bug - I hate to suggest this because it sounds so Tier 1 Helpdesk, but have you tried Cleaning your solution, exiting Visual Studio, then restarting it and Rebuilding your solution?

I've had VS gently caress up in similar ways in the past, being unable to find classes that I knew were there and the like, specifically with XAML. Restarting the IDE tended to fix it.

Knyteguy posted:

I think this the right place. I'm having some trouble with XAML since I'm completely new to it. Specifically I'm having trouble with the data binding.

ljw1004 posted:

Why do people use json for their sample data? Beats me.

ljw1004 posted:

I think people make data-binding more difficult than it need be. Here's how I'd write your code...

ljw1004 posted:

C# code:

public class SampleMarginData : ObservableCollection<MarginModel>

Ithaqua posted:

A note: It's generally a bad practice to subclass collections.
http://stackoverflow.com/questions/21692193/why-not-inherit-from-listt

Factor Mystic posted:

Aside from the non-generic subclass, I'll give the benefit of the doubt to anyone subclassing ObservableCollections since the base class is so irritating. Who's using OC<T> and NOT subclassing it?

Knyteguy posted:

Anyone have an opinion on the Telerik tools, http://www.telerik.com/windows-universal-ui, or telerik appbuilder? As a .NET developer who uses their tools - have you found them to be worth the cost?

NoDamage posted:

Progress on our Windows version is going smoothly, so now I am having to consider some aspects of app distribution that were previously taken care of with the App Store model. Does anyone have experience/thoughts/advice on selling traditional (consumer) desktop Windows apps, particularly with regards to payment processing/licensing/automatic updating?

For payments I was thinking of going with FastSpring, licensing I have no idea but I'm not particularly inclined to roll my own, and for automatic updating I was hoping something like Sparkle existed for Windows but it doesn't seem like there is anything robust/currently maintained.

NickFendon posted:

We use LimeLM for licensing. They aren't a big company but the product works well and they've been on the ball with their support whenever we've needed it.

A lot of people would disagree with this, but I legitimately love ClickOnce for app deployment and automatic updating. I use it whenever I can. We've also used wyBuild on a few products - it works well but is a pain to script/automate.

NoDamage posted:

How long have you been using LimeLM? Have they been reliable? Their product looks pretty nice, but I'm always a bit wary about adding a third-party dependency, especially one that depends on someone else's servers for activation.

Doghouse posted:

I've been working with the TFS API in C# a bit recently, but now I'm trying to move an iteration node from one root node to another. You can easily do this in the web tfs interface, just by dragging and dropping. Is there a way to do it with C#?
I can get the root node objects and the child node objects but they don't seem to be able to do anything.

Gul Banana posted:

https://github.com/gulbanana/wpfbinding
here's a demo of something similar to what you describe - using data-binding from a textbox to trigger a calculation in code.

i've implemented it in two different ways
1) using an ICommand binding on a Button to explicitly run the calculating code
2) using a property setter to modify another property, which notifies the UI (using INotifyPropertyChanged, as Ithaqua says)

mvvm really doesn't involve a lot of work - check it out and you might be pleasantly surprised

Ithaqua posted:

You're misunderstanding how MVVM works, I think.

Your viewmodel represents the state of your view, and exposes properties (sometimes in the form of model objects, sometimes not) that are bound to the view.

You should have your button bound to an ICommand implementation in your viewmodel. When you click the button, it calls the method in your viewmodel. The viewmodel then does "stuff", and updates its properties (or model objects) based on the results of that stuff. Since you've bound properties to the view, the view will automatically update as your viewmodel and model changes.

GrumpyDoctor posted:

The whole process is made harder than it needs to be by the fact that WPF doesn't offer a good, concrete ICommand implementation out of the box, for some idiotic reason. Most people either use third-party frameworks or just roll the bits from them they need on their own, like the RelayCommand in this article. (RelayCommand is really tiny so it's not hard.)

The end product looks something like this:

C# code:

public class ViewModel : INotifyPropertyChanged
{
    public ICommand CalculateCommand { get; private set; }

    public ViewModel()
    {
        CalculateCommand = new RelayCommand(Calculate);
    }

    private void Calculate()
    {
        // Perform whatever calculation and property assignment is necessary.
        // Remember that you have access to all the data-bound properties you need to serve as calculation inputs.
    }

    // blah blah blah whatever else
}

A Tartan Tory posted:

Ok so, this is the viewmodel, it initiates itself whenever the button is pressed (how do I represent that in the XAML in view?) and all the inputted data is bound to the name I use in the xaml in view for that textbox it just needs to be assigned to a new variable within this method (how do I access it from the binding to do that then, it can't be within the model as given in the example?).

A Tartan Tory posted:

Ok so, this is the viewmodel, it initiates itself whenever the button is pressed (how do I represent that in the XAML in view?) and all the inputted data is bound to the name I use in the xaml in view for that textbox it just needs to be assigned to a new variable within this method (how do I access it from the binding to do that then, it can't be within the model as given in the example?).

GrumpyDoctor posted:

It doesn't need to be assigned anywhere new; presumably you've got some of these guys elsewhere in your viewmodel:

that you've databound to. The body of Calculate will then have access to this.Months and this.Years as calculation arguments, and this.Results to stuff the results in.

A Tartan Tory posted:

Oh, oh! I get it now! So whenever the view is updated by the user, the command updates the variables that are assigned in public in the ViewModel, so it can be used by the programming logic later on and then displayed as results when finished?

If I was to stuff multiple arrays into this.results though, would it still work if it was shown in view in the correct way?

A Tartan Tory posted:

The button push just tells it to get the Calculated Results? What I should be doing is telling the button to implement a command rather than to get existing results?

quote:

View passes information to viewmodel, viewmodel updates model, model updates viewmodel, viewmodel updates view? Is that supposed to be how it works?

quote:

Ok so, this is the viewmodel, it initiates itself whenever the button is pressed (how do I represent that in the XAML in view?) and all the inputted data is bound to the name I use in the xaml in view for that textbox it just needs to be assigned to a new variable within this method (how do I access it from the binding to do that then, it can't be within the model as given in the example?).

A Tartan Tory posted:

Right, so if I understand this correctly now, the only way ViewModel and View interact is through data binding for both getting the user inputted variables and sending the results back. The viewmodel has the programming logic and the model has the business logic behind it (ViewModel and Model are linked).

So to do what I need to do, I need to get my inputs from View to Viewmodel using data binding, run it through the programming logic in there, then spit it back out through data binding again.

A Tartan Tory posted:

So to do what I need to do, I need to get my inputs from View to Viewmodel using data binding, run it through the programming logic in there, then spit it back out through data binding again.

Gul Banana posted:

It's not magic, mind you.