Petar Petrov

I have the same problem. Instead of `CreateCertificateOverTransportBindingElement` the client binding is generated with `CreateUserNameOverTransportBindingElement`. Binding (Server) ```csharp var binding = new BasicHttpBinding(BasicHttpSecurityMode.TransportWithMessageCredential); binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.None; binding.Security.Message.ClientCredentialType = BasicHttpMessageCredentialType.Certificate; ```...

Setting the base addresses seems to fix the problem. But shouldn't the service behavior dynamically update the WSDL response? ```csharp .AddService(options => { options.BaseAddresses.Clear(); options.BaseAddresses.Add(new Uri($"http://localhost:17010")); }) ```

There should be a way to work with the base entity only without querying all the derived types. ```csharp var entity = context.Set().FirstOrDefault(x=> x.Id == myEntityId); entity.Text = "test"; context.SaveChanges();...

Maybe we need a mixed mode so that we have a discriminator column in the base entity and all extra columns/properties mapped to other tables.

@roji My case seems to be more niche, as I am trying to use EF on an existing database. In my case, I have a base table with a string...

I am appending a co-signature or prolonging the previous signature and aiming to authenticate the package prior to saving it. The addition or extension of signatures does not invalidate the...