What is the PhoneLink Control?
Good question! It is for mobile devices so that you can dial a phone number shown on a webpage.
Notice that "DataKeyNames" property on a GridView is plural? What's up with this?
I grabbed the following from the Beta1 docs:
Use the DataKeyNames property to specify a comma-separated list of field names that represent the primary key of the data source. When the DataKeyNames property is set, the GridView control automatically populates its DataKeys collection with the values from the specified field or fields, which provides a convenient way to access the primary keys of each row. When the AutoGenerateColumns property is also set to true, the GridView control automatically ensures that the field or fields specified in the DataKeyNames property are read-only.
So it is a comma-separated, composite field, primary key.
What happened in your SQLCache Dependency demo on 4/13/2005? Did you figure out the problem?
I sure did. It turns out that I accidently had not removed the settings from the last time I presented the content in March. So I did the following:
- Removed the database Cache Dependency settings by using the command: aspnet_regsql -S -E -d Northwind -dd
- Changed the Web.config so that the SQLCacheDependency enabled=”false”
- On the SQLCacheDependency.aspx file I did the following on the SQLDataSource1 control:
- Set the property EnableCaching = False
- Cleared the property SqlCacheDependency value from having “Northwind:Employees:
Then it worked perfect!
I stepped backwards and increased the Web.config SQLCacheDependency element / Polltime attribute to 10000 milliseconds to give my changes a little more time before rendering.
What did you not do on the StrongPassword-SQLMembershipProvider demo on 4/12/2005?
A big, simple, stupid, “OOPS!”
Before step one in the demo, I forgot to run the command “aspnet_regsql.exe” file. This opens up a dialog box which allows you to generate the provider database on the SQL Server DB. So when we never saw the reference to the “ASPNETDB” and we thought it was a ConnectionString problem, well the problem was deeper. The database did not even exist yet.
Be sure when you run the code to do this step and you will be much more successful than I was on Wednesday.