This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello, Our SL4 project references the April 2010 release of the Silverlight Toolkit for SL4, but I find that your Silverlight Elements requires the Dec 2009 release and builds using VS2008 with SL3. This leads to a version conflict when compiling in your library. We're only using the HTML editor from SL Elements. Will you have an update for SL4 shortly, or do you have a recommended work around? Thank you, Peter |
|
|
|
|
Hello Peter, We've tried to reproduce this here and we've not had any problems getting Silverlight Elements to coexist with the April 2010 Toolkit under Silverlight 4. Could you describe what you're doing that results in the version conflict, or provide us with a minimal project that causes the version error in your environment? Thanks! |
|
|
|
|
Thank you for your reply. Here are some additional details. The toolkit files we presently reference include:
I have the following toolkit versions installed:
We had originally referenced the v4 toolkit. When I add the reference to Mindscape.SilverlightElements.dll I get the below messages - repeated many times. If instead I reference all 3 files from the v3 toolkit, all will build fine. And if I use your supplied copy of System.Windows.Controls.Toolkit.dll, along with the v4 toolkit files for the other two modules, I get a version conflict message due to the mix and match. These results are what let me to think there was a meaningful change in the v4 toolkit that created a problem for your DLL. Have I overlooked something? Best regards,
C:\Program Files\MSBuild\Microsoft\Silverlight\v4.0\Microsoft.Ria.Client.targets(303,5): warning : Failed to load types from assembly 'Mindscape.SilverlightElements, Version=1.1.283.14316, Culture=neutral, PublicKeyToken=3d6a6620bd25674b' so the assembly will be ignored. C:\Program Files\MSBuild\Microsoft\Silverlight\v4.0\Microsoft.Ria.Client.targets(303,5): warning : Cannot resolve dependency to assembly 'System.Windows.Controls.Toolkit, Version=2.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' because it has not been preloaded. When using the ReflectionOnly APIs, dependent assemblies must be pre-loaded or loaded on demand through the ReflectionOnlyAssemblyResolve event. |
|
|
|
|
Hello Peter, I've attached a test project which uses both the April 2010 toolkit and Silverlight Elements and builds okay on our test systems (it uses the PaletteColorPicker control rather than the HTML editor, but I've tested with the HTML editor as well). Could you give this a go and let us know if it fails to build in your environment? (You may need to modify the reference paths of course.) Looking at the error messages, this looks like it may be a RIA Services issue. Can you confirm that your project is using RIA Services? Can you reproduce the problem in a non-RIA Services project? If this is the problem, it may make it necessary to refactor the solution, as we've found RIA Services to be very flaky when dealing with dependencies -- but of course we'll be happy to work with you and the RIA Services team at Microsoft to see if we can achieve a less drastic resolution. |
|
|
|
|
Thank you again for the excellent support. I'll give this test project a try right away. And yes, we are making extensive use of WCF RIA Services. Peter |
|
|
|
|
I have tested with your project and everything built correctly. I did not have to change any references. I then one by one added in all the other additional assemblies I reference (total of 43) and all built correctly. So it seems that the trigger for this issue will take a bit more analysis on my end. Just very odd that all builds with the v3 toolkit but not with v4, without a single change to our own app code - which unfortunately is hundreds of files - not so easy to just turn a few things off. I'll update you when I have more deails. Peter
|
|
|
|
