First time here? You are looking at the most recent posts. You may also want to check out
older archives.
Please
leave a comment, ask a question and consider
subscribing to the latest posts via RSS or
email. Thank you for visiting!
Advertisement
You are looking at a partial list of posts.
Please
leave a comment, ask a question and consider
subscribing to the latest posts via RSS or
email. Thank you for visiting! Below is a list of entries related to:
assembly cache.
My site contains more than just the information below and I'd encourage you to visit the
home page to view
current information as well as other items/categories that might be of interest.
There are 1 entries for the tag
assembly cache
One of the new features I mentioned in my What’s new/changed post on Silverlight 3 is the fact that any application developer can take advantage of the cached assembly functionality provided by Silverlight. Let me show you how and start with the current situation.
Current Situation with Silverlight assembly references
If you are building a Silverlight application, chances are you are referencing assemblies either from the SDK, Silverlight Toolkit or other great Silverlight third party controls/frameworks. When you Add Reference to these controls/frameworks, their assembly is copied to your application and packaged up in your XAP. For some situations this is fine...