[enter image description here][1]
[1]: https://i.stack.imgur.com/u2ptX.jpg this is link of image
Edit: I found a solution by luck. After deleting the folder .AndroidStudio2.3 under C:\Users\<your_user> I could open the projects in Andorid Studio 2.3 normal again. Deleting this folder will also delate all your custom settings for Android Studio, so be sure to back up them if you want to keep them.
Still, I would recomend to switch to the new Android Studio:
I had this problem with multiple projects with the version 2.3 of Android Studio. Since I was already using Android Studio 3.0 for some of my projects, I migrated the other projects also to the new version. With the new Android Studio and Gradle version it works normal again.
open Gradle task, delete VM options.
Related
I am trying to combine obfuscating my xamarin android project and then bundle the assemblies into native code with the Visuals Studio 2017 Pro option.
I was able to obfuscate my assemblies with this tutorial https://blog.noser.com/xamarin-android-code-obfuscation/
Unfortunately the obfuscated assemblies does not find its way into the native bundle.
Likely i intercepted the build proccess at the wrong place.
<Target Name="Obfuscate" AfterTargets="_CopyIntermediateAssemblies" Condition="'$(Configuration)' == 'Release'">
Does anyone know how to merge the obfuscated assemblies into the native bundle? Thx for help in advance.
I help develop another .NET obfuscation/protection tool, Dotfuscator.
We've written a Xamarin build integration that automatically handles protection as part of the normal build process, so you don't have to manually write your own MSBuild targets or copy files around.
The official Xamarin docs recommend using Dotfuscator to protect Android builds, but this integration also works for iOS and UWP.
As Dotfuscator's Community Edition is included in Visual Studio, you can try this integration out for free.
I wrote a guest post for the Xamarin Blog that explains how to do this.
Edit regarding the setting in the question: I did some limited testing and Dotfuscator works fine with the "Bundle assemblies into native code" setting. I installed the latest version of Visual Studio 2017 Enterprise, version 15.7.2, but found out that version has a bug related to this setting. To work around it, I used the unofficial VSIX install mentioned at that link. Then I opened a Dotfuscator-Xamarin sample app and enabled the native code setting. I also added code to the sample to show the name of a class used by the application. Then I deployed the app to an emulator. The app ran normally and the logging statement showed an obfuscated name for the class, indicating that Dotfuscator correctly protected the app before it was bundled into native code.
I just recently swapped my MS PC for an Mac, I'm trying to continue working on an MVC project, but I'm getting an error (Error CS1902: Invalid option 'portable' for /debug; must be full or pdbonly (CS1902)).
Are there any good documents that explain how to make it work? I have seen people porting MVC to .NET Core, but I can't get the analyser to work on my Mac (not sure it's supported yet).
I did two things.
I update the Microsoft.Net.Compliers via nuget.
https://www.nuget.org/packages/Microsoft.Net.Compilers/
Change one value in the properties of project.
https://johnharold.wordpress.com/2017/08/16/csc-error-cs1902-invalid-option-portable-for-debug-must-be-full-or-pdbonly-cs1902/
I wish you can solve the problem
I had this same problem when trying to use Visual Studio for Mac to build a solution that works fine in Windows. Turns out the /debug:portable flag was being passed to the build command, even though the 'Debug Information' was correctly set to 'Full' in my project settings. Search the build output for 'portable' and you will indeed find the flag there regardless of your settings.
The fix is to upgrade the Microsoft.Net.Compilers nuget package. In my case, it upgraded from 1.0 to 2.7, and then the project built successfully.
Right click on the project in the solution explorer and go to
Options, Build, Compiler and change Debug information to Full
I just installed Visual Studio 2013 Ultimate trial version for completing the MVC5 tutorial by Rick Anderson, which worht doing it.
The tutorial: http://www.asp.net/mvc/tutorials/mvc-5/introduction/getting-started.
However, I created a blank solution first and then try to add an ASP.Net Application project, which is going to be my MVC5 tutorial project. And I got this weird message:
Error: this template attempted to load component assembly
'Microsoft.VisualStudio.Web.Project, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a'. For more information on this problem
and how to enable this template, please see documentation on
Customizing Project Templates.
But I´m not customizing, I´m just creating a project out of a built in template.
Do you know how can I solve it?
Here is the solution:
In Visual Studio 2013, select Tools > Extensions and Updates
Check for updates. You should have the Azure SDK update available.
Download and install the Azure SDK. After this, everything should work fine.
If your updates are not turned on, enable your auto detection of updates in Tools > Options > Environment > Extensions.
If you have unspecified error related to E_fail(code), try this:
When creating a new MVC 5 application, change the framework version from 4.5.1 to 4.5, if that did not work change it to 4. Check the below image if it is not clear.
Another approach:
This is really important if you are installing Visual Studio 2013 on un-updated Windows 7.
there reason i am calling out "not updated is",
The reason that 'un-updated' matters is because Visual studio 2013 does not update the powershell that is required by VS2013 for most of the stuff.
The simple solution is to update Powershell to the latest version.
If you are not sure how to update powershell, you can use this tutorial.
So I stumbled upon this issue as well and would like to share how I was able to resolve this problem.
Tools -> Extensions and Updates -> Online -> NGet Package Manager: Click the download button once you have the NGet Package Manager selected. Make sure to restart your Visual Studio after you have downloaded the Manager.
This should do the trick
Close Visual Studio, run the VS executable with the command line option as shown below (you will likely have to supply the full path), and relaunch VS normally. This should re-initialize the templates, including the one that you are having problems with.
devenv.exe /installvstemplates
So I faced the same problem with Visual Studio 2013, and I don't know what's the problem but it appears that it only occurs when creating a new project, and choosing "Web" from the panel.
What I did was simply clicking on "Visual Studio 2012" just below it, and it worked !
I am using Xamarin's Visual Studio pluggin. I have a Xamarin iOS Library project and it needs to use System.Net.Http in order to compile. However, I cannot seem to add it as a reference. I have updated my Xamarin Studio to the Alpha version, but still cannot see System.Net.Http in the Assemblies list when attempting to Add Reference.
Any help here would be GREATLY appreciated as I am inches away from getting this thing implemented, but am stuck on this one reference.
Is this available in Visual Studio (with Xamarin Pluggin installed), or is it only in Xamarin Studio?
Thanks in advance for your help !!
WOW !! What a work around.
Ok, here's the solution. Looks like the Visual Studio pluggin does NOT get updated when you update Xamarin Studio on your windows box. HOWEVER, when you go to your mac build server and update Xamarin to the Alpha version, then open a Xamarin Project in Visual Studio, it will prompt you that the build server and Pluggin are different versions and will allow you to upgrade. When you upgrade, after closing visual studio, then open visual studio again, VOILA!!! The System.Net.Http reference is now available under Assemblies when adding a reference.
So, the solution is to update your MAC Xamarin Studio to the Alpha version and then Visual Studio will prompt you for an update. Update it and you're golden !!
Seems like there should be an easier way, but this one worked.
i think you cant add The System.Net.Http reference.you should try this RestSharp
A simple REST client for consuming HTTP APIs..
RestSharp makes it easy to consume the wide array of services on the web over HTTP, like: Amazon, Facebook, or even Twitter...
http://components.xamarin.com/view/restsharp
I am new to Blackberry. Present I am working on 4.7 Blackberry component pack.Now I want to move my old projects to newer versions like 5.0 and 6.0. For that I installed eclipse Galileo 3.5 version and configured latest component packs and Blackberry java plug_in 1.1.2.
I searched in google and find somewhere that use File menu option Import>Import Legacy Blackberry projects and it is asking .jdw file in the workspace.I dont want to move entire workspace, I want only single project. am not able to find it.can any one help me to get this......
In Eclipse, for your old project, try to compile with the new JDE like say 5.0. See what breaks, fix it, repeat till it compiles. Then run on handset to ensure it looks ok.