After I select my assemblies to upload I see the treeview load with the assembly details for a split second and then it disappears. I ran fiddler and noticed there are two MinifierService.svc calls. The first looks like it is uploading the files and returns the list of objects. The second call sends the list of objects but returns with a 500 http error.
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</faultcode><faultstring xml:lang="en-US">The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.</faultstring></s:Fault></s:Body></s:Envelope>3 Answers, 1 is accepted
0
Hi Michael,
Unfortunately the Assembly Minifier tool has many known limitations and therefore at the moment it might not be your best option.
Instead you can check out this blog post that elaborates on different ways for reducing the size of your XAP. Also, with the Q1 SP1 2012 release we started providing no-xaml version of our assemblies. They are smaller as all xaml is stripped down so that you can use the controls' logic but add in your application only the xaml styles for the RadControls you need.
Regards,
Tina Stancheva
Telerik
Unfortunately the Assembly Minifier tool has many known limitations and therefore at the moment it might not be your best option.
Instead you can check out this blog post that elaborates on different ways for reducing the size of your XAP. Also, with the Q1 SP1 2012 release we started providing no-xaml version of our assemblies. They are smaller as all xaml is stripped down so that you can use the controls' logic but add in your application only the xaml styles for the RadControls you need.
Regards,
Tina Stancheva
Telerik
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for SILVERLIGHT.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
0
Alex Heavner
Top achievements
Rank 1
Rank 1
answered on 09 Sep 2014, 03:04 PM
Has there been any update on this issue? I tried Minifier with Telerik.Windows.Controls.dll and I experience the same issue that was encountered by Michael. Looking at the traffic I see a 500 error with the same fault code and I see the list appear for a split second and then disappear.
Thanks!
Alex
Thanks!
Alex
0
Hello Alex,
As Tina stated in the previous reply, we are fully aware of some discrepancies in our Assembly Minifier. The Assembly Minifier provided a solution to a problem which was present in the previous version of Silverlight. With the introduction of Implicit Styles and no-XAML assemblies in UI for Silverlight we may be discontinuing the support for the minifier. We will have an official statement soon.
Alex, do you think you will be able to use our no-XAML assemblies and Implicit Styles instead of the minifier? It is a better solution, because the dlls are with reduced size at first place and after that you have full control on which styles you need. Furthermore, this approach ensures a better performance for your project. More information on the benefits from using Implicit Styles you can find in this blog post.
We are ready to assist you with any questions you may have when using Implicit Styles.
Regards,
Hristo
Telerik
As Tina stated in the previous reply, we are fully aware of some discrepancies in our Assembly Minifier. The Assembly Minifier provided a solution to a problem which was present in the previous version of Silverlight. With the introduction of Implicit Styles and no-XAML assemblies in UI for Silverlight we may be discontinuing the support for the minifier. We will have an official statement soon.
Alex, do you think you will be able to use our no-XAML assemblies and Implicit Styles instead of the minifier? It is a better solution, because the dlls are with reduced size at first place and after that you have full control on which styles you need. Furthermore, this approach ensures a better performance for your project. More information on the benefits from using Implicit Styles you can find in this blog post.
We are ready to assist you with any questions you may have when using Implicit Styles.
Regards,
Hristo
Telerik
Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.