I dont believe so, I think you just set the normal asp.net debug mode in web.config

Note: I tried in 2 different solutions, same issue.

The customerros settings should be fine, like i use to have them set:

<customErrors mode="Off" />
<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" />

What is the issue exactly then?

I cant seem to enter debug mode, like i normalty would. 
I also tried to set debug to true in compilation and the settings for trace  in web.config to no avail.

I'm having trouble with it too. Clean install of Umbraco 7.0.0 via nuget into an empty MVC solution in VS2012. 

I added <add key="umbracoDebugMode" value="true" /> to the appSettings.config and it is not working.

That's because in MVC trace doesn't work. See this blog post: http://umbraco.com/follow-us/blog-archive/2013/5/10/umbraco-610-beta-2-out-now!.aspx

"Many people noticed that in Mvc mode, Umbraco can't give you tracing any more, which made finding bugs and performance issues harder."

Have a look at the MiniProfiler alternative in that blog post.

Jeroen

I am not using MVC, but webforms, does that make difference?

Thanks Jeroen. I was able to see the MiniProfiler by setting the compilation debug attribute to true in the web.config and adding ?umbDebug=true to the URL.

This looks even better and more useful than the old Asp.Net Tracing.

is working on a reply...