Bognar posted:

This is kind of lovely since it's dodging your question entirely, but my recommendation is to avoid web services if you're just starting out with C#. They are basically legacy now and there's no real reason to start a new project with one these days. If you're trying to make something web accessible, then I'd recommend looking into ASP.NET MVC and Web API. The tutorials over at http://www.asp.net/web-api are decent enough to get started.

Bognar posted:

This is kind of lovely since it's dodging your question entirely, but my recommendation is to avoid web services if you're just starting out with C#. They are basically legacy now and there's no real reason to start a new project with one these days. If you're trying to make something web accessible, then I'd recommend looking into ASP.NET MVC and Web API. The tutorials over at http://www.asp.net/web-api are decent enough to get started.

GrumpyDoctor posted:

code:

double[] x = { building.geoProperties.CoreArea + building.geoProperties.PerimeterArea };
Expression has been evaluated and has no value
res.Data["Total Area"] = new UmiDataSeries { Data = x };
{Mit.Umi.Core.UmiDataSeries}
    Data: {double[1]}
    Name: null
    Resolution: null
    Units: null
res.Data["Total Area"] = new UmiDataSeries { Data = { building.geoProperties.CoreArea + building.geoProperties.PerimeterArea } };
[don't wanna break the tables] threw an exception of type 'System.NullReferenceException'

what

This is not just happening in the Immediate window - the exception is thrown by my code. Seriously, what the hell is this?

edit: I made a simpler case

Munkeymon posted:

So it works about as well as the 'keep me logged in' check box or basically Microsoft's web login system in general?

Ithaqua posted:

Works On My Machine

crashdome posted:

Ok I see you are logging in from a new device. We're going to text you a code or maybe an email. We can wait while you run to another device to check that code.... I hope you don't have alzheimers!

OK you got the code and you managed to enter it correctly. Great! Please wait while we forget what page you were on and redirect you back to the beginning. We'll probably ask you to login again.

Che Delilas posted:

crashdome posted:

Ok I see you are logging in from a new device. We're going to text you a code or maybe an email. We can wait while you run to another device to check that code.... I hope you don't have alzheimers!

OK you got the code and you managed to enter it correctly. Great! Please wait while we forget what page you were on and redirect you back to the beginning. We'll probably ask you to login again.

Squall posted:

If you have two factor auth setup without a really quick and easy way to access the codes you need, you kind of deserve to be jerked around imo

GrumpyDoctor posted:

I'm having a weird AutoMapper problem. Mapper.AssertConfigurationIsValid() succeeds, but all my actual mappings are failing with "Missing type map configuration or unsupported mapping." As an example: I'm mapping a Source.GlazingMaterial to a Destination.GlazingMaterial, but the mapper, in a child mapping, then tries to map the source object itself to an Int32 field, which obviously fails. I don't know which one, because neither type even has any Int32 fields. Something like this is happening with every type - the mapper tries to map the source object itself to a field on the destination object (which may not even exist). Calling Mapper.Reset() before establishing my mappings doesn't fix the problem. Is there any way to ask AutoMapper wtf it thinks it's doing?

e: When the exception is thrown, AutoMapperMappingException.Context.MemberName is empty. That seems...wrong.

Destroyenator posted:

Wild guess, is the Mapper.AssertConfigurationIsValid in the same build mode (debug/release)? Anything funky with the models being in assemblies targeting different runtime versions from the call site/tests?

Destroyenator posted:

Weird. Any chance it's generating a parent class mapping that's getting selected so the child specific fields aren't recognised?

EssOEss posted:

Okay, I have managed to write down all my relevant learnings about NuGet packaging in the modern way. Phew, that was more effort than I expected!

• How to package a .NET Framework library?
  
• How to package a .NET library targeting the Universal Windows Platform?
  
• How to package a portable library targeting .NET Core?
  
• How to package a .NET library targeting .NET Framework and Universal Windows Platform and include platform-specific functionality?
  
• How to package a multi-architecture .NET library that targets the Universal Windows Platform?
  
• How to package a .NET library that targets the Universal Windows Platform and depends on Visual Studio extension SDKs?
  

Comments very welcome! Code is on GitHub.

Trying out this SO self-answered questions format. Yay, already one vote to close from some jerk who didn't even read my text!

Inverness posted:

Are SO self-answered questions even allowed?

quote:

Stack Exchange has always explicitly encouraged users to answer their own questions. If you have a question that you already know the answer to, and you would like to document that knowledge in public so that others (including yourself) can find it later, it's perfectly okay to ask and answer your own question on a Stack Exchange site.

Munkeymon posted:

Anyone else think it's be nice to have a "Only break on uncaught exceptions in files currently open in the editor" option? Getting sick of closing tabs I don't want open just because something I didn't break and can't fix is failing off in the corner over there.

Ithaqua posted:

Yeah, web services are double legacy. They were eclipsed by WCF services which were eclipsed by WebAPI.

Finster Dexter posted:

That depends on who you ask. The ongoing debate at my job here has been WCF vs. WebAPI, with pretty good arguments on either side. Basically, WCF still has a place where you can use NetTcpBinding or whatever. Honestly, it's moot as far as I'm concerned because I want exposure completely divorced from the service business logic, anyway, so that my WebAPI/WCF is just wrapped around a DLL.

Finster Dexter posted:

I've never seen that before.

What does your packages.config look like? Is Autofac.Mvc5 in there? (guess not if a solution wide search doesn't find it)

Is it in the packages directory for the solution?

Is your Nuget exe and tooling up to date for VS2012?

It sounds like something is cached or corrupted somewhere, though.

epalm posted:

I keep running into the same ASP problem.

Generally my ASP solutions are structured like this:

• FooAsp
  
• FooCore
  
• FooCore.Tests
  

FooCore is "The Application".

FooAsp is pretty thin, and depends on FooCore to get the real work done. If I wanted to, I could write other interfaces like FooConsole or FooWpf.

FooCore.Tests, as expected, depends on FooCore and runs my tests.

I want to take advantage of user management via the Identity framework, which does registration, login, password hashing, password resets, authorization via roles, authentication via cookies (mvc) and tokens (webapi), and more. I really, really don't want to write and maintain these things myself. However, the ApplicationUser class is sitting in a UserContext in FooAsp, and all my other entities are sitting in DataContext in FooCore.

Here's an example of the problem. Say I wanted to add a feature that sends users text messages based on events that occur in FooCore. I want to build a testable class in FooCore that interfaces with (for example) Twilio, with restrictions on how many messages per second it sends, logs who it has sent messages to, records failures, etc. FooCore doesn't know about FooAsp (ie doesn't know about ApplicationUser).

What I've done in the past is write my own User entity in FooCore that maps 1:1 with an ApplicationUser in FooAsp, but this is a pain to keep synchronized (and redundant to keep two user tables in literally the same database).

How can I deal with this properly?

epalm posted:

I keep running into the same ASP problem.

Generally my ASP solutions are structured like this:

• FooAsp
  
• FooCore
  
• FooCore.Tests
  

FooCore is "The Application".

FooAsp is pretty thin, and depends on FooCore to get the real work done. If I wanted to, I could write other interfaces like FooConsole or FooWpf.

FooCore.Tests, as expected, depends on FooCore and runs my tests.

I want to take advantage of user management via the Identity framework, which does registration, login, password hashing, password resets, authorization via roles, authentication via cookies (mvc) and tokens (webapi), and more. I really, really don't want to write and maintain these things myself. However, the ApplicationUser class is sitting in a UserContext in FooAsp, and all my other entities are sitting in DataContext in FooCore.

Here's an example of the problem. Say I wanted to add a feature that sends users text messages based on events that occur in FooCore. I want to build a testable class in FooCore that interfaces with (for example) Twilio, with restrictions on how many messages per second it sends, logs who it has sent messages to, records failures, etc. FooCore doesn't know about FooAsp (ie doesn't know about ApplicationUser).

What I've done in the past is write my own User entity in FooCore that maps 1:1 with an ApplicationUser in FooAsp, but this is a pain to keep synchronized (and redundant to keep two user tables in literally the same database).

How can I deal with this properly?