With VS 2022 v17.14 the slnx format is no longer in preview.
I made a quick test:
dotnet sln migrate
When I open NCrunch I must re-enable it because the NCrunch file name is now different.
Old file name (with sln) Solution.v3.ncrunchsolution
New file name (with slnx) Solution.slnx.v3.ncrunchsolution
It is not even a problem cause renaming the file makes everything work like before, but I find it a little inconsistent to strip the extension in once case but not the other.
I think stripping the slnx from the name would make the user experience way better
It isn't supposed to work this way .. it's supposed to strip the .slnx just like it does the .sln. I'll see about getting this fixed. Sorry for the trouble.
I've prepared a build containing a fix for this, if you're interested in giving it a try? Note that you might need to rename your config files again (they shouldn't have .slnx in the name).
When we use your attached version **5.15.0.3**, we don't encounter the issue. However, if we use the current versions **5.15.0.4** or **5.15.0.5**, the bug reappears.
Can you confirm 100% whether downgrading to 5.15.0.3 resolves the issue? The fix for this problem was rolled into the 5.15.0.4 build on the download page. If you're experiencing this problem with the latest build, my suspicion is that there may be an element here that hasn't been fully fixed, or a component that hasn't been considered (like a stray file)
I apologize for the delayed response. I've been trying to reproduce the issue over the past few days but haven't been able to find a straightforward, reproducible case.
I now suspect it might be related to older .user files. All my solutions were migrated from .sln to .slnx, and NCrunch was already running with the .sln files back then, which also created .user files with the previous settings.
Could this be a reason for the strange behaviour?
ariupper wrote:I apologize for the delayed response. I've been trying to reproduce the issue over the past few days but haven't been able to find a straightforward, reproducible case.
I now suspect it might be related to older .user files. All my solutions were migrated from .sln to .slnx, and NCrunch was already running with the .sln files back then, which also created .user files with the previous settings.
Could this be a reason for the strange behaviour?
It's difficult to say. The system is designed so that it can work with either .slnx or .sln files, so if both happen to exist, one will end up taking precedence.
I'm confident that the .slnx support is in all newer versions of NCrunch. But it's still new. I have a feeling you may have stumbled onto an edge case that gives unexpected behaviour. If you manage to pin it down, please do let me know.