I was working on a project this week and needed to setup a hyperlink in in the SL 4 datagrid. It took just a bit of playing and works great. You can take the following code and put it into the <sdk:DataGrid.Columns> entity under the grid. in this case, we are using the Navigation framework in SL. To make this work, i bound CompanyName to the Content property and then set the NavigateUri property by setting a reference to the page (CustomerInfoPage) and fed it the parameters (IdNumber and SomeDate) ......
Working on the same solution as problem 1. This time it was a binary reference to two dlls. The app would build on my system but not on the tfs build server. Well, after lots of playing around i found out that one dll had the correct hintpath to its source in the project references and one did not. Solution: 1: Close VS 2: Open Windows Explorer and find the parent folder of the solution. 3: Search for all Bin and Obj folders in the solution. 4: Delete all of these folders. 5: Reopen VS and go back ......
This week i hit a couple of problems with VS 2010.
Problem no 1 was with references to other projects in a solution. I had been working away on a solution for weeks when yesterday vs started complaining that a reference was bad in one app. I would reset the ref and the errors would go away until i recompiled and boom they were right back. And this is a C# app by the way.
Solution: Close all instances of VS and reload app.
Frustrating!
One of the cool features with Sl 4 is the ability to bind directly to an indexed item such as a dictionary. For instance, i can set a binding to a custom dependency property in a custom user control to this in XAML where MyDictionary is a .Net dictionary of objects: {MyDictionary[A221], Mode=TwoWay} Now, a word of warning. Its cool in most cases to setup a datacontext to an object that does not have data but is initialized. Works just fine. But you can’t do that here. Why not? After beating my head ......