RiaServicesContrib Discussions Rss Feed

New Post: How to generate in code first with out EDMX file scenario ?

jophy — Thu, 21 Feb 2013 08:28:44 GMT

Hello all ,

         I am working on project were we connect to database through code first EF approach .

is it possible to generate using Dbcontext and POCO class's .

with regards ,
jophy

New Post: Fluent Metadata Custom Validation

dwinter0 — Fri, 09 Nov 2012 22:52:10 GMT

Hi Merijn.

I'll try it.

Thanks!

New Post: Fluent Metadata Custom Validation

MdeJ — Fri, 09 Nov 2012 22:27:59 GMT

Hi,

Suppose you have a class Person with a property FirstName, and a class TestPersonData with a method CheckFirstname like this:

public class PersonDataValidator
        {
            public static ValidationResult ValidateFirstName(string firstName)
            {
                if(string.IsNullOrEmpty(firstName))
                {
                    return new ValidationResult(
                        "Invalid first name.");
                }
                return ValidationResult.Success;
            }

        }

Now you can use the Fluent API to register this validation method for the property FirstName on the entity Person:

metadataContainer.Entity<Person>().Validation(x => x.FirstName).Custom<PersonValidator>("ValidateFirstName");

I hope this helps you

Kind regards,

Merijn

New Post: Fluent Metadata Custom Validation

dwinter0 — Thu, 08 Nov 2012 10:46:55 GMT

I'm trying to use Custom Validation with Fluent Metadata but it doesn't have any documentation or sample usage.

Can someone provide a sample for this?

Thanks,

Douglas

New Post: EntityTools - ApplyState not setting EntityState correctly for non-persisted client extension property

vsdotnetguy — Sat, 25 Aug 2012 02:27:55 GMT

Hi Colin and others,

I'm extending an RIA entity on the client using a partial class with a string property that is marked with DataMember attribute but is not persisted.

When updating my entity using ApplyState method the values are correctly updated and the EntityState is correctly changed to Modified. However, if I ONLY change the partial class extension property described above, the property change gets applied but the EntityState stays as Unmodified. Is this a possible bug in EntityTools or by design?

Is there a workaround?

Thanks...Bob Baldwin
aka vsdotnetguy

New Post: Fluent Metadata - UIHints issue

MdeJ — Mon, 30 Jul 2012 08:44:44 GMT

Hi,

Thanks for reporting this issue. Since I was on holiday I couldn't respond to this issue earlier. Sorry for that.

I've fixed the bug and published a new version on nuget.org

Merijn

New Post: Fluent Metadata - UIHints issue

MdeJ — Mon, 30 Jul 2012 08:37:17 GMT

This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.

New Post: Fluent Metadata - UIHints issue

osheh — Sat, 28 Jul 2012 10:34:51 GMT

Anybody who can help on this? It seems that this UIHints is a big part of dataannotations and it is frequently used.

Regards,

Osheh

New Post: Fluent Metadata - UIHints issue

rockresolve — Sun, 22 Jul 2012 21:41:40 GMT

Yes, I've had this too.

UIHints crash VS2010 when next build or open solution.
Appears to be while building, loading Silverlight (not Web) project. So a code generation issue?
The closest Google match I found didnt seem to be related: http://forums.silverlight.net/t/219633.aspx/1/10

Peter

New Post: Fluent Metadata - UIHints issue

Amit_o9 — Thu, 19 Jul 2012 10:24:07 GMT

Even I am experiencing same problem. Someone please help.

Thanks,

Amit

New Post: Fluent Metadata - UIHints issue

osheh — Thu, 19 Jul 2012 07:06:06 GMT

I've tried to use FluentMetadata and its working perfectly fine except for UIHints. If i use this attribute, the Visual Studio crashes. Anybody had the same problem?

Thanks,

Osheh

New Post: Implementing Partial Save of deletions (plus Undo)

rockresolve — Tue, 17 Jul 2012 11:40:28 GMT

Hi Syam,

Sorry for the delay, was away on business, holiday. I've sent the code separately to you.

TODO

Clone() GraphedNodes no context parm
Copy GraphedNodes
IsCopyOf GraphedNodes
Synchronize MergeIntoCurrent GraphedNodes
Resolve if should implement IEditableObject for EntityRelationGraph.DroppedNodes?

I've added a number of tests, including specifically the SubmitChanges/RejectChanges scenarios. The code seems to be working in my limited application.

I discovered a related problem when processing changesets. By default multiple changes submitted all at once get processed in an unknown order on the server.
Delete Child followed by Add, gets processed on Server as Add & then Delete.
So if you reuse Child keys ==> problems

One possible solution is to in the Web Server project service override Submit method. In there process the deletes first, then the remain changes. See http://msdn.microsoft.com/en-us/library/ee707364%28v=vs.91%29.aspx

        public override bool Submit(ChangeSet changeSet)
        {
            bool submitOk = true;
            using (var scope = new TransactionScope())
            {
                ChangeSet changeSetDeletes = new ChangeSet(changeSet.ChangeSetEntries.Where(t => t.Operation == DomainOperation.Delete));
                ChangeSet changeSetNotDeletes = new ChangeSet(changeSet.ChangeSetEntries.Where(t => t.Operation != DomainOperation.Delete));
                if (changeSetDeletes.ChangeSetEntries.Count > 0)
                    submitOk = base.Submit(changeSetDeletes);
                if (changeSetNotDeletes.ChangeSetEntries.Count > 0)
                    submitOk = submitOk & base.Submit(changeSetNotDeletes);

                //Does not update changeSet parm
                //Does not update and is not able to change this.ChangeSet. It is readonly

                if (!changeSetDeletes.HasError && !changeSetNotDeletes.HasError)
                    scope.Complete();
            }
            return submitOk;
        }

New Post: Implementing Partial Save of deletions (plus Undo)

syammohan — Wed, 11 Jul 2012 10:11:08 GMT

Hi Peter,

Sorry for bugging you again. Can you tell me an approximate time by which you will be able to complete the Clone feature and share the source with me.

Thanks

Syam

New Post: Implementing Partial Save of deletions (plus Undo)

syammohan — Tue, 26 Jun 2012 09:53:49 GMT

Hi Peter,

Thanks a lot. Appreciate your help.

You can send me as a zip to my personal email address(wickedsyam@gmail.com).

I have been using the EntityGraph by Merijn, mostly the Clone method and Synchronize method. So it would be great if you send me the source once you implement the Clone method.

Thanks in Advance

Syam

New Post: Implementing Partial Save of deletions (plus Undo)

rockresolve — Mon, 25 Jun 2012 21:27:32 GMT

Hi Syam,

Yes I can do that. What is the best method for sharing, just a big zip?

It's proved mostly stable, I've had to make only some minor changes. However just yesterday I think I have uncovered a bug so I need to resolve that.

I have done anything about refactoring/improving the API. I've ended up with several "if (IsTrackGraphedNodes) ..." which make me think it should be refactored into an derived class. I still have some edge methods that arent implemented for TrackGraphedNodes (copy & clone functions, IEditable ?).

Peter

New Post: Implementing Partial Save of deletions (plus Undo)

syammohan — Fri, 22 Jun 2012 03:52:03 GMT

Hi Peter,

Will it be possible for you to share the customized source code of EntityGraph which can do Partial Save with deletions. It will be extremely helpful for me as I am having a similar requirement.

Thanks

Syam

New Post: Implementing Partial Save of deletions (plus Undo)

syammohan — Fri, 25 May 2012 04:57:26 GMT

Hi Peter,

That's a wonderful thing you've done. It would really great if you pulled this off. I was badly looking for this as I was having the requirement of doing the Partial Save of the deleted Entities. Keep us posted on the updates. Good Luck.

Thanks

Syam

New Post: Partial Save of Entities with Child Entities using Entity Graphs

rockresolve — Fri, 18 May 2012 02:21:47 GMT

Hi Merijin

I've been working on tracking old members. See "Implementing Partial Save of deletions (plus Undo)" http://riaservicescontrib.codeplex.com/discussions/356233

Regards,
Peter

New Post: Implementing Partial Save of deletions (plus Undo)

rockresolve — Fri, 18 May 2012 02:15:22 GMT

I've been working on implementing support for deletes in Partial Save, and also support for Partial Undo (context.RejectChanges) of additions, deletes.

I found there was no way around having to hold references for obsolete entities (I tried releasing on Detached, IdentityKeys). And then I found Undo added a whole other layer of complexity (Add, Delete during Reject). So I figured as long as people knew it was happening and could stop it, holding onto obsolete entities was survivable.

I bit the bullet and introduced another mode of behaviour for EntityGraph to TrackGraphedNodes.

I've now got it passing my unit Tests, but I'm having second thoughts about my choice of API members as that "DoTrackGraphedNodes mode" smells. Currently it used like

         === Initialise ===
        graph.TrackGraphedNodesStart();
 
         === Entity Changes here ===
 
         === Partial Save =
        EntityGraphTestsDomainContext tempContext = new EntityGraphTestsDomainContext();
        var clone = graph.Clone(tempContext);
        tempContext.AcceptChanges();    //or tempContext.RejectChanges();
        graph.SynchronizeTracked(context, clone);        
        graph.TrackGraphedNodesReset();
 
         === Dispose (release Entity references) ===
        graph.TrackGraphedNodesStop();

The context parameter in the SynchronizeTracked method is needed as the target Entity's states need updating. Which makes me question why we dont hold the context in the graph class.

Does that mode smell enough to justify reworking it to a new class? Say EntityGraphTracked

         === Initialise ===
         EntityGraphTracked graph = new EntityGraphTracked(context, sourceEntity, graphShape);
 
         === Entity Changes here ===
 
         === Partial Save =
        EntityGraphTestsDomainContext tempContext = new EntityGraphTestsDomainContext();
        var clone = graph.Clone(tempContext);
        tempContext.AcceptChanges();    //or tempContext.RejectChanges();
        graph.Synchronize(clone);        
        graph.TrackGraphedNodesReset();
 
         === Dispose (release Entity references) ===
        graph.TrackGraphedNodesStop();

Is it a fair assumption that holding Entity references is ok as long as it can be stopped? Or are there consequences I haven't found yet?

I'm currently testing it in my LOB project, but would like Feedback on the approach.

Regards,

Peter

New Post: Synchronizing list of cloned EntityGraphs

MdeJ — Sat, 14 Apr 2012 20:05:40 GMT

Hi,

Sorry for my late response...

I am afraid that I don't exactly get what the problem is. If you need to submit a Parent and Child entity, why don't you include both in a single entity graph and use the partial save mechanism for that entity graph? I probably miss the point. Perhaps you can explain your issue in a little more detail?

Best regards,

Merijn