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

Notification

Icon
Error


Poll Question : What should be the minimal version of .NET for iGr
Choice Votes Statistics
  .NET Framework 2.0
5
26 %
  .NET Framework 3.5
8
42 %
  .NET Framework 4.0
6
31 %
(Poll is closed)  Total 19 100%
Guests can't vote. Try login or register. The poll has expired.
Options
Go to last post Go to first unread
Igor/10Tec  
#1 Posted : Friday, January 28, 2011 10:15:19 AM(UTC)
Igor/10Tec

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)
We are going to develop iGrid.NET only for the .NET Framework 4.0 and abandon the support of the v2.0-3.5 in the future versions of iGrid later this year. The reason for this is that many developers have already migrated to .NET 4.0/VS2010 or will do that this year, so there will be a very minimal demand for iGrid.NET for the earlier versions of .NET.

Vote here to let us know what minimal version of the .NET Framework is required for iGrid.NET.

Feel free to place any additional textual comments in this topic.

You can also vote for the minimal version of VS used to develop iGrid here.

Edited by user Friday, March 14, 2014 2:15:57 PM(UTC)  | Reason: Not specified

hgirma  
#2 Posted : Friday, February 4, 2011 7:01:40 PM(UTC)
hgirma

Rank: Newbie

Groups: Registered
Joined: 1/20/2011(UTC)
Posts: 1

Well, it looks like you may after all abandon 2.0, but before you do that, can you please add one last feature for it. I really liked and welcomed the new events you added

RowsAdded and RowsRemoved

These two events are very powerful, and equally powerful, yet missing, is the RowsVisibleChanged. Please add this before moving on..

here is what I am thinking.. its signature should look something like this

RowsVisibleChanged(object sender, iGRowsVisibleChangedEventArgs e)
{
//the following properties are helpful..
e.RowIndex
e.Visible //the updated state of the row
}

I will love you long time if you add this!!
Axel  
#3 Posted : Monday, February 7, 2011 6:51:44 AM(UTC)
Axel

Rank: Newbie

Groups: Registered
Joined: 1/24/2011(UTC)
Posts: 2

I have sympathy for those who are staying with the previous versions of .NET, yet when one wants to offer a competitive product to the customer, one has to offer an interface that matches what's new on the market. So, bite the bullet and upgrade.
BlackForestIT  
#4 Posted : Monday, February 7, 2011 8:21:55 AM(UTC)
BlackForestIT

Rank: Newbie

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

One of the main issue we choose iGrid was the smart footprint.
So if you change to .NET 4.0 it would be a good thing to try to use the (smaller) Client profile of it.
Regards Friedhelm
Igor/10Tec  
#5 Posted : Monday, February 7, 2011 3:19:37 PM(UTC)
Igor/10Tec

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)
Originally Posted by: BlackForestIT Go to Quoted Post
One of the main issue we choose iGrid was the smart footprint.


Thanks! We always try to make our products as small as possible - we do not like to bloat them with tons of features and turn them into "monsters".

Originally Posted by: BlackForestIT Go to Quoted Post
So if you change to .NET 4.0 it would be a good thing to try to use the (smaller) Client profile of it.


iGrid.NET 3.0 has been already reimplemented to be totally compatible with the .NET 4.0 client profiles. Though it is still .NET-2.0-based :)
Users browsing this topic
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.