Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6112559
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T14:45:31+00:00 2026-05-23T14:45:31+00:00

I have found strange behavior of IEnumerable. When i create a collection using Linq

  • 0

I have found strange behavior of IEnumerable. When i create a collection using Linq to XML and than loop the collection and change it’s elements, the collection size reduces by 1 on each passing through the loop. Here is what I am talking about:

    var nodesToChange =  from A in root.Descendants()
                         where A.Name.LocalName == "Compile"
                         && A.Attribute("Include").Value.ToLower().Contains(".designer.cs")
                         && A.HasElements && A.Elements().Count() == 1
                         select A;
    foreach (var node in nodesToChange) {
          //after this line the collection is reduced
          node.Attribute("Include").Value = node.Attribute("Include").Value.Replace(".Designer.cs", ".xaml");
    }

But if I add only ToArray<XElement>() to the end of the linq expression, problem is solved.

Can anyone explain me why is this happening? Thanks.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T14:45:31+00:00Added an answer on May 23, 2026 at 2:45 pm

    The query is evaluated on each loop cycle.

    You’re changing the Include value so the element is no longer returned from your query, as it doesn’t match

    A.Attribute("Include").Value.ToLower().Contains(".designer.cs")
    

    By calling ToArray or ToList on your query the loop enumerated a fixed collection, so your manipulation doesn’t impact.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have found an strange behavior when use the open file dialog in c#.
I found some rather strange behavior... Here is how to replicate the problem: Create
I have noticed strange behavior when using term-mode if I kill word in termmode
I have found a strange behavior in p:inputMask if it is located inside a
I found the following rather strange. Then again, I have mostly used closures in
I have found many tutorials about using Windows Server 2003 as a development machine,
Good day, everyone. I found strange behavior within ASP.NET engine when it handles non-existent
I found out really strange behavior on relatively simple use case, probably I can't
Is there any explanation of this strange behavior of defined constant? I have 1
I have found a strange behaviour when trying to push a viewcontroller onto the

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.