Advanced Forum Search Results
-
But why have to go through all that trouble? Making the Silverlight app behave like HTML is more work than just doing it in HTML. As I said there are many cases where Silverlight is valid. But this site we are talking about is a classic example of how NOT to use Silverlight. This is basically just a site with some text, some menus and some links.
-
In 2030? You gotta be kidding me. Even 10 years ago we had no clue how far the web would be pushed today (back then the web was mostly just static information - today it hosts entire applications with immersive experiences, AJAX, Animations, etc... using just HTML+JS).
And I don't laugh at MS DOS. We still have the commandline that ...
-
Could you be more specific?
-
According to the error you should add a reference to System.Windows
-
What does your brush and animation look like?
Note that you can't animate the color of a LinearGradientBrush for instance (since it doesn't have a color property). So usually you would use ColorAnimation on a SolidColorBrush. You can however animate the color of one of the gradient stops inside the lineargradientbrush.
Here's an ...
-
Things to check for: Animations running, pixelshader filters etc.
To track down what is causing it start collapsing elements until the processing goes down, or remove elements one by one. A quicker method to find whats causing it might be to use the EnableRedrawRegions debugging feature.
You can also try XPerf: ...
-
System.Web.UI.WebControls is used in ASP.NET for webpages, and NOT for Silverlight. In other words, you can't use that for Silverlight.
-
I know this is not what you want to hear, but it must be said:
If you had built your website in HTML you wouldn't have had that problem.
Why not Silverlight?
Your pages are not indexable by Google
You do nothing that HTML can't do. Use Silverlight where it makes sense, and leave HTML to do what it does best.
You cannot select ...
-
You can use DoubleAnimation to animate the Opacity, or ColorAnimation to animate the color (or a combination of the two if you want both)
-
I would call it a bug, but officially it's by design. Unfortunately the internal positioning works in the Int16 range (-32768 -> 32768) most likely for performance reasons. If you get beyond that the rendering gets messed up. I've seen numerous examples of this.