I've installed VS15.7.1 Create a dummy UWP project targeting Build 10240.
With this configuration:
Execute the app.
Modify the text inside a button in the XAMl in VS.
Nothing gets reflect in the running app.
This used to work before. It's any kind of hidden setting or it's broken?
I I target version 1803 as in the photo XAML Edit & Continue works, but In 10240 it's broken:
This was finally a bug in Visual Studio that is going to be fixed soon in VS 2018 preview 3: https://developercommunity.visualstudio.com/content/problem/256287/xaml-edit-continue-broken-in-uwp-10240.html
Related
I am using Vs 2019 on Windows and Vs 2019 mac for the same Xamarin forms project. When I open project on VS 2019 mac, Android project has some auto changes on Droid.cs files and comparing what was changed is the result below in the image
You can see that in both debug and release configuration AndroidLinkSkip , EnableMultidex and enableProguard are removed.
Interesting part is that when i look at the UI on Options part, settings are checked there.
I am not able to revert those changes also. If i select revert changes, VS will check them out again.
What is the problem with VS 2019 mac?
EDIT: it looks like that latest update of VS2019 windows changed settings before it was called "enabled proguard" as in the screenshot from Mac. Now they call it as "Code Shrinker". This causes conflict between Vs2019 windows and Mac.
Beside I tried using this option only by removing old setting for proguard but it doesnt work. It throws exception. If i run it on VS2017 using old settings it works fine. I dont see any good documentation for this Breking change.
I have downloaded VS For Mac Preview and created a new Xamarin Forms IOS/Android Solution using the portable library. When i try and load the XAML designer though to view the startup page I get the error "Invalid XAML : default constructor not found for Xamarin.Forms.Applicaton". I have not made any changes to the project code generated by VS For Mac and the only thing I did was to build the Android project as this is required before the designer can be opened. I also had to download the latest versions of the Android SDK via the SDK Manager.
Does anyone have any idea what is wrong
Thanks
Steve
Firstly, there are two preview modes, one for iOS and one for Android - if you can't see both tabs, drag the frame over a bit. I can't currently get the Android preview to work right even though it builds, but for iOS to work it looks like you simply need to update the Xamarin.Forms package. Go to the 'Project' menu and select 'Update NuGet Packages.' Then, restart Visual Studio for Mac and it should be working. It is very slow to load, however. I had to rebuild my project and select 'Update NuGet Packages' a second time before it actually showed up.
I'm still trying to figure out why Android preview does not work.
I try to edit an axml file in Visual Studio, because drag and drop doesn't work in Xamarin Studio. But when I open my axml file, it's loading forever.
I've been waiting for more than 10 minutes, but it is still loading. When I restart VS I can open the axml file without any problems.
The same applies for all my other axml files (in other projects).
Does anyone knows how to fix this?
I'm using the newest stable version(cycle 8) of Xamarin btw.
EDIT:
I'm using Visual Studio Community 2015 Version 14.0.25425.01 Update 3 and I've got all the latest updates installed.
More detailed explanation:
I open my project in Visual Studio
I open my foo_bar.axml file
I switch from the Designer tab to the Source tab
I remove the android:background="blablabla" attribute
I switch from the Source tab to the Designer tab
The Designer tab is loading forever
AND
I open my project in Visual Studio
I open my foo_bar.axml file
I make some changes
I close the foo_bar.axml file
I reopen the foo_bar.axml file
the foo_bar.axml file is loading forever
NOTE:
The problem doesn't happen when I change the android:text="blablabla" attribute at step 4 and when I change some other attributes it also doesn't happen, so it is specific to just some attributes.
According to a forumer at Xamarin Forums, it has something to do with Cycle 8's AXML Designer not being able to render using the newest API.
But even in Cycle 8 when I choose to compile under Android 6.0 instead of 7.0 in the project's properties, the designer is still wonky as it is. Switch between "Designer" and "Source" on one .axml file and the designer still loads until Harambe cometh.
Therefore, your best bet is to downgrade Xamarin Studio to Cycle 7, and you can finally get the AXML Designer as working as before.
Until Cycle 9 or an incremental update/hotfix of Cycle 8 comes about, this is the way to go for now.
You can download and install the previous cycle in the link below:
https://store.xamarin.com/account/my/subscription/downloads#cycle7
For your own interest, you can read more about the aforementioned forum thread below:
https://forums.xamarin.com/discussion/77992/axml-layout-designer-inside-visual-studio-keeps-loading-forever
This happened to me also. Then I realised I hadn't opened Visual Studio in Admin mode. After I did, everything was fine.
Open the visual studio as admin and it loads perfectly. All the best.
I created a new android layout file using visual studio 2015 and am unable to view with the designer that is built in to visual studio.
After selecting 'design' tab, I just see a waiting icon in the center of the view and it never finishes. After a while, i have to close the design tab and open in xml editor. The form is valid as it runs fine in emulator.
ideas?
I was able to resolve after uninstalling all platforms using Android SDK Manager and re-installing each platform 1 by 1. If there is an issue with the installation nothing will be installed (note: watch the logs for errors and review after each platform is installed)
Initially, I did have to manually download SDK Manager and copy the tools folder to my existing installation. I am not sure why my Tools folder was empty but after performing this step I could again run SDK Manager.
Edit: the described issue below occurs also in a Win 10 UWP application (VS2015, Win10) when using the MapControl.
I have a weird problem using the MapControl in a Windows Phone 8.1 (universal app) application. After adding the control to a page, Visual Studio says The name "MapControl" does not exist in the namespace "using:Windows.UI.Xaml.Controls.Maps". Building the app works, I can deploy it to the phone and the map is shown and everything is fine - but I cannot use the Designer for this page any longer since it claims that error.
The problem occured in a bigger project originally started in VS2013 (update 4) on Windows 8.1. My first thought was that my VS-installation was kind of broken. But also after a clean new installation of Windows 10 (10240) and VS2015 RTM the problem occured. My steps to reproduce are quite simple:
Create a new project from template "Blank App (Universal Windows 8.1)"
Open the MainPage.xaml of the WindowsPhone subproject
Double click the MapControl in the toolbox
Note that the MapControl is added to the Grid in xaml and it is shown in side-by-side design view. Everything seems to be ok.
I can now add more controls to the page just by clicking the toolbox. I can modify the controls on the page with the mouse in the designer (e.g. rearrange them) and I can change their properties by the properties pane. Everything is still ok.
But when I either close and reopen that page (or the whole project) in the designer or when I start to edit the xaml directly with the keyboard, the designer fails and claims the error described above.
What's the problem here? How can I make Visual Studio designer to work with pages with MapControls again? First I thought of a bug in VS2013 - but that simple to reproduce, not fixed in VS2015 and no information about it on the internet? What did I wrong?
There is a bug on Visual Studio Tools for Universal Windows Apps 1.0 causing this issue with the map, installing this update should fix the issue Update
Procedure to correctly use the map sdk
Windows 8.1
Go to Tools-> extension and update -> install Bing Map SDK.
Right click on the project->Add reference->Windows->Extensions->Bing maps
Set configuration to x86 (Configuration Properties -> Configuration)
Add the map reference to your page using xmlns:maps="using:Bing.Maps"
Adding this line to your xaml <maps:Map />
and now you are good to go
Windows Phone and Windows 10 UAP
Add this reference in your xaml
xmlns:maps="using:Windows.UI.Xaml.Controls.Maps"
and then add this line to your xaml
<maps:MapControl />
Set configuration to x86 instead of "Any CPU". For prioritising fix upvote at https://connect.microsoft.com/VisualStudio/feedback/details/1659249/visual-studio-2015-rtm-uwp-the-name-mapcontrol-does-not-exist-in-the-namespace-using-windows-ui-xaml-controls-maps
Make the correct map library reference
xmlns:Maps="clr-namespace:Microsoft.Phone.Maps.Controls;assembly=Microsoft.Phone.Maps"
Instead of
xmlns:Maps="using:Microsoft.Phone.Maps.Controls;assembly=Microsoft.Phone.Maps"