Sorry for the general and (hopefully) simple nature of this question, but I can't find an answer to this for VS2017 anywhere.
The step-into (F11 on my machine) function seems to be broken for constructors. Does anyone know how to alter this unhelpful behaviour?
Update
I
must be missing an option in Visual Studio 2017 here. I have now noticed that step-over (F10) jumps not to the next line but to the next breakpoint.
I don't know if this has anything to do with it, but I have just found a load of stuff in the main WPF .csproj file that I don't recognise:
<Project ToolsVersion="14.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" Condition="Exists('$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props')" />
<PropertyGroup>
<Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
<Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
<ProjectGuid>{19445C4F-9102-4EDE-B898-6CEAEF581DD7}</ProjectGuid>
<OutputType>WinExe</OutputType>
<AppDesignerFolder>Properties</AppDesignerFolder>
<RootNamespace>DoddPMP.WPF</RootNamespace>
<AssemblyName>DoddPMP.WPF</AssemblyName>
<TargetFrameworkVersion>v4.5.2</TargetFrameworkVersion>
<FileAlignment>512</FileAlignment>
<ProjectTypeGuids>{60dc8134-eba5-43b8-bcc9-bb4bc16c2548};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
<WarningLevel>4</WarningLevel>
<AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
<PublishUrl>publish\</PublishUrl>
<Install>true</Install>
<InstallFrom>Disk</InstallFrom>
<UpdateEnabled>false</UpdateEnabled>
<UpdateMode>Foreground</UpdateMode>
<UpdateInterval>7</UpdateInterval>
<UpdateIntervalUnits>Days</UpdateIntervalUnits>
<UpdatePeriodically>false</UpdatePeriodically>
<UpdateRequired>false</UpdateRequired>
<MapFileExtensions>true</MapFileExtensions>
<ApplicationRevision>0</ApplicationRevision>
<ApplicationVersion>1.0.0.%2a</ApplicationVersion>
<IsWebBootstrapper>false</IsWebBootstrapper>
<UseApplicationTrust>false</UseApplicationTrust>
<BootstrapperEnabled>true</BootstrapperEnabled>
</PropertyGroup>
What I have tried:
If I put a breakpoint inside the constructor, this is hit okay.
I have already turned on the option to step into properties but can't find anything similar for constructors.
The code I am trying this on at the moment is in the WPF App() constructor, but I am pretty sure I have had no problems debugging from here on VS2015.
Update
Well, that is weird and more than a little worrying. Removing all the guff I have posted above from the project file gets the debugging working properly inside the constructor of a class created during application start-up but the debugging is still broken in the main App.xaml.cs file.