Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugger: Cannot specify configuration, that is debugger always loads ../bin/Debug/*/whatever.dll #538

Open
maxild opened this issue Jul 7, 2016 · 1 comment

Comments

@maxild
Copy link

maxild commented Jul 7, 2016

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.0-preview2-003121)

Product Information:
 Version:            1.0.0-preview2-003121
 Commit SHA-1 hash:  1e9d529bc5

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.11
 OS Platform: Darwin
 RID:         osx.10.11-x64

VS Code version:

1.2.1

C# Extension version:

1.2.1

I have some tests that fail only on osx and linux in release builds running on CoreCLR. I cannot get the debugger to attach to release artifacts in ../bin/Release/netcoreapp1.0/ folder.

I have to tried to make 'build' task only build configuration=Release. But 'codelens' run test and debug test, seems always to run tests with configuration=Debug. And I cannot get F5-debugging to work with this canonical './src/library', '/.test/library.tests' repo tree.

I have commited .vscode folder together with the rest of my code here

task 'failingtest' is a failing test (-method switch shows test method) that I cannot debug with the omnisharp debugger extension.

Related to #455, especially this comment

@DustinCampbell
Copy link
Member

Hi, it appears that this issue has gotten stale without a response from us. Our apologies!

It looks like you've mentioned a few issues above:

  1. Unable to get F5 debugging to launch on Release artifacts
  2. Unable to get "debug test" to work on Release artifacts

The second is issue is something we don't support today. However, I'm curious if you were every able to get the first issue working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants