Cannot remove Platform with Configuration Editor : Bug Reports

[roneil]

Removing a platform using the Ranorex Studio Configuration Editor doesn’t remove that platform in all projects.

1. Open Ranorex solution that contains one or more projects with multiple defined platforms (e.g., ‘x86’ and ‘AnyCPU’)
2. Select Build->Edit configurations/platforms->Platform<Edit>
3. Select platform to remove, click ‘Remove’, then click ‘Yes’
4. Platform is removed from listing; click Close
5. But platform is NOT removed from all projects (use drops-downs in each project to check)
6. Select <Edit> on a project then try to remove the platform (select, click ‘Remove’, click ‘Yes’) – it doesn’t work (platform stays listed)

The only way to ensure the platform is removed is to edit the CSPROJ file with a text editor (Notepad, etc.):
1. Change the Platform in PropertyGroup containing the project GUID
2. Delete the PropertyGroup for the platform no longer required
3. Save and close the file
4. Repeat as needed for all projects within the Ranorex solution
5. Now the platform option is no longer listed

Similar issues occur when changing Target CPU from x86 to AnyCPU … these work-around steps may be combined with those for that issue.

We have verified this issue exists for Ranorex Studio versions 3.01, 3.03, 3.04, 3.05, and 3.1.0 on Windows 7 SP1 x64. VS2008 is installed, as well as .NET 3.5.1 and .NET 4.0 (client profile).

This issue doesn't occur if you manually fix the issues that occur when changing Target CPU from x86 to AnyCPU (http://www.ranorex.com/forum/cannot-change-the-target-cpu-when-platform-is-anycpu-t2600.html#p10371).

[Support Team]

Hi,

Thanks for reporting this issue!
It looks like it might be a bug, we will look into it.

Regards,
Markus
Ranorex Support Team

[Support Team]

I could not reproduce that problem with Ranorex 3.1.1 anymore. Anyway, if it only occurred in combination with the issue described in this post, it should be gone with the fix for that issue

Regards,
Alex
Ranorex Team

[roneil]

We have verified that this and the other issue are fixed in versions 3.1.3, 3.2.0, and 3.2.1.

Thank You.