Microsoft Visual Studio Professional 2022 Version 17.0.4
Starting from scratch a "Multi-Platform App (Uno Platform|net6)" project, closing the solution and reopening it, the "mobile" project is listed as "incompatible".
It happened to me on two different computers.
I run the "uno-check" and after installing the missing parts it tells me that everything is ok, but when I load the solution the mobile project continues with the same error.
Any idea?
The .NET 6 mobile project template is only supported on Visual Studio 17.1 Preview 1 and later.
I leave the link where he explains that the problem is in the manifest of the packages.
[https://github.com/unoplatform/uno/discussions/7833][1]
Related
I just newly installed Visual Studio Comunity 2019, and I tried to start a new ASP.NET MVC project. However, I can't seem to find the Browser Button. https://imgur.com/ajtDatf
I mean the one where you can choose with which Browser (IE, Chrome, Mozilla, etc) do you want to run your project. Does anyone know how to fix this.
I'm in Germany and Visual Studio is also in german.:D
Thank you for your help.
So, aparently I get this issue when I'm forking from a Repo from Github. If I close and reopen the Visual Studio after the fork, the problem is solved.
So far, It happend only with two repos. The thing is that I borrowed a new laptop and installed the Visual Studio 2019 on it. Never had this issue before on my old PC.
Feels good fixing your own issues. :D
We have a Xamarin.Forms project that was created a couple of years ago and after upgrading to the latest build of Visual Studio 2019 (16.2) we are getting nearly 100 errors like the following when building the android version of the project: error: package com.google.android.gms.common.api.GoogleApiClient does not exist
I checked with a colleague who was using Visual Studio build 16.1.3 and the android project built fine but after upgrading their Visual Studio 2019 to the 16.2 build they now get the same problem too. The iOS project continues to build fine.
Does anyone have any suggestions on what to try? I found a bunch of older posts that suggested adding items in the Android SDK manager but none of these changes helped me.
Failing that does anyone know of a way for me to revert my Visual Studio install back to 16.1.3?
Have you updated all NuGet packages? Did it help to move to VS 16.3.5? Have you checked the dependencies of your NuGet packages?
I am having issues with an activity being placed outside of application. It seems like the Google Ads/Admob implementation in Xamarin apps is a source of troubles. Net Core version also seems like a good place to check for a solution.
I have VS2015 and VS2013 installed side-by-side. In VS2013 I have a list of emulators to start my app and it works awesome.
But VS2015 only has device in the list. How do I add the phone emulators to Visual Studio 2015?
UPDATE:
After playing around some more I've dug up some new findings.
Creating a new universal JavaScript project has the same issue
Creating a new universal C# project DOES show a list of emulators.
This worked for me!
Although I had CoreCon\12 and vs2015.3 instead of CoreCon\11 and vs2012
Maybe you could fix this issue by deleting this folder
C:\Users\\AppData\Local\Microsoft\Phone Tools\CoreCon\11.0
Then open VS2012 again.
If not repairing is always recommended
original post : no-emulator-lists-to-deploy-windows-phone-app
Rerun the installer. Make sure that the desired options are checked (probably either Windows Phone 8.1 Emulator or Microsoft Visual Studio Emulator for Android, you don't say which emulator you are interested in). If in doubt, just check everything.
If you had unloaded your start project, it may not be your start project anymore after reloading. So do a right click -> Set as Startup Project and then hopefully the emulators will reappear.
I am unable to open CSS files in Visual Studio 2010 after adding to a project.
It shows the following error:
The operation could not be completed.Unspecified error.
Even if I try to edit embedded CSS in a webpage directly, IntelliSense doesn't appear.
I found the solution from here:
I was having the same issue and found that by going to the Tools -> Extension Manager -> Online Gallery and search for/install the "Web Standards Update for Microsoft Visual Studio 2010 sp1" I was able to open CSS files again.
And it worked for me.
Probably it can happen after installing the Visual Studio LightSwitch beta
OR
Windows Azure tools installed
OR
SQL Server 2012 installed
Download this and install it if already installed then repair it and it'll fix the issue:
http://visualstudiogallery.msdn.microsoft.com/a15c3ce9-f58f-42b7-8668-53f6cdc2cd83
This happened to me after installing Adobe Cloud production suite. Web Standards Update did the trick.
There is dropdown box in the toolbar saying "XHTML 1.0 transition". Change it to HTML.
I'd like to understand the proper way to build the MVVM toolkit from the source files on codeplex for a WP7 sample app. I've got the source associated with codeplex changset 47157 by lbugnion Apr 18 at 10:42 AM 1300 associated with Release: MVVM Light Toolkit V3 SP1 (2).
I've got VS2010 and Windows Phone Developer tools installed. I see the VS10 dir that presumably contains the VS2010 solution files. Do I just open that .sln file in VS2010 and build all? The distributed binaries contain versions of the dlls suffixed with WP7. I don't see those version of the dlls generated when I build the VS10 solution file.
Thanks,
Peter
There seems to be a problem with the WP7 bits. Unfortunately they are missing from the VS10 folder and are instead in the old GalaSoft.MvvmLight folder. Plain and short, I messed up. The "old" folder was historically the root. When I added projects for SL4 and WPF4, I did so in the VS10 subfolder (not my brightest idea). And when I added WP7, I apparently did so in the wrong folder. This is really weird.
I have a flaky internet connection in the moment (I am on the road) so I won't be able to fix the issue before a couple of days. I made a note and will fix the CodePlex code base ASAP. More info will be given on my blog http://blog.galasoft.ch.
Cheers,
Laurent
If you're using Visual Studio 2010 the solution you should open is source\VS10\GalaSoft.MvvmLight\GalaSoft.MvvmLight.sln. The Silverlight projects may not open if you don't have the Silverlight Tools for Visual Studio installed. Don't worry about this if you're only building the WP7 version of the toolkit assemblies. The solution structure is confusing at first because it uses linked file references.
Actually, now that I look at the VS10 solution, it doesn't look like there are any WP7 files under the structure. I think you're correct, and the Visual Studio 2010 solution doesn't build the Windows Phone 7 assemblies.