BUY Cefaclor ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/?utm_source=rss&utm_medium=rss&utm_campaign=replace-your-collections-with-ienumerablet Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 BUY Cefaclor ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/comment-page-2/#comment-64341 Aa Tue, 11 Oct 2011 07:31:00 +0000 http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/#comment-64341     MsgPanel.Visible=true;             viewPlaceHolder.Visible = false;             imgsearch.Visible = false;             txtsearch.Visible = false;             Msg.Visible = true;             Msg.Text = "Enter the Role code and then click Next!";             addPlaceHolder.Visible = true;             viewPlaceHolder.Visible = false;             Msg.ForeColor = System.Drawing.Color.Red;     MsgPanel.Visible=true;
            viewPlaceHolder.Visible = false;
            imgsearch.Visible = false;
            txtsearch.Visible = false;
            Msg.Visible = true;
            Msg.Text = “Enter the Role code and then click Next!”;
            addPlaceHolder.Visible = true;
            viewPlaceHolder.Visible = false;
            Msg.ForeColor = System.Drawing.Color.Red;

]]> BUY Cefaclor ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/comment-page-1/#comment-31363 io Thu, 04 Sep 2008 06:48:45 +0000 http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/#comment-31363 o o

]]> BUY Cefaclor ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/comment-page-1/#comment-20029 ?? (21-4-2008) | ????? .NET Atlantis Mon, 21 Apr 2008 06:10:42 +0000 http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/#comment-20029 [...] Replace your Collections with IEnumerable ???LinQ???? [...] [...] Replace your Collections with IEnumerable ???LinQ???? [...]

]]> BUY Cefaclor ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/comment-page-1/#comment-19647 John Thu, 10 Apr 2008 17:57:29 +0000 http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/#comment-19647 The main reason I can see for moving a method that returns a Collection or List to returning an IEnumerable is that you then have the use of the yield keyword. http://flimflan.com/blog/ThePowerOfYieldReturn.aspx Joshua is better at explaining things than I am. The main reason I can see for moving a method that returns a Collection or List to returning an IEnumerable is that you then have the use of the yield keyword.

http://flimflan.com/blog/ThePowerOfYieldReturn.aspx

Joshua is better at explaining things than I am.

]]> BUY Cefaclor ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/comment-page-1/#comment-19547 Matt Wed, 09 Apr 2008 00:35:21 +0000 http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/#comment-19547 @trasa I didn't mean from properties. and yes, arrays implement IList but IList.Add? Please don't try that on your array. In my experience it's easiest for the consumer to just handle the array, new List(tArr); .. but I could be swayed. I'll play with it. @trasa I didn’t mean from properties. and yes, arrays implement IList but IList.Add? Please don’t try that on your array. In my experience it’s easiest for the consumer to just handle the array, new List(tArr); .. but I could be swayed. I’ll play with it.

]]> BUY Cefaclor ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/comment-page-1/#comment-19497 Reflective Perspective - Chris Alcock » The Morning Brew #68 Tue, 08 Apr 2008 07:11:09 +0000 http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/#comment-19497 [...] Replace your Collections with IEnumerable<T> - Tony Rasa looks at moving from concrete collection classes in his API to IEnumerable<T> [...] [...] Replace your Collections with IEnumerable<T> – Tony Rasa looks at moving from concrete collection classes in his API to IEnumerable<T> [...]

]]> BUY Cefaclor ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/comment-page-1/#comment-19482 Chris Brandsma Tue, 08 Apr 2008 02:25:11 +0000 http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/#comment-19482 I've been doing this for a while now. You should always try to pass the most basic object you can to between layers. But something I have been wondering about these days, when I'm passing data between layers (say between a view and a presenter), do you just stick with passing primitives, or do you create a specialized data class? If you stick with primitives you end up with a more complex interface between the objects. Also, if you create a special data object you can keep the data interaction better in mind for what is intended to happen. On the down side, you now have another tiny class to manage. I’ve been doing this for a while now. You should always try to pass the most basic object you can to between layers.

But something I have been wondering about these days, when I’m passing data between layers (say between a view and a presenter), do you just stick with passing primitives, or do you create a specialized data class?

If you stick with primitives you end up with a more complex interface between the objects. Also, if you create a special data object you can keep the data interaction better in mind for what is intended to happen. On the down side, you now have another tiny class to manage.

]]> BUY Cefaclor ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/comment-page-1/#comment-19480 Sean Timm Mon, 07 Apr 2008 22:07:15 +0000 http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/#comment-19480 Okay... it removed all of my nice generics markup... argh. Before everyone starts yelling at me for not using generics, I was referring to ICollection(T), IList(T), and IEnumerable(T). Okay… it removed all of my nice generics markup… argh. Before everyone starts yelling at me for not using generics, I was referring to ICollection(T), IList(T), and IEnumerable(T).

]]> BUY Cefaclor ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/comment-page-1/#comment-19479 Sean Timm Mon, 07 Apr 2008 22:05:31 +0000 http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/#comment-19479 If you're passing around a collection where you know you'll be frequently accessing the count, I'd argue that you should just be returning ICollection. Do you want to be able to index into it? IList. The extension methods can be nice where someone returned you an IEnumerable, and it turns out that you want to know the count. Internally, it'll just call the Count() method if it's an ICollection underneath. Otherwise, it'll enumerate through them to get a count. All that being said, I've personally refactored some code to move to IEnumerable where I *knew* I'd be accessing a Count at one point, but it was a Count that needed to disappear at some point, so I was okay with it. :) If you’re passing around a collection where you know you’ll be frequently accessing the count, I’d argue that you should just be returning ICollection. Do you want to be able to index into it? IList. The extension methods can be nice where someone returned you an IEnumerable, and it turns out that you want to know the count. Internally, it’ll just call the Count() method if it’s an ICollection underneath. Otherwise, it’ll enumerate through them to get a count.

All that being said, I’ve personally refactored some code to move to IEnumerable where I *knew* I’d be accessing a Count at one point, but it was a Count that needed to disappear at some point, so I was okay with it. :)

]]> BUY Cefaclor ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/comment-page-1/#comment-19477 trasa Mon, 07 Apr 2008 21:37:57 +0000 http://elegantcode.com/2008/04/07/replace-your-collections-with-ienumerablet/#comment-19477 Mostly, its just a matter of personal style. There is an FxCop rule warning about returning arrays from properties, the issue being that an outside caller gets a reference to your array, and can alter it and therefore alter the state of your class: http://msdn2.microsoft.com/en-us/library/0fss9skc.aspx For methods: an array implements IList, so returning an array is really just a step or so away from my original starting place of returning Collection<T> or List<T>. Returning a more abstract type than an array gives you more options for extensibility - you could replace the array with another collection type that had more implementation. This is only a factor if you've got developers out there "in the cloud" who rely on your return type - if its not a big deal to make breaking changes, then it doesn't matter so much. Mostly, its just a matter of personal style.

There is an FxCop rule warning about returning arrays from properties, the issue being that an outside caller gets a reference to your array, and can alter it and therefore alter the state of your class: http://msdn2.microsoft.com/en-us/library/0fss9skc.aspx

For methods: an array implements IList, so returning an array is really just a step or so away from my original starting place of returning Collection or List. Returning a more abstract type than an array gives you more options for extensibility – you could replace the array with another collection type that had more implementation. This is only a factor if you’ve got developers out there “in the cloud” who rely on your return type – if its not a big deal to make breaking changes, then it doesn’t matter so much.

]]>