In the generated code of the Admin Edit/Insert pages one will see a typed EntityDataSource with a script that contains only 3 properties
for example:
<data: CompanyDataSource ID="CompanyDataSource" runat="server" SelectMethod="GetByCompanyID" EnableTransaction="false">
This compiles and works.
However when I try to add the datasource to a page by drag and drop, it creates many more properties including
provider="" (a property that does not appear in the property inspector)
Not filling in a value for the Provider leads to an error. After deleting again all extra created properties (including Provider) from the tag, this error disappears, at least when dealing with a single page.
However, when I try to use the same script code inside a wizardstep and go to design view I get the "Object reference not set to an instance of an object" error. This can only be again the Provider
But when I set Provider to "CompanyService" or "CompanyProvider" or even "DataRepository.CompanyProvider" then I get the error:
Cannnot create an object of type 'TestLogin.DataAccess.IEntityProvider from its string representation for the 'Provider' property.
So what should be done with this property ?
And why am I forced to use it if the Admin pages do not use it ?
Any help would be appriciated
In a single page I can put a typed EntityDataSource connected to a MultiFormView that contains an InsertItemTemplatePath to create an insert page. This compiles and works.
However, when I try to do the same in a wizardstep I get design view control errors.
I tried it in two different ways:
1) When I copy and paste the script sourcecode for the EntityDataSource and MultiFormView inbetween the wizardstep tags, and switch to design view I get "