-
Notifications
You must be signed in to change notification settings - Fork 44
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
Errors do not appear in error list #49
Comments
I have the same issue. |
If there's a way to get a tiny repro that demonstrates this, it'll help. |
ExampleApp.zip |
It appears to only happen when the xaml exists in a library output project and not in the executable output project. |
Was the example app I uploaded able to reproduce it for you locally? |
Any progress on this? |
I'm not sure if MSBuildSdkExtras can do anything about it. To me, it's the new project system not showing errors for projects it doesn't know anything about, and since the XAML compilation use a temp project for its first pass, we get this behaviour. |
I think I fixed with the recent commit on my PR. I checked with your repro. It's working as expected. @DanFTRX so, Can you check again (just for confirmation)? |
I'm getting this same issue with SDK 1.6.68, VS 15.9.7, .Net 472 |
I've managed to reproduce the issue with the sample project. It occurs when using the new style csproj: <Project Sdk="MSBuild.Sdk.Extras/1.6.68">
<PropertyGroup>
<TargetFramework>net472</TargetFramework>
<ExtrasEnableWpfProjectSetup>true</ExtrasEnableWpfProjectSetup>
</PropertyGroup>
<ItemGroup>
<Folder Include="Properties\" />
</ItemGroup>
</Project> I've opened this in a new issue: #157 |
Using VS 15.6.2
and the following project file
and the following code error.
the error does not appear in the error list. It appears if the intellisense source is used but not the build.
https://dl.dropboxusercontent.com/s/fwwj61z8g6h3bqg/2018-03-19_12-33-35.mp4
I can't send the entire project as it is not open source. If you need me to try create a fully standalone reproduction then let me know. Maybe it is obvious what the problem is from the description.
The text was updated successfully, but these errors were encountered: