Bug 56959 - Buggy IDE VS2017 latest everything FORMS and template ADD listviewpage to PCL and try it in the PREVIEWER -EXCEPTIONS ALL OVER
Summary: Buggy IDE VS2017 latest everything FORMS and template ADD listviewpage to PCL...
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Xamarin.Forms Previewer ()
Version: 4.6.0 (15.3)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-05-30 13:56 UTC by Stanley Broo
Modified: 2017-06-21 20:53 UTC (History)
6 users (show)

Tags:
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 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 Stanley Broo 2017-05-30 13:56:07 UTC
Buggy IDE VS2017 latest everything FORMS and template ADD listviewpage to PCL and try it in the PREVIEWER -EXCEPTIONS ALL OVER

DEBUG IS BEING USED BY ANOTHER PROCESS?
COULD NOT FIND LISTVIEWPAGE CLASS??
Comment 1 Stanley Broo 2017-05-30 13:58:08 UTC
REPRODUCE

1. START A NEW PROJECT
2. ADD A ListView page
3. open previewer

exceptions...
Comment 2 Alan McGovern 2017-06-21 20:53:06 UTC
We addressed a similar issue and that fix will ship with a future release.

If you can attach log files from your IDE after triggering the issue we can use that to verify that we did fix the precise issue you're seeing.

Thanks for reporting this!