Search Results

Search found 3 results on 1 pages for 'eugarps'.

Page 1/1 | 1 

• IEditableCollectionView.AddNew() Throwing ArgumentNullException

  - by Eugarps

  In the context of Silverlight RIA using DomainContext and, the code as follows: private void AddProductButton_Click(object sender, RoutedEventArgs e) { var target = (Web.LocatorProduct)((IEditableCollectionView)ProductSource.DataView).AddNew(); target.Locator = LocatorID; target.Product = NewProduct.Text.ToUpper(); ((IEditableCollectionView)ProductSource.DataView).CommitNew(); } Is throwing ArgumentNullException in AddNew(), CreateIdentity() further up on the stack (a generated method) due to product being null. Product and LocatorID are, in combination, the primary key. I'm guessing that EF is not allowing me to generate a new item without meeting database contraints? How does this make sense if I need to obtain a primary key from the user? I have control over all tiers of the application, so suggestions on database design if needed are also welcomed.

  Read the article

• LocalUser access for WCF hosted in IIS

  - by Eugarps

  I have tried every combination to allow unauthenticated access to WCF as in "LocalUser" accounts, in IIS without success. Here is what I've most recently tried: wsHttpBinding with Message security and mode set to "None". IIS anonymous access enabled, all others disabled, folder level access at default (but granted read access to "Users" which is all users in our domain). I understand I may not have provided enough information to solve the issue, but perhaps somebody can point me in the right direction - is this likely to be a IIS configuration issue or a WCF configuration issue... if WCF, is it likely to be a client level or server level issue? The error I get when attempting to access here is "User is not authenticated". We have ASMX services in the domain which are behaving properly, I am the first developer using WCF here.

  Read the article

• C# Events and Lambdas, alternative to null check?

  - by Eugarps

  Does anybody see any drawbacks? It should be noted that you can't remove anonymous methods from an event delegate list, I'm aware of that (actually that was the conceptual motivation for this). The goal here is an alternative to: if (onFoo != null) onFoo.Invoke(this, null); And the code: public delegate void FooDelegate(object sender, EventArgs e); public class EventTest { public EventTest() { onFoo += (p,q) => { }; } public FireFoo() { onFoo.Invoke(this, null); } public event FooDelegate onFoo; }

  Read the article

1