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

XamlMarkup-Sample shows error in designer #279

Closed
Urmeli0815 opened this issue Nov 19, 2017 · 8 comments
Closed

XamlMarkup-Sample shows error in designer #279

Urmeli0815 opened this issue Nov 19, 2017 · 8 comments

Comments

@Urmeli0815
Copy link

When trying to open MainPage.xaml of the XamlMarkup-Sample from kennykerr/cppwinrt I get the error "Visual Studio requires a newer version of Windows to display this content. Please update to UAP (10.0.17025.0) or later."

Will this be fixed when the XAML-Compiler will be available in cppwinrt?

BTW thanks to Kenny for the nice collection of samples and the minimalism/purity of them: only C++ and the UWP. No .NETCore thrown into the mix which makes it difficult to grasp which component comes from which technology.

@rvinothrajendran
Copy link

Build 17025 for Windows insider , Are you using 16299 build ? Its is yes ,Use the 16299 samples or upgrade to windows insider build

@Urmeli0815
Copy link
Author

I tried that but without success. Now I get "Some assembly references are missing". I think the XAML-Designer needs some .NET-Assemblies to work.

@rvinothrajendran
Copy link

Please share the error details

@Urmeli0815
Copy link
Author

When I double-click on MainPage.xaml from the XamlMarkup-Example the designer window opens but only this text appears:

"Some assembly references are missing.
Building to restore the NuGet cache might resolve this issue."

Environment:

  • Visual Studio Community 2017 (15.4.4)
  • Windows 10 (Build 17040)
  • Target Platform Version 10.0.17035.0

@Scottj1s
Copy link
Member

Does the build output indicate which references are missing? You can set build verbosity via Tools | Options | Projects and Solutions | Build and Run. You can also, per the suggestion, right click the project node and select "Manage NuGet Packages...", which will both confirm whether you have an outdated package, and provide the means to update it. Finally, you may be able to simply edit all target version references in the sample's *.vcxproj file, and replace them with 16299, or whatever version will resolve the project's dependencies.

@Urmeli0815
Copy link
Author

I tried all of your suggestions but the problem stays the same. I attached a screenshot of how it looks like.

xaml_markup_error

As you can see the XML-Elements in the designer have these squigglies underneath them and the tooltip says "The type 'TextBlock' was not found. Verfiy that you are not missing an assembly reference and that all referenced assemblies have been built."

@kennykerr
Copy link
Collaborator

This is currently unsupported. The XAML team is currently working on designer support, so you should see this light up in a future update to the Windows SDK.

@terriblememory
Copy link

@kennykerr Are we any closer to having this working? And if not do you know of any good workarounds? I'm pretty much useless without autocomplete and some kind of previewer really helps keep the cycle time down...

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

No branches or pull requests

5 participants