Advanced Forum Search Results
-
The System.xml.linq.dll did not appear to be deployed in either C:\Program Files (x86)\Microsoft Silverlight\4.0.41108.0 or C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\Silverlight\v4.0
Are XDocument and their peers elsewhere in the new version?
-
DDtMM,
I've seen the same errors. As far as I can tell, it's traced back to having the object you're binding against be derived from DependencyObject... I believe there's a bug in how the XcpImports handle DependencyObjects as a data context. I believe the same code path executes and exhibits the bug if you attempt to ...
-
I look forward to seeing the results of this effort, I really hope you can sustain it. I know you're targeting the SL3 features, but it would be great if you could include at least thoughts and samples towards the tester's perspective, automated and otherwise. Silverlight provides lots of unit tests, let's see how to extend those to our own work!
-
So, what other image options are there now? I'm the architect on Inkubook.com, and we do a LOT of image manipulation all things considered. I haven't, unfortunately, taken the time to dig into the new parts yet, mostly just checking for upgrade compatability with the current site.
-
Try casting to float instead of int. I noticed in the course of doing some other work that a double value that's passed through AgCore isn't the same as went it went in. Investigation led me to realize that agcore.dll took everything in floats instead of doubles, and the difference was rounding error from the cast.
It's been a while since I ...
-
Is this SL3? You have it tagged with both, but I've never noticed this in SL2.
-
As I posted above, my primary goal was to successfully set compile-time dependencies on the visual state names. This is important to us, so a "fix" to remove those generated parameters would be considered a breaking change to inkubook.com.
Here is the code I created to populate those fields as a work-around until MS fixes ...
-
I'm running into the same issue, and it's making it much harder to write elegant code for Visual State Manager... I'd like to be able to say:
VisualStateManager.GoToState(this, EditorWorkspaceMode.Name, true);
(Or, ...
-
First off, great job! This is a major release for you guys, and I'm very impressed.
Second, I have a serious message to Microsoft's management of this release: "You screwed it up."
My opinions are here:
manicprogrammer.com/.../silverlight-2-rtw-or-how-microsoft-choked.aspx
-
We have a Silverlight solution with five projects in the following structure (project names changed to protect the guilty):
Class libraries A and BApplication (.xap's) C and Dweb application (test harness) E. B references A,
C & D each reference both B and A,
E references C and D.Throughout Beta 2, we have been successfully building this ...