I do have to say that I tried to use 6.0.6 to see if this would fix our issue, but I encountered another issue earlier in the application that was likely caused by the User entity being out of whack.  In addition, I was a bit annoyed by the number of breaking changes to the API that necessitated code changes.  It seems odd to update method signatures and remove constructors in a minor release that would cause many who use your product some unnecessary work and annoyance.  It's certainly not encouraging us to upgrade to 6.0.6 any time soon.

The problem was fixed in the 6.0.5 release, or you can work around it in 6.0.4 by adding the property back into the model.

 

In response to your other questions:

- We have just one edmx.

- There aren't any many-to-many navigation properties on this entity.

- All property getters and setters are public.

- The class doesn't implement any interfaces.

 

We have fixed a number of problems with navigation properties since 6.0.4, although we hadn't seen this specific problem before, so it's hard to say whether an upgrade to the latest release (6.0.6) would help.  It might be worth a try if upgrading isn't too painful for you right now.

 

Other than the above, can you provide some more information on your application:

- Do you have multiple EDMX in the solution (in either one or multiple assemblies)?

- Are there any many-to-many navigation properties on this particular entity? 

- Do any property getters or setters on this entity have other than public access?

- Does this User class implement IPrincipal/IIdentity?

 

The column I added was a simple varchar column that allows nulls and has nothing to do with the values I'm trying to set.  The properties that throw the exception are Guids that have foreign key relationships in the database table and thus also have navigation properties that are related to them.  This only occurs when creating a new entity.  The exception is thrown either when setting those Guid properties or when adding the new entity to the manager (I was trying to play with the order in the hopes it would work).

I have tried deleting the class from the designer and re-adding it, but since it's an essential class to the model, a lot of other classes had navigation properties of that type that were broken and not fixed when adding the class back in through an update of the model, so I had to revert back to the old model.

I even tried reverting back to the model from before I added the new column and forced a code gen, and I still have the same issue, which I find even more bizarre.  The stack trace from the exception goes through a whole slew of DevForce method calls, which I've pasted below.  We're using DevForce 6.0.4.  I appreciate any help that can be given.