Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Anthony Sneed
    @tonysneed
    This package has not been indexed yet. It will appear in search results and will be available for install/restore after indexing is completed.
    Lubos Hladik
    @luboshl
    This package has not been indexed yet. It will appear in search results and will be available for install/restore after indexing is completed.
    :)
    Anthony Sneed
    @tonysneed
    You should still be able to install it though
    install-package from the Package console in VS 2015
    Lubos Hladik
    @luboshl
    installed :+1:
    Anthony Sneed
    @tonysneed
    Better if I had first tested the packages locally. :) https://blogs.endjin.com/2014/07/how-to-test-nuget-packages-locally/
    Lubos Hladik
    @luboshl
    Never mind, I've tested it :)
    Anthony Sneed
    @tonysneed
    Yes, but best to test before publishing it. 😱
    Lubos Hladik
    @luboshl
    Yes, it's true :)
    Anthony Sneed
    @tonysneed
    Didn’t know anyone was going to get it the first day 😇
    🙄
    Lubos Hladik
    @luboshl
    CommonInstanceFactory.Adapter.Unity - 40 downloads
    CommonInstanceFactory.Extensions.Wcf.Unity - 56 downloads
    Wow! :)
    Anthony Sneed
    @tonysneed
    Looks like there is interest after all! Lots of WCF still out there; glad to fill a need
    Lubos Hladik
    @luboshl
    Yes, WCF is not dead :)))))
    Anthony Sneed
    @tonysneed
    No, it does live
    That is why TE includes support for WCF
    Anthony Sneed
    @tonysneed
    Just because people should not use WCF for building new web services, does not mean they will not. ;)
    Lubos Hladik
    @luboshl
    Anthony Sneed
    @tonysneed
    I'm grateful for the comments on this post, because I could then provide more info in my responses to those comments, and hopefully clarify what I meant
    For example, I never said
    that one should never use WCF
    It is still appropriate for certain scenarios
    And there is the need to integrate with legacy systems
    That are based on SOAP
    Lubos Hladik
    @luboshl

    Yes, I know. It was really only paraphrase to your title with "WCF id dead...", so I wrote "WCF is not dead" :) And it's true that sometimes it happens that comments are more interesting finally. If people don't agree, the writer answers and exaplains and then it goes deep into problem.

    I understand the title of your post to be a little provocative, isn't it? :)

    Anthony Sneed
    @tonysneed
    Exactly! Just to get the discussion started. :)
    Lubos Hladik
    @luboshl
    Tony, have you found my email, or it has fallen into spam?
    Anthony Sneed
    @tonysneed
    Ah yes, it got buried in my Inbox. Thanks again for your contribution! I'll be sure to reply .. Had a busy week, so I'm glad you reminded me to check. :)
    Lubos Hladik
    @luboshl
    No problem, I was only worried I got into spam :-)
    Anthony Sneed
    @tonysneed
    Celebrating Valentine today and getting my wife something. ;))
    Marc
    @MarcDrexler
    Hi Tony
    I found the next one
    Marc
    @MarcDrexler
    And I also found this chat room :smile:
    Anthony Sneed
    @tonysneed
    Cool!!
    Marc
    @MarcDrexler
    I still feel that one of the most difficult things in development is, how you name something... now I don't know how to name my branch :) So you want me to create a local branch where I should add my tests? And for this branch only I should create a pull request? Is that correct? Or what is the best practice in here so you don't have to change things manually afterwards again.
    Anthony Sneed
    @tonysneed
    Don’t know why I didn’t see this until now. But check out this page, the section on GitHub, and the link on creating pull requests: http://trackableentities.github.io/6-contributing.html
    @MarcDrexler The branch name can be anything you want, but probably a short word or phrase that describes it, such as change-tracking-tests
    Shimmy
    @weitzhandler
    Is TrackableEntities still maintained? Any future plans? 2017?
    Anthony Sneed
    @tonysneed
    Hi Shimmy, We can chat here about Issue #161 .. I'd like to understand your scenario better.
    Anthony Sneed
    @tonysneed
    From what I gather, you want to be able to call NotifyPropertyChanged from a Xamarin Forms client without having to pass a lambda expression, using the CallerMemberName attribute. Is that right?
    Shimmy
    @weitzhandler
    @tonysneed
    That's right. I'm migrating my existing model (shared code between ASP.NET Core WebAPI and Xamarin PCL) to use TrackableEntities.
    It's a model of a about few hundred entities and properties. Since the API semantics has no use of INPC, I decided to use Fody/PropertyChanged to auto implement all properties. If the class is a subclass (i.e. not directly inheriting from INPC interface, it can raise the error directly, thus it must have a propertyName: string parameter notify method. After my ugly workaround things work well with Fody.
    Besides it would be a good thing to allow users freedom in how to notify the property change, especially given this is the base class for all client entities. Especially now that the nameof and CallerMemberNameAttribute were introduced.
    Have you seen my PR (#162)?
    Anthony Sneed
    @tonysneed
    I am looking at this today
    Anthony Sneed
    @tonysneed
    Just submitted PR #164 to address this issue. Check it out and try the prerelease NuGet Client and Common packages.
    Olivier MATROT
    @omatrot
    Hello everyone
    I'd like to hear about using trackable-entities-js with a JSON serialized object graph comming from the server written in c#. Is that possible ? What deserializer to use to preserve object references issued by Json.Net ?