Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 VA 2385: rename file issue

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
Uniwares Posted - Aug 20 2020 : 11:29:02 AM
when renaming a file with VA in a C# .NET Core project I get the following message:

---------------------------
Visual Assist
---------------------------
No project association was identified for C:\Users\...\_SimpleAction - Copy.cs.

Do you want to continue the rename operation anyway?
---------------------------
Yes   No   
---------------------------


Confirming Yes, works as expected. But message comes always.
10   L A T E S T    R E P L I E S    (Newest First)
feline Posted - Aug 25 2020 : 07:03:21 AM
Thank you for the video, I am now able to reproduce this here on demand:

case=142813

it turns out that the bug is a little "fragile" in VA 2382, if you interact with the new file a little bit, as I must have been doing in my tests, you don't get the message box. But if you rename immediately then you do get the message box.

The message box was a lot easier to trigger in VA 2385, the internal build.
Mnemonic Posted - Aug 25 2020 : 02:42:20 AM
Yup, same versions. No idea why it should work differently, it does indeed seem pretty straightforward: http://dead-code.org/misc/vax.mp4
feline Posted - Aug 24 2020 : 1:38:37 PM
I still cannot reproduce this here. I am using VA 2382.0 built 2020.06.25
Visual Studio 2019 version 16.7.2

Are you using the same version numbers, or different version numbers? I am not sure why you should be seeing this but I am not, not when the steps to reproduce this are nice and clear.
Mnemonic Posted - Aug 22 2020 : 07:34:41 AM
I'm using 2382, actually, and still getting this.
feline Posted - Aug 21 2020 : 10:12:19 AM
I was testing a different version still.

This has been fixed in the latest internal builds.
Uniwares Posted - Aug 21 2020 : 09:35:49 AM
2385.6
feline Posted - Aug 21 2020 : 09:34:12 AM
Seeing the same problem here, happening in VA 2385.0, not happening in release version 2382.0, which is why I didn't pick it up at first.

Are you both using 2385.0, or a different point build?

Looking into why now...
Mnemonic Posted - Aug 21 2020 : 07:39:43 AM
I'm getting this error as well. SDK-style csproj.

EDIT: I was able to repro it easily:
1) create a new project (Console .NET Core)
2) add a new class Class1
3) Use Rename files... command to rename class1.cs to something else

Could it be related to this still-unfixed super-annoying bug? https://forums.wholetomato.com/forum/topic.asp?TOPIC_ID=16705
Uniwares Posted - Aug 21 2020 : 06:53:43 AM
Hmm, do you still have my solution? Try with it if you have it. Might be the project config.
feline Posted - Aug 21 2020 : 06:51:16 AM
So far no sign of this message. I am testing VA 2382.0, VS2019 in a new, simple C# .NET Core console project.

I am sitting in a .cs file, with keyboard focus in the code file, and triggering:

VAssistX -> Code Generation and Refactoring -> Rename Files...

I get the rename dialog, set the new file name, accept it, and the file is renamed.

© 2019 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000