As you may know, Microsoft provided .NET Framework 3.5 and 4.0 with so called client profiles optimized for client applications. With the release of iGrid.NET 3.0 we split its only DLL into two DLLs (the core functionality and the design-time functionality) to enable the usage of iGrid with the .NET client profiles.
However, starting with the .NET Framework 4.5 the .NET Framework client profiles have been discontinued. So the question is whether we need to support these outdated client profiles in the future builds of iGrid.NET?
Note that the two-assembly iGrid implementation causes extra problems for the developers when installing/deploying the component (see this forum topic
for more details). Putting all the functionality back into one DLL would also help all of us to avoid these deployment problems.
Edited by user
| Reason: Not specified