Bug 21349 - XMLNS on Shared Projects
Summary: XMLNS on Shared Projects
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Xamarin.Forms ()
Version: 3.3
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-07-15 18:08 UTC by Michel Chowanski
Modified: 2016-12-23 12:54 UTC (History)
5 users (show)

Is this bug a regression?: ---
Last known good build:

Screenshot (40.93 KB, image/jpeg)
2014-07-15 18:09 UTC, Michel Chowanski

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:

Comment 1 Michel Chowanski 2014-07-15 18:09:08 UTC
Created attachment 7377 [details]
Comment 2 Parmendra Kumar 2014-07-24 13:19:49 UTC
I have tried to reproduce this issue with following steps.
1. I create a Xamarin.Form Shared Project.
2. It Build sucessfull.
3. I get some error mesage in designer, because it does not find the namespace.



Microsoft Visual Studio Professional 2013
Version 12.0.30501.00 Update 2
Microsoft .NET Framework
Version 4.5.51641

Xamarin (48bc8a484441700b633a09133e208654bf62fa12)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android
Comment 3 Emanuel 2016-12-23 12:54:26 UTC
I couldn't reproduce this issue, and since we've added several improvements to Xamarin.Forms since the bug was reported, I'm resolving it tentatively as Fixed.
That said, if you're still facing this issue with current bits, please feel
free to reopen the bug.