Move to Resource-Warning: Cannot move element to resource

Hi,

I'm trying to use the "move to resource" function in R# 6.0 build 2144. I get a warning, that says "Cannot move element to resource" and I don't see any reason why R# can't do this.
The string is added to the resource file and in the Resource.Designer.cs the Property is created. The only missing stepis the replace the string with the Property.
Is this a bug or a feature?

Greets
JT

11 comments

Hello,

Does this happen with any solution (even in a newly created win forms project)?
Could you please attach a screenshot of the error message? Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi,

I'm trying to use the "move to resource" function in R# 6.0 build
2144. I get a warning, that says "Cannot move element to resource" and
I don't see any reason why R# can't do this. Is this a bug or a
feature?

Greets
JT
---
Original message URL:
http://devnet.jetbrains.net/message/5301765#5301765



0

Hi,

Move to resource does not work for me either.

See http://youtrack.jetbrains.net/issue/RSRP-260651

Henning

"Andrew Serebryansky"  wrote in message
news:c8a898dd1033e8cdd48a48886a57@news.intellij.net...

Hello,

Does this happen with any solution (even in a newly created win forms
project)?
Could you please attach a screenshot of the error message? Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi,

>

I'm trying to use the "move to resource" function in R# 6.0 build
2144. I get a warning, that says "Cannot move element to resource" and
I don't see any reason why R# can't do this. Is this a bug or a
feature?

>

Greets
JT
---
Original message URL:
http://devnet.jetbrains.net/message/5301765#5301765


0

The latest build I see is 2151. Do you mean this one? In this build I still get the error.

0

The 2151 build does not have fixes for it. Waiting the next EAP build...

0

I paid for 2017.2.2 yesterday just to have this silly issue of Move to Resource-Warning: Cannot move the element to resource kills me.

I download 2017.3 EAP 4 and still the same issue it just does not work I think I will have to ask for a refund since 2017.3 EAP 4  is now expiring in the next 28 days what is this seriously.

 

I know that I'm, not a perfect coder that is why I like your idea with resharper could be a great tool but hey you sell your software and people pay for it, sort it since you market is with all the great descriptions and explanations but it is just not working at the moment I can do it faster by manually coding than trying to use resharper. I recommend using an example of a before and after state will help anyone.

 

Ok, the thing I so badly missed is that I had to select the actual resource file. This small bit of detail can help a lot if it is mentioned in the error message instead of just saying "the resource cannot be moved" I mean 3 days flat just for this.

I will revert back to 2017 2.2 so I can benefit of my money spent, just have to live with performance issues now in VS.

0

Hello Freddie!

 

Please accept our sincere apologies for delay in responding and for inconvenience you've experienced.

We'll do our best to improve usability when working with resources.

Please let us know if you experience any other problems, specifically performance issues. Possibly we could help in this case.

Thank you.

0

So it's not only that it doesn't work on a blank, brand new project, but it shows that you don't care: what conflicts? What should we fix in "cannot move"? Why is it just "cannot do it" - any reason? It does not work in any other projects either. VS2017 community, latest r# ultimate - but didn't work with the previous either.
Please concentrate on fixing it rather than increasing the number of politically correct lies used in your messages like "sincere" "apology", "we do our best" - this just makes us upset: yeah, so we know that it's not sincere, that you're not doing your best. Be honest, treat us as partners and don't bullshit.

0

Hello Kovrob!

 

Thank you for the feedback.

Could you please specify if any tool is set to resource file in Properties window | Advanced | Custom tool?

Is there any chance you could provide some  solution demonstrating the problem?

Thanks in advance.

0

Nah, no custom tool.
The problem happens with the most basic solution as well: Start VS2017, create a new solution by using the "Windows Forms App (.Net Framework)" template, double click on the form, insert 'MessageBox.Show("Dis");', then Alt+Enter on "Dis", choose the "Move to resource", accept defaults - and then voila, the above.
In the solution where it matters for me it adds the resource to the incorrect .resx file (maybe the first one in the project?) - so not to the one belonging to the control - but then I get the same error. In this default one nothing seems to be added to the .resx file.

Well, I can provide the zipped up solution, but it's really just the above.

0

Please sign in to leave a comment.