I installed Android Studio on the same PC as Xamarin. I wanted to use the same adb as Visual Studio in Android Studio.
(android-sdk path is an option on the initial install screen, but I had to use mklink to get around the fact that VS installs Android sdk at Program Files (x86) - Android Studio doesn't like non alphanumeric characters.
When I returned to Xamarin I could no longer compile, this seemed to be the main error:
C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1183,2): error MSB6006: "aapt.exe" exited with code -1073741819.
Luckily I kept a backup of this folder first, and reverting it did help
c:\Program Files (x86)\Android\android-sdk
Others might need to reinstall Xamarin after deleting / renaming android-sdk folder.
In addition to reverting this file I also had to clear the contents of
MyProject\MyProject.Droid\Resources\Resource.Designer.cs
This file isn't visible in VS, but you can get to it if there are errors to click on.
Don't forget to clean before build.
Related
I'm attempting to install DotVVM in Visual Studio 2019. Right now I can find it when I 'manage extensions' and it downloads and installs without error. However when I restart Visual Studio post installation I get an error stating 'The DotVVM package did not load correctly' and points me to an xml output file. The contents of said file shows:
SetSite failed for package [DotvvmPackage]
Source: System.ComponentModel.Composition
Description: The composition produced multiple composition errors, with 3 root causes. The root causes are provided below. Review the CompositionException.Errors property for more detailed information
No exports were found that match the constraint: ContractName DotVVM.Integration.VisualStudio.Dialogs.DialogFactory RequiredTypeIdentity DotVVM.Integration.VisualStudio.Dialogs.DialogFactory Resulting in: Cannot set import DotVVM.Integration.VisualStudio.VsPackages.DotvvmPackageDependencies.DialogFactory (ContractName='DotVVM.Integration.VisualStudio.DialogFactory') on part DotVVM.Integration.VisualStudio.VsPackages.DotvvmPackageDependencies.Element: DotVVM.Integration.VisualStudio.VsPackages.DotvvmDependencies.DialogFactory (ContractName='DotVVM.Integration.VisualStudio.Dialogs.DialogFactory') DotVVM.Integration.VisualStudio.VsPackages.DotvvmPackageDependencies
No exports were found that match the constraint:
Pretty much the same error except it's talking about 'DotVVM.Integration.VisualStudio.Common.Licensing.ILoginProvider'
No exports were found that match the constraint:*
Same error except it's talking about 'DotVVM.Integration.VisualStudio.Services.CommandService'
Now I have been trying to find other topics and came across many that said to delete (or rename) the '%appData%'/Local/Microsoft/VisualStudio/16.0/ComponentModelCache' folder which I've tried with no luck. Removed it out of every VisualStudio version folders as well. Restarted Visual Studio of course after. That folder did rebuild itself but I got the same error again.
I've also tried uninstalling and reinstalling it as well. Tired with running Visual Studio as an admin for kicks. Even downloaded the DotVVM.Integration.VisualStudio.2019.RTM.vsix file directly (both 4.0.534 and 4.0.539) and installing it that way with no luck.
I also tried fully uninstalling and reinstalling Visual Studio 2019 all together with no luck. I made sure the entire VisualStudio/16.0 folder was also gone between installs.
I have been able to install other extensions alright just to see.
It seems like I'm missing something or some files when it's trying to install, but I can't figure out what. Any ideas?
Turns out my version of Visual Studio was the issue. My cooperate environment locks me to 16.10.2 which is not the latest version. Visual Studio updates claims I'm up to date but I am not.
The version of DotVVM (4.0.539) doesn't support version 16.10.2 of visual studio, hence the error. I did find an older version of DotVVM (2.5.254) that does support that version of visual studio and that worked fine.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(373,3): warning MT0178: Debugging symbol file for '/Users/appledevelopment/Library/Caches/Xamarin/mtbs/builds/XamAppHartzSystems.iOS/831856682f36592c89c1d1be72305370c507305528b30a6064078e5ddad8b0d1/bin/iPhoneSimulator/Debug/XamAppHartzSystems.dll' is not valid and was ignored.
Getting this warning in my build process. The build completes without errors.
The build is for a Xamarin iOS project that was working before I updated xcode and visual studio 19 to latest versions.
When I try to put a brakepoint in my shared library, it will not stop in the debugger due to the above warning.
I have tried to clear all the obj and bin folders, but that does not help.
I can't seem to find why it thinks the symbol file is invalid.
Windows VS is up to date
Mac xcode is up to date
Mac VS is up to date
Using Xamarin Forms 4.8.1821, tried the latest version too with no luck.
How do I find out why my symbol file is invalid...
Answer: Somehow in the Library Build Settings, the Debugging information was set to Pdb-only. I changed it to Portable and it fixed the problem.
It happened to a few of my projects after upgrading to the latest VS and xcode.
I got the exact same problem posted here:
Attempting to Install an extension to VS2019 results in a NullReferenceException
Same error, same log.
But since I cannot comment nor answer and the question has not been answered as of yet, I'm asking again.
I am using VS2019 Community, but I had VS2017 Enterprise at one point. (student license)
Every single extension I tried to install so far has led to this error. For example "Live Share", "Open Command Line", "Github Extension for Visual Studio", "Markdown Editor".
I believe it started with Live Share when suddenly an update wouldn't install for no reason. I guess that was back with VS2017 even. But I cannot recall, I just assume. With the newly installed VS2019 I was never able to install any extension via the in-app Extension feature, nor by downloading with browser and then trying to open it.
What I've tried:
0) Every suggestion by Perry Qian-MSFT
1) Repairing Visual Studio 2019
2) Reinstalling Visual Studio 2019
3) Uninstalling "Live Share"
4) Deleting various Folders or contents thereof:
C:\Users\Admin\AppData\Local\Microsoft\VisualStudio
C:\Program Files (x86)\Microsoft Visual Studio\2017 (trying to get rid of any remnants)
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\Extensions
Next I'll deinstall as much as possible: VS2019 and Installer and try to see what's left, what could have remained that causes such pain in the a***.
But since my internet will be busy with reinstalling afterwards for a while this question goes up now.
Update1: The installer made some problems getting uninstalled. Deinstallation via Windows Software Management failed with an error but it was still removed from the list. Now I've deleted the folder and will try and reinstall the installer. I don't know why I didn't try that before throwing it all over board.
Update2: I decided to start with a simple barebones VS2019 version without any workloads. But it still doesn't work. So back to throwing everything out and looking for the remainder.
Update3: I now tried to delete various folders then reboot and tried to reinstall a barebone VS 2019 Community again. Still same error.
Here's a list:
C:\Program Files (x86)\Microsoft Visual Studio Tools for Unity
C:\Program Files (x86)\NuGet
C:\Program Files (x86)\MSBuild (except for .\Microsoft\Windows Workflow Foundation)
C:\Users\Admin\AppData\Local\Microsoft\VisualStudio Services
C:\Users\Admin\AppData\Local\Microsoft\VisualStudio\Packages
C:\Users\Admin\AppData\Roaming\Microsoft\Microsoft Visual Studio
C:\Users\Admin\AppData\Roaming\Microsoft\VisualStudio
C:\Users\Admin\AppData\Roaming\Visual Studio Setup
C:\Users\Admin\AppData\Roaming\vs_installershell
C:\Users\Admin\AppData\Roaming\vs-report-problem
C:\Users\Admin\Documents\Visual Studio 2013
C:\Users\Admin\Documents\Visual Studio 2017
C:\Users\Admin\Documents\Visual Studio 2019
Oddly enough my personal settings are still persistent. So these will be my next target. But where are they stored? Any pointers?
Update4: Seems like settings are stored in a cloud, hm. I made a local backup and tried to reset them resulting in yet another error.
Your settings were reset, but there were some errors.
Error 1: An error occurred while importing settings for 'Product Updates' [code 5396].
Was this 'Product Updates' Setting the culprit?
Update5: The settings reset didn't seem to accomplish anything at all.
Update6: So, I've signed out of VS, reinstalled VS2019 again and this time it seems like settings were actually reset. Still no luck. This is getting really frustrating.
That's it. I'm done. Apart from reinstalling Windows 10 I have no clue what could help now. Maybe there was some registry error? I am lost here.
Thanks to #dxiv who made me aware of the InstallCleanup.exe.
I don't know what that tool does additionally to what I did and I cannot tell what was wrong in the first place. But that thing actually helped!
Thanks again!
I'm just starting to use Dart in Visual Studio code and having some problems.
I've gone into Visual Studio Code, gone to File-->Open Folder..then created a folder with another folder inside, and then selected it. Then I downloaded package-simple through the terminal.Then when I go to explorer, I see that there is already pre-made code..ie under lib, src, there is a simple_console_example.dart file.
When I try to run this file I get a bin/main.dart:1: Error: The system cannot find the path specified.
Any help is appreciated!
If you're running flutter extension in visual studio code for a sub-root directory, then debugging may yield the error whereas flutter run would work.
Solution is to open the sub-directory as folder in visual studio code.
If you're having this error for no apparent reason, try running commands below in the root directory of the project as suggested in this solution:
flutter clean & flutter run
Running
flutter clean & flutter run
from a terminal worked but it didn't fix the issue that I couldn't run a Debug session from within Visual Studio Code. The fix that did it for me was:
The solution is to delete .vscode folder inside your project
which I found here: Issue #29589 on Flutter Github Project
I have the same problem. find out that in my visual studio code at the explorer, i opened the wrong folder for my project. make sure your visual studio code is opening your folder project at the explorer nav bar on the left. File=>Open Folder=>"your project folder file.
Is it possible to create XNA games using Visual Studio 2012?
Yes, it's possible with a bit of tweak. Unfortunately, you still have to have VS 2010 installed.
First, install XNA Game Studio 4.0. The easiest way is to install the Windows Phone SDK 7.1 which contains everything required.
Copy the XNA Game Extension from VS 10 to VS 11 by opening a command prompt 'as administrator' and executing the following (may vary if not x64 computer with defaults paths) :
xcopy /e "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft\XNA Game Studio 4.0" "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\Microsoft\XNA Game Studio 4.0"
Run notepad as administrator then open extension.vsixmanifest in the destination directory just created.
Upgrade the Supported product version to match the new version (or duplicate the whole VisualStudio element and change the Version attribute, as #brainslugs83 said in comments):
<SupportedProducts>
<VisualStudio Version="11.0">
<Edition>VSTS</Edition>
<Edition>VSTD</Edition>
<Edition>Pro</Edition>
<Edition>VCSExpress</Edition>
<Edition>VPDExpress</Edition>
</VisualStudio>
</SupportedProducts>
Don't forget to clear/delete your cache in %localappdata%\Microsoft\VisualStudio\12.0\Extensions.
You may have to run the command to tells Visual Studio that new extensions are available. If you see an 'access denied' message, try launching the console as an administrator.
"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe" /setup
This has been tested for Windows Games, but not WP7 or Xbox games.
[Edit] According Jowsty, this works also for XBox 360 Games.
[Edit for Visual Studio 2013 & Windows 8.1] See here for documentation on installing Windows Phone SDK 7.1 on Windows 8.1. Use VS version number 12.0 in place of 11.0 for all of these steps, and they will still work correctly.
On codeplex was released new XNA Extension for Visual Studio 2012/2013. You can download it from: https://msxna.codeplex.com/releases
I found another issue, for some reason if the extensions are cached in the local AppData folder, the XNA extensions never get loaded.
You need to remove the files extensionSdks.en-US.cache and extensions.en-US.cache from the %LocalAppData%\Microsoft\VisualStudio\11.0\Extensions folder. These files are rebuilt the next time you launch
If you need access to the Visual Studio startup log to debug what's happening, run devenv.exe /log command from the C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE directory (assuming you are on a 64 bit machine). The log file generated is located here:
%AppData%\Microsoft\VisualStudio\11.0\ActivityLog.xml
There seems to be some confusion over how to get this set up for the Express version specifically. Using the Windows Desktop (WD) version of VS Express 2012, I followed the instructions in Steve B's and Rick Martin's answers with the modifications below.
In step 2 rather than copying to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\Microsoft\XNA Game Studio 4.0", copy to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\WDExpressExtensions\Microsoft\XNA Game Studio 4.0"
In step 4, after making the changes also add the line <Edition>WDExpress</Edition> (you should be able to see where it makes sense)
In step 5, replace devenv.exe with WDExpress.exe
In Rick Martin's step, replace "%LocalAppData%\Microsoft\VisualStudio\11.0\Extensions" with "%LocalAppData%\Microsoft\WDExpress\11.0\Extensions"
I haven't done a lot of work since then, but I did manage to create a new game project and it seems fine so far.