epalm posted:

This is how I do it. I have Services (what you just referred to as Managers) which represents The App (which is its own VS class lib) which sits in between the UI (an ASP.NET controller, a WPF viewmodel, etc) and a datastore (SQL Server, WhateverNoSql, InMemoryMock, etc). I end up with app.dll which contains all the services and business logic and has no references to anything but does define repository interfaces, data.dll has a reference to app.dll and implements the interfaces in whichever way it needs to (entity framework, for example), and at that point you can tack on an ASP/Console/WPF project which has a reference to app.dll (and probably to data.dll if you're doing IoC just to specify which datastore your app wants to use).

Dietrich posted:

I don't know. The Repository should know how to ferry data to and from a database, and that's pretty much it.

At the very least, you should put the new SKU calculation code into it's own class where you can mock the data coming from the database, then set up test cases where you pass it data that should lead to various scenarios and validate that the result is what you expect.

Che Delilas posted:

Right now the new Items are being created by the ASP.NET MVC model binder (i.e. behind the scenes when the user posts the form). Is it possible to modify or replace the model binder with something that could use an ItemFactory?

...

The factory sounds like the ticket, I'm just not sure how to work it into the MVC framework. If it's possible, I'm sure I can find out how.

Ithaqua posted:

I started playing with SignalR tonight, it's pretty neat. Any ideas on best practices for actually using it in conjunction with WebAPI? I have an idea for a goofy little game.

GrumpyDoctor posted:

I've got a WPF control with a bunch of buttons and a "description" label. I want the description text to be updated whenever a button is hovered (with an explanation of what the button does). What's the best way to do this? Some kind of trigger wizardry? Just saying "gently caress it" and writing two code-behind events for each button? Binding directly to IsMouseOver isn't possible, apparently.

GoodCleanFun posted:

I think you could do something similar to this attached behavior solution: http://znite.wordpress.com/2010/02/20/mvvm-mouseover-binding/.

GrumpyDoctor posted:

I've got a WPF control with a bunch of buttons and a "description" label. I want the description text to be updated whenever a button is hovered (with an explanation of what the button does). What's the best way to do this? Some kind of trigger wizardry? Just saying "gently caress it" and writing two code-behind events for each button? Binding directly to IsMouseOver isn't possible, apparently.

gariig posted:

The biggest problem I've ran into is VS2012 no longer support Visual Studio Setup Projects (vdproj). You need to use WIX. You can browse this StackOverflow thread for more info about it. Besides that there's always minor breaking changes but I've never ran into one.

quote:

InvalidOperationException: MapsetMapRowHex is not a collection
System.Xml.Serialization.TypeData.get_ListItemType ()
System.Xml.Serialization.XmlReflectionImporter.ImportListMapping (System.Xml.Serialization.TypeData typeData, System.Xml.Serialization.XmlRootAttribute root, System.String defaultNamespace, System.Xml.Serialization.XmlAttributes atts, Int32 nestingLevel)

Wheany posted:

I'm not sure if this is a .NET problem or a Unity problem, but I have this xml data:

XML code:

<?xml version="1.0" encoding="utf-8" ?>
<Mapset>
    <Map name="The First">
        <Row>
            <Hex height="4" connections="nw ne e"/>
            <Hex height="1" connections=""/>
        </Row>
        <Row>
            <Hex height="3" connections="nw ne se"/>
            <Hex height="2" connections="se sw e"/>
        </Row>
    </Map>
    <Map name="another Map">
        <Row>
            <Hex height="4" connections="nw ne e"/>
            <Hex height="1" connections=""/>
        </Row>
        <Row>
            <Hex height="3" connections="nw ne se"/>
            <Hex height="2" connections="se sw e"/>
        </Row>
        <Row>
            <Hex height="3.0" connections="nw ne se sw e w"/>
            <Hex height="2.0" connections="nw ne sw e w"/>
            <Hex height="1.0" connections="nw se sw e w"/>
            <Hex height="4.0" connections="ne se sw e"/>
            <Hex height="3.0" connections="nw ne se sw w"/>
            <Hex height="-1.0" connections="nw ne se sw e"/>
            <Hex height="3.0" connections="sw e"/>
            <Hex height="2.0" connections="se sw e w"/>
            <Hex height="3.0" connections="nw ne sw w"/>
            <Hex height="2.0" connections="w"/>
            <Hex height="3.0" connections=""/>
            <Hex height="2.0" connections="e w"/>
        </Row>
    </Map>
</Mapset>

It's supposed to describe hex-based maps in our game. I generated a schema using xsd.exe and then classes from the xsd. However, when I try to instantiate an XMLSerializer: XmlSerializer serializer = new XmlSerializer(typeof(Mapset)); I get an exception:

I omitted most of the stack trace because I don't think it's relevant.

wwb posted:

No idea about the xsd because I don't use that junk but the class to handle this is pretty easy -- trick is to us the [XmlElement] attribute on the array properties for the Maps under MapSet and the rows under the Map. I can work up a code example a bit later if that don't help.

wwb posted:

Yup, that is usually where I start too. Write class, write unit test to deserailize, play attribute voodoo until it works.

XSD is some old poo poo (like 2002, .NET 1.0 old).

You need something like

code:

public class MapSet

wwb posted:

Just glancing at it the generator seemed to think your maprowhex was a 2 dimensional array for some reason. It wasn't the bestest thing in it's day once the xml got non-trivial.

aBagorn posted:

This is a little more generalized than a specific .NET question, but since I'm using it in a .NET app I'll ask here.

Ok, let's say I have 3 List<Foo> that contain elements that could be common to all three, two, or none.

I want to create a 4th list that combines all the elements of the 3, but orders them so that Foos that appear in all of them get put first, then 2, then the unique ones. (think kind of like a search engine?)

What's the best approach to go about this?

GrumpyDoctor posted:

Here's how I'd do it:

C# code:

using System.Linq;

var result =
    lists
    .SelectMany(x => x) // Concatenate all lists
    .GroupBy(x => x) // Identify common groups, using default equality
    .OrderByDescending(group => group.Count()) // Sort by group size
    .SelectMany(group => group); // Flatten groups into single list

(I haven't tested this.)

Wheany posted:

Okay, is there something similar that people actually use in 2014? I just followed the instructions here http://elegantcode.com/2010/08/07/dont-parse-that-xml/ after having had good experiences with JAXB on Java side.

Ithaqua posted:

I went with this:
listOne.Concat(listTwo).Concat(listThree).GroupBy(l => l).Select(s => new { s.Key, Count = s.Count() }).OrderByDescending(o => o.Count);

Gul Banana posted:

DataContractSerializer

Gul Banana posted:

Yes, the newer tool is svcutil.exe. with the /dconly flag, it will generate classes from an xsd, hopefully with more success than xsd.exe had.

cletus42o posted:

Ithaqua posted:

VS2012 Express RTM? If so, install Update 4. I seem to recall some XAML issues got fixed between RTM and Update 4.

Or better yet, just install VS2013.

Opulent Ceremony posted:

TFS 2013 with Git question, if this is better off in the Source Control thread I can move it. I'm hoping for feedback on a good way to manage our projects. We hope to use project management features of TFS like bug-tracking and such.

We've got several different .NET solutions, and everyone has different ideas about how to organize this:

1) Single TFS project, single Git repo where each solution is in a different branch (really multiple branches per solution for development/production etc). Seems like switching between branches to get to a different solution would suck, because we couldn't work on more than one solution/branch without committing changes before the branch switch? Also seems to take a long time to switch between branches since it removes and adds a bunch of files each time.

2) Multiple TFS projects, one solution per project, one Git repo for that project, multiple branches to accommodate development/production etc. Will this make it harder to work with in-house libraries that are shared across solutions?

3) Single TFS project, multiple Git repos for the solutions?

None of us are terribly familiar with TFS and Git, so I'm hoping someone in here can offer some good pros and cons, or to point out obviously good/bad ideas.