Error: Collection was modified

Elements
, ,
41

Still the main problem here is bugs://E26012 because we are very hapy with legacy targets and PackageReferences, the only problem here is the migration doesnt allow us to use that elements.
Non-legacy doesnt support Nuget api v2 and we cant move packages to a API v 3 service.

42

Yes, we’re working on getting this fixed.

43

Still no progress with E26012 ? Thanks.

44

Relevant members of the VS team have been on vacation, sorry.

45

Today’s build will have the fix that migration is skipped for legacy projects.

1 Like
46

Unfortunately, i can confirm, that it is not working in Version 11.0.0.2765: Project File lie this gets upgraded:

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">
  <PropertyGroup>
    <ProjectGuid>{3c4c43d9-9a9d-1e32-a4e6-f00e5f358a31}</ProjectGuid>
    <RootNamespace>TescoSW.CEN</RootNamespace>
    <OutputType>Library</OutputType>
    <AssemblyName>TescoSW.BLModule.CEN</AssemblyName>
    <AllowGlobals>True</AllowGlobals>
    <AllowLegacyWith>False</AllowLegacyWith>
    <AllowLegacyCreate>True</AllowLegacyCreate>
    <AllowLegacyOutParams>True</AllowLegacyOutParams>
    <AllowUnsafeCode>False</AllowUnsafeCode>
    <SCCProjectName />
    <SCCAuxPath />
    <SCCLocalPath />
    <SCCProvider />
    <ServerPath />
    <ProjectTypeGuids />
    <Configuration Condition="'$(Configuration)' == ''">Release</Configuration>
    <UseLegacyPreprocessor>True</UseLegacyPreprocessor>
    <Name>CEN</Name>
    <Mode>Echoes</Mode>
    <RunPostBuildEvent>Always</RunPostBuildEvent>
    <PrintTEAFDefines>false</PrintTEAFDefines>
    <RestoreAdditionalProjectSources>https://nuget.tescosw.loc/nuget</RestoreAdditionalProjectSources>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)' == 'Debug' ">
    <DefineConstants>DEBUG;TRACE;AGGREGATION;NORIGHTSGETSET;</DefineConstants>
    <OutputPath>bin\Debug</OutputPath>
    <GeneratePDB>True</GeneratePDB>
    <GenerateMDB>False</GenerateMDB>
    <EnableAsserts>True</EnableAsserts>
    <TreatWarningsAsErrors>False</TreatWarningsAsErrors>
    <RegisterForComInterop>False</RegisterForComInterop>
    <CaptureConsoleOutput>False</CaptureConsoleOutput>
    <StartMode>Project</StartMode>
    <CpuType>anycpu</CpuType>
    <RuntimeVersion>v25</RuntimeVersion>
    <EnableUnmanagedDebugging>False</EnableUnmanagedDebugging>
    <WebDebugTarget>Cassini</WebDebugTarget>
    <WebLaunchBrowser>False</WebLaunchBrowser>
    <XmlDocAllMembers>False</XmlDocAllMembers>
    <CodeFlowAnalysis>True</CodeFlowAnalysis>
    <UseXmlDoc>False</UseXmlDoc>
    <XmlDocWarning>WarningOnPublicMembers</XmlDocWarning>
    <Optimize>False</Optimize>
    <WarnOnCaseMismatch>False</WarnOnCaseMismatch>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)' == 'Release' ">
    <DefineConstants>AGGREGATION;NORIGHTSGETSET;</DefineConstants>
    <OutputPath>bin\Release</OutputPath>
    <GeneratePDB>False</GeneratePDB>
    <GenerateMDB>False</GenerateMDB>
    <EnableAsserts>False</EnableAsserts>
    <TreatWarningsAsErrors>False</TreatWarningsAsErrors>
    <RegisterForComInterop>False</RegisterForComInterop>
    <CaptureConsoleOutput>False</CaptureConsoleOutput>
    <StartMode>Project</StartMode>
    <CpuType>anycpu</CpuType>
    <RuntimeVersion>v25</RuntimeVersion>
    <EnableUnmanagedDebugging>False</EnableUnmanagedDebugging>
    <WebDebugTarget>Cassini</WebDebugTarget>
    <WebLaunchBrowser>False</WebLaunchBrowser>
    <XmlDocAllMembers>False</XmlDocAllMembers>
    <CodeFlowAnalysis>True</CodeFlowAnalysis>
    <UseXmlDoc>False</UseXmlDoc>
    <XmlDocWarning>WarningOnPublicMembers</XmlDocWarning>
    <Optimize>False</Optimize>
    <WarnOnCaseMismatch>False</WarnOnCaseMismatch>
  </PropertyGroup>
  <Import Project="..\References\TEAFSDK.targets" />
  <Import Project="$(MSBuildExtensionsPath)\RemObjects Software\Elements\RemObjects.Elements.Echoes.Legacy.targets" />
</Project>
47

bugs://E26012 was closed as fixed.

48

It is not working in Version 11.0.0.2765

49

Yes. 2765 (should have) had a workaround to not run upgrade for Legacy (not sure why that part didn’t work). Ne now committed the final actual fix; that’s why the issue was closed. I’ll try to get a new build to you later today, to test…

50

That would be awesome.

51

Done, new build is your Personal Downloads now.

52

Thank you very much, the private build works perfectly. We are ready to migrate to Elements 11, use Visual Studio 2022 and now I can start to analyze the migration from legacy targets.

53

Happy to hear!