Skip to main content

Optimizing a Silverlight XAP File

I took another hard look at Regex Hero to see if there was any way I could remove the two remaining assemblies I still had in it. I did something similar once before by removing the Linq assembly a couple months ago.

But still, the Regex Hero XAP file was 170 KB and I knew these assemblies were taking up most of that. So I tried to find a way to remove the System.Windows.Controls and System.Windows.Controls.Toolkit assemblies. After all, I was using only a small fraction of their features anyway.

Well I was indeed able to remove the toolkit by getting rid of the expanders and dockpanels. I found that I didn't really need them. That saved 60 KB.

But I still needed the GridSplitter out of the System.Windows.Controls assembly so I wasn't willing to get rid of it. So I asked this question on StackOverflow. It seems that Microsoft released the source for all of Silverlight 2's controls. So I downloaded the source, pulled everything out necessary for the GridSplitter and made a new project out of it. After rebuilding it and including it in the RegexHero project, that removed another 60 KB. That brought the Regex Hero XAP file down to 51 KB.

So yesterday Regex Hero was 170 KB. Today it's 51 KB. That's what I'm talking about. You can see how fast it loads now by clicking here.

I've come up with a few other optimization techniques you can read about on my new site SilverlightXAP.  I've even created a project out of the GridSplitter that you can download yourself.

Comments

Popular posts from this blog

Regex Hero for Windows 10 is Underway

Awhile back I began working on an HTML5 / JavaScript version of Regex Hero . However, it was a huge undertaking essentially requiring a complete rewrite of the entire application. I have not had enough time to dedicate to this lately. So I've begun again, this time rewriting Regex Hero to work in WPF. It'll be usable in Windows 10 and downloadable from the Microsoft Store. This is a much easier task that also has the advantage of running the .NET regex library from the application itself. This will allow for the same speedy experience of testing your regular expressions and getting instant feedback that Regex Hero users have always enjoyed. I expect the first release to be ready in Q4 of 2019.

Optimizing Your Regular Expressions

Regular expressions will backtrack.  That's an unfortunate thing about them because backtracking can be slow.    And in certain (rare) cases the performance can become so awful that executing the regular expression against a relatively short string could take over a minute.  There's a good article about catastrophic backtracking over at regular-expressions.info . And today I created a video about all of this called  Regex Lesson 5: Optimization .  In the video I start with a very poorly written regular expression and make several improvements to it, using the benchmarking feature along the way.  By the end of the video I make the regular expression over 3 million times faster. In addition, today's update to Regex Hero provides a little message in the event that you encounter a regular expression that takes over 10 seconds to evaluate... And then last of all, I changed the benchmarking feature a bit.  In the past it would simply test your regular expression against

Silverlight 4 Coming in April, or Maybe Sooner

The exact release date has not been announced. But Visual Studio 2010 RTM is coming out in April and I think it's safe to assume that Silverlight 4 will be released no later than that. Each release of Silverlight has brought massive improvements over the previous version. And once again, Silverlight 4 does not disappoint. There is a long list of improvements but the ones that I think that will affect Regex Hero are as follows: RichTextBox My plan is to use this in place of all 4 major textboxes in Regex Hero. The new RichTextBox has built-in multiple undos & redos, so I can ditch my home-brewed code. It should be nice to use for syntax highlighting for the regular expressions I intend to create. It also has a built-in API to determine the pixel position of the text. I should be able to use this API and build a new highlighting scheme based off of it. This should do a couple things. First, I should be able to finally fix the problem I had with the ScrollViewer and