Skip to content

Error on debugging my website #1445

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.

Sign up for GitHub

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

Jump to bottom
Closed
kermitfrosch opened this issue May 16, 2016 · 3 comments
Closed

Error on debugging my website #1445

kermitfrosch opened this issue May 16, 2016 · 3 comments

Comments

@kermitfrosch
Copy link

Hallo,

when i debug my Website and set a breakpoint i can't watch my variables.
I got the error:
error CS0103: The name 'model' does not exist in the current context

See Picture attached.

How can i fix this.
thx

Jens
error
@Tratcher
Copy link
Member

Is the code running as Release / optimized? Local variables like this may be removed by optimizations. Try running under Debug instead.

@moozzyk
Copy link
Contributor

moozzyk commented May 16, 2016

I think this is a bug in VS - see: http://stackoverflow.com/questions/36284093/visual-studio-2015-update-2-rtm-and-rc-debugging-context-not-available

@aspnet-hello
Copy link

This issue is being closed because it has not been updated in 3 months.

We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.

natemcmaster pushed a commit that referenced this issue Oct 17, 2018
@mikeharder
Add Linux, Node8, and Node10 to test matrix (#1445)
9c37082 
- Test both Node8 and Node10 on Windows and Linux
- Only test Node8 on MacOS, since the ASP.NET Core 2.1.X templates are incompatible with Node10 on macOS
  - aspnet/Templating#608
- Move Windows build to "Hosted VS2017" pool which has more agents
  - We would rather use the "Hosted" pool, but "npm restore" currently fails on agents in this pool
- Remove "Preview" from Mac pool name
natemcmaster pushed a commit that referenced this issue Nov 14, 2018
@davidfowl
Use ascii decoding routine that disallows null chars (#1445)
da763b4 
* Use ascii decoding routine that disallows null chars
- GetAsciiString() in newer corefxlab builds allows 0 (which is a valid
ascii char). To avoid future regressions, GetAsciiStringNonNullCharacters()
was added and used in place of GetAsciiString() when interpreting the
request line and headers
- Make GetAsciiStringNonNullCharacters return empty instead of null
ryanbrandenburg pushed a commit that referenced this issue Nov 27, 2018
@BrennanConroy
Logging invocations with errors would throw inside logger (#1445)
d9b32ee
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@moozzyk @Tratcher @kermitfrosch @aspnet-hello