Hello,
model.Load<State, Transition>(XElement.Parse(xml), “State”, “Transition”);
model.Modifiable = true;
model.HasUndoManager = true;
myDiagram.Model = model;
}
Hello,
model.Load<State, Transition>(XElement.Parse(xml), “State”, “Transition”);
model.Modifiable = true;
model.HasUndoManager = true;
myDiagram.Model = model;
}
A minor difference is that in VB you are doing new XElement(XElement.Parse(…)) instead of just XElement.Parse(…).
Also I notice the change from GraphServiceReference to LearningProgressionService, which I assume was intentional.
But I suspect that the problem is not in this code at all. Are you sure all of the templates are exactly the same as before in C#? Or do they need to be different because of changes you have made to design of the code?
Unfortunately, debugging exceptions in Silverlight can require a lot of tedious trial and error trying to find the thing that is wrong.
The name of the service is not the error because in vb.net solution i’ve changed it. I did XElement.Parse() but still facing the same error.
Which version of Silverlight 4? We’re about to release a kit that works with Silverlight 4 RTM. (Still some bugs to be squashed, and regression testing to be done.)
The current beta kits are GoSilverlight version 1.1.1.x, which are newer than what you are using. It wouldn’t hurt to use 1.1.1 beta instead of 1.1.0 beta. But if you’re using Silverlight 4 RTM, I know there are problems with printing.
Still, I don’t know of any problems that you would be encountering now by using the old beta DLL that targets Silverlight 3 instead of Silverlight 4.
To summarize: try using the GoSilverlight1114.msi beta kit, which targets Silverlight 4 RC.