Bug 38565 - After adding a UWP project, VS2015 reports 'Error Cannot create an instance of "WindowsPage"'
Summary: After adding a UWP project, VS2015 reports 'Error Cannot create an instance o...
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.0.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-02-09 08:16 UTC by John Hardman
Modified: 2016-12-21 17:38 UTC (History)
5 users (show)

Tags: VS Visual Studio 2015 designer xaml UWP
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description John Hardman 2016-02-09 08:16:25 UTC
As per part of the discussion thread at https://forums.xamarin.com/discussion/comment/179526#Comment_179526
after adding a UWP project to a solution (following the instructions precisely), the VS2015 (Enterprise) designer (error window) is showing:

Error Cannot create an instance of "WindowsPage". 
at line 1 of MainPage.xaml

It doesn't appear to stop the app being built, but shouldn't happen anyway.
Comment 1 credoandjeroen@hotmail.com 2016-04-10 16:13:23 UTC
I can confirm this bug.

Stacktrace:
 at Microsoft.VisualStudio.DesignTools.Platform.InstanceBuilders.InstanceBuilderOperations.InstantiateType(Type type, Boolean supportInternal)
   at Microsoft.VisualStudio.DesignTools.Platform.InstanceBuilders.ClrObjectInstanceBuilder.InstantiateTargetType(IInstanceBuilderContext context, ViewNode viewNode)
   at Microsoft.VisualStudio.DesignTools.Platform.InstanceBuilders.ClrObjectInstanceBuilder.Instantiate(IInstanceBuilderContext context, ViewNode viewNode)
   at Microsoft.VisualStudio.DesignTools.WindowsXamlDesigner.InstanceBuilders.FrameworkElementInstanceBuilder.Instantiate(IInstanceBuilderContext context, ViewNode viewNode)
   at Microsoft.VisualStudio.DesignTools.WindowsXamlDesigner.InstanceBuilders.UserControlInstanceBuilder.Instantiate(IInstanceBuilderContext context, ViewNode viewNode)
   at Microsoft.VisualStudio.DesignTools.Platform.InstanceBuilders.ViewNodeManager.CreateInstance(IInstanceBuilder builder, ViewNode viewNode)
Comment 2 Paul DiPietro [MSFT] 2016-12-21 17:38:23 UTC
I don't believe this is occurring any more (and might not have specifically been a Forms issue) so I'm marking it as resolved. If I'm mistaken here, please feel free to reopen this with a reproduction that still throws this error.