Welcome Guest! To enable all features please Login or Register.



Poll Question : Do we need to support .NET Framework client profiles in the future builds of iGrid.NET?
Choice Votes Statistics
  Yes, support this.
44 %
  No, abandon this.
55 %
(Poll is closed)  Total 9 100%
Guests can't vote. Try login or register. The poll has expired.
Go to last post Go to first unread
#1 Posted : Friday, March 14, 2014 2:13:30 PM(UTC)

Rank: Administration

Groups: Administrators, Forum Moderator
Joined: 1/17/2011(UTC)
Posts: 1,111

Thanks: 15 times
Was thanked: 141 time(s) in 141 post(s)
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 Wednesday, March 19, 2014 6:40:39 AM(UTC)  | Reason: Not specified

Martin Sutherland  
#2 Posted : Tuesday, March 18, 2014 2:15:36 PM(UTC)
Martin Sutherland

Rank: Newbie

Groups: Registered
Joined: 3/18/2014(UTC)
Posts: 7
Location: United Kingdom

Was thanked: 1 time(s) in 1 post(s)
The split between client and full framework was to satisfy the security concerns of big corporates. Framework 4 client profile is almost always already installed on users PCs and thus easier to target this. Corporates may not allow installation of newer framework!
#3 Posted : Tuesday, March 25, 2014 4:55:11 PM(UTC)

Rank: Newbie

Groups: Registered
Joined: 2/7/2011(UTC)
Posts: 2
Location: Germany

Perhaps this are two questions.
1. Continue support of the client profile.

As long as you target .NET 4.0 I would prefer the support of the client profile.

2. Using different assemblies for design and runtime.

One big point why we are using iGrid is it's small runtime footprint.
Users browsing this topic
Similar Topics
Support of .NET Framework client profiles in iGrid.NET (WinForms Grid Polls)
by Igor/10Tec 3/14/2014 2:09:33 PM(UTC)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.