Howdy Infragistics, I found a neat project that allows you to recompile SL code to web assembly/html5. If I got your controls to work on there we could potentially migrate without a major rewrite. doc.opensilver.net/.../getting-started-tour.htmlSo I downloaded the infragistics source code and tried to build in VS2013 using debug any cpu, but I am getting issues in that these references are not found Reference Include="Microsoft.Windows.Design.Extensibility, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL" Reference Include="Microsoft.Windows.Design.Interaction, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL"If I turn off specific version the Microsoft.Windows.Design.Metadata can't be found.What configuration do I need to be able to build this sln? Alternately if you guys could build it on Open SL, you could unretire the product and advertise it for SL migrations....
Hello Andrew,
Thank you for contacting Infragistics. You shouldn't need the source code to build 16.1 SL projects, just use our assemblies and avoid any design assemblies for now. As long as you are able to run a blank silverlight project similar to our wpf controls I don't see any issue migrating to a newer platform that accepts this project type. If you can send me a basic project I'll take a look. Bare in mind most of us here at Infragistics moved away entirely from Silverlight so I personally don't have VS 2013 or VS 2015 that accepts Silverlight to run anything at the moment.
Michael,
I do need to build your code, let me elaborate.
1. We have a silverlight application
2. There is a project called open silver that allows visual studio to compile silverlight projects to run via web assembly which will allow us to run the app in new browsers. http://doc.opensilver.net/documentation/general/getting-started-tour.html
3. Each silverlight project needs to be compiled by open silver.
Therefore, I need to recompile all your controls in open silver, but first I want to make sure they build normall,
So if we get this working, your silverlight controls will be viable for both migrating SL apps to web assembly or for use in modern development.
Edit: Found out how to make it build, you guys are relying on this dll, and changing specific version to off failed
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PublicAssemblies\Microsoft.Windows.Design.Interaction.dll
So I had to install vs2010 and it build fine.
Now to see if I can migrate
Ok thank you for clarifying, I see we discussed this previously here:https://www.infragistics.com/community/forums/f/retired-products-and-controls/97966/issues-building-infragistics-silverlight-14-2-20142-2159
Let me know how it works out.