This question is locked. New answers and comments are not allowed.
Hi,
Since the update to the Icenium extension for Visual Studio to 2013.3.1210.1, we have been unable to edit the configuration files for the projects. (android manifest, info.plist, config.xml)
Attempting to do so will show a popup message with "The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))"
This happens on old projects that have existing configuration files, as well as new projects without configuration files.
This is happening on multiple computers, is there a fix or workaround?
-- More information --
Operating Systems : Windows 8, Windows 8.1
Visual Studio Version : Microsoft Visual Studio Premium 2013 version 12.0.21005.1 REL
--Edit #2--
An Icenium update was just released, now on 2013.3.1219.1 and this error is still occurring...
Since the update to the Icenium extension for Visual Studio to 2013.3.1210.1, we have been unable to edit the configuration files for the projects. (android manifest, info.plist, config.xml)
Attempting to do so will show a popup message with "The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))"
This happens on old projects that have existing configuration files, as well as new projects without configuration files.
This is happening on multiple computers, is there a fix or workaround?
-- More information --
Operating Systems : Windows 8, Windows 8.1
Visual Studio Version : Microsoft Visual Studio Premium 2013 version 12.0.21005.1 REL
--Edit #2--
An Icenium update was just released, now on 2013.3.1219.1 and this error is still occurring...
3 Answers, 1 is accepted
0
Hello,
We were able to reproduce the issue. It is not related to Visual Studio version nor to the Windows version. It is reproducible when you add a configuration file from the Edit Configuration context menu and then delete the configuration file from the file system (outside Visual Studio) but not from the project itself. In this case the configuration file can be found in the Solution explorer and is marked with exclamation mark icon. To work around the problem, delete the orphaned node in the Solution explorer and add it again using the Edit Configuration menu.
Regards,
Ivan K. Ivanov
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
We were able to reproduce the issue. It is not related to Visual Studio version nor to the Windows version. It is reproducible when you add a configuration file from the Edit Configuration context menu and then delete the configuration file from the file system (outside Visual Studio) but not from the project itself. In this case the configuration file can be found in the Solution explorer and is marked with exclamation mark icon. To work around the problem, delete the orphaned node in the Solution explorer and add it again using the Edit Configuration menu.
Regards,
Ivan K. Ivanov
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
0
fr3dom
Top achievements
Rank 1
Rank 1
answered on 20 Dec 2013, 10:23 AM
Hi Ivan,
Unfortunately, this is also happening on a totally new, freshly created project, which has never had a config.xml or android manifest. (there are no files with an exclamation mark against them in the solution explorer is this, or the existing projects -- indeed, with the existing project, these files are visible in the solution explorer and editing them by double clicking on them works fine, but using the "Edit Configuration" menu commands fails with the above error)
I've created a new solution, and added the projects to it, some projects now allow the configuration to be edited from the menu, others still give this error.. There are no missing files, the only difference I can see is the length of the project name?
Is there some small limit to the length of the project name that Icenium can work with?
I have uploaded a test solution, with two projects here --> http://www.fr3domhealth.co.uk/TestSolution.zip
The project TestApp works correctly with the menu command to edit config.xml.
The project TestApp2 does not work correctly with the menu command to edit config.xml.
Both projects were created within a minute of each other, the only difference being the project name.
Is this me? Am I doing something wrong here?
Unfortunately, this is also happening on a totally new, freshly created project, which has never had a config.xml or android manifest. (there are no files with an exclamation mark against them in the solution explorer is this, or the existing projects -- indeed, with the existing project, these files are visible in the solution explorer and editing them by double clicking on them works fine, but using the "Edit Configuration" menu commands fails with the above error)
I've created a new solution, and added the projects to it, some projects now allow the configuration to be edited from the menu, others still give this error.. There are no missing files, the only difference I can see is the length of the project name?
Is there some small limit to the length of the project name that Icenium can work with?
I have uploaded a test solution, with two projects here --> http://www.fr3domhealth.co.uk/TestSolution.zip
The project TestApp works correctly with the menu command to edit config.xml.
The project TestApp2 does not work correctly with the menu command to edit config.xml.
Both projects were created within a minute of each other, the only difference being the project name.
Is this me? Am I doing something wrong here?
0
Hello,
I investigated the projects you sent me. You aren't doing anything wrong. I found an issue in adding/editing configuration files when there is more than one project in the solution. The issue is:
1) you adds a configuration file in one of the projects - works OK
2) then you try to add the same type of config file in the other project - fails with an error
I noticed that in your particular case this configuration file is under TestApp/App_Resources/Android/xml/config.xml. If you try to add the same file (using Edit Configuration context menu) in TestApp2 project, this results in error. However, if you try to add some of the other config files, it works fine.
You can work-around this situation by adding the corresponding config file manually by using the built-in Add Existing Item feature.
We apologize for the inconvenience. We have logged this issue in our bug tracking system and we'll provide a fix in an upcoming release.
Regards,
Ivan K. Ivanov
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
I investigated the projects you sent me. You aren't doing anything wrong. I found an issue in adding/editing configuration files when there is more than one project in the solution. The issue is:
1) you adds a configuration file in one of the projects - works OK
2) then you try to add the same type of config file in the other project - fails with an error
I noticed that in your particular case this configuration file is under TestApp/App_Resources/Android/xml/config.xml. If you try to add the same file (using Edit Configuration context menu) in TestApp2 project, this results in error. However, if you try to add some of the other config files, it works fine.
You can work-around this situation by adding the corresponding config file manually by using the built-in Add Existing Item feature.
We apologize for the inconvenience. We have logged this issue in our bug tracking system and we'll provide a fix in an upcoming release.
Regards,
Ivan K. Ivanov
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.