Reference error .netportable 4.0 profile136 profile is not installed - xamarin.android

Suddenly I started getting reference errors in my Portable Class Library projects,
When referencing System, System.Core, System.Xml I get
.netportable 4.0 profile136 profile is not installed
It used to work fine a few days ago so I'm not sure if a recent update would have caused this issue. I did switch back and forth from stable to beta, and back to stable update channel. Does anyone know what might be causing this error?

Does this happens on MAC? you might need to reinstall Xamarin Studio

Related

Visual studio unable to evaluate anything in debug in any page of my blazor webassembly

I have a blazor webassembly app that is working fine and it is split in webassembly talking to a web api version all .Net Code
I use VS community Edition 2019 and suddenly after many modifications to my code I noticed that I am not able to debug and see any variable content(unable to Evaluate) at any break points anywhere in my web assembly app. I tried with an old version of my code which I know it was working then and same issue, so it is not the code.
I tried upgrading VS to 16.11.75.64347 ( from 16.6 something) without success and even uninstall & reinstall VS with no success.
The only new thing on my station was a windows update this week.
Is someone had something similar happening this week?
ps: What is weird is that I do not not have this problem in my web API solution portion just the webassembly solution.
I think I've been badluck to find many not working thread but finally it was simply to close VS . delete the .vs directory tehn relod the solution and it was OK. It is weird though that many old version of my code that never had this issue had the same problem. It was impossible to have all those .vs not working although I had not touched them in weeks. Anyway it is now working.

Delphi 10.3.2 - Add Project to version Control - Import to SVN Crashes Delphi IDE

I am running Delphi 10.3.2 RIO. I have installed the latest version (x64) of Tortoise SVN (1.12.xx) and created several repositories. Using the Repository browser, I have the URL of the repository. I open a Delphi project and select Add to version Control -> SVN. Delphi IDE correctly identifies the files in the project (and those to exclude). I add a message and click import. After a couple of seconds I get the Windows message "Embarcadero RAD Studio for Windows has stopped working" and it literally crashes completely.
I have tried this with several different Projects and with several different repositories. I uninstalled the latest version of Tortoise SVN (1.12.xx) and installed the earlier version (1.10.xx). I deleted and recreated the repositories and repeated the Add to version control from the Delphi IDE. The result was exactly the same, ie. after a couple of seconds I get the Windows message "Embarcadero RAD Studio for Windows has stopped working" and it crashes completely.
I have not gone back to the previous version of Delphi and retried the SVN. That's on an Archived VM. If I did go to the trouble of resurrecting the D10.2.3 VM and it worked, what would it prove? Simply that a previous version Worked.
I can try and populate the repository manually (ie. outside of D10.3.2) and see if it works then.
When I have tried this with the previous version of Delphi, D10.2.3, it worked fine with SVN. I had expected it to simply import the project.
Notes:
I have seen this issue posted on another forum, but there was no response, so I am not the only one experiencing this issue.
I thought this may have been because the REPO was in OneDrive, but I moved it to my C:\ drive and the result was the same.
Two questions:
Has anyone else had similar experience with D10.3.xx and SVN?
Has anyone else with that problem solved it?
Thank you
After taking #KenWhite's advice, I find there is a defect already posted WRT this issue:
Version Control Doesn't Work
So a known issue with no fix.
Kevin

Get InvalidCastException with Glimpse, even though it's not installed. How do I fix this?

I had a Visual Studio 2012 project that I imported into Visual Studio 2013. I upgraded Entity Framework to version 6. I got the following error when I started the first time: Unable to cast object of type 'Glimpse.Ado.AlternateType.GlimpseDbConnection' to type 'System.Data.SqlClient.SqlConnection'. Since this was a prototype app, I wasn't concerned about Glimpse, so I uninstalled it via NuGet, which removed the error and I carried on.
Now, I'm deploying to Azure websites and I keep getting that error!
Glimpse is uninstalled.
It works fine in release and debug locally.
I tried putting System.Data.Metadata.Edm.MetadataWorkspace.ClearCache(); in the Application_Start like this says. (Even though I don't run queries in Application_Start
I suspect I have a caching problem on Azure, but I'm not sure. How do I get the Azure deployment to remove Glimpse like the local install has?
Update: "Fixed"it by deleting the azure website and recreating it. Would still love to hear how to do with this without going with the nuclear option.
This is a bug and is fixed in the release that will hopefully be going out tomorrow - see here for more details https://github.com/Glimpse/Glimpse/issues/540.
I also faced this error and later on found the resolution.
Issue was that I had MVC5 and EF6 based solution and i had imported Glimpse.mvc4 and Glimpse.ef5 packages and they were incompatible i think .
Once i upgraded to Glimpse.EF6 and Glimpse.MVC5 it started working fine.
also had the same one, when I opted to remove Glimpse.
you can prevent this by deleting the bin/ and obj/ folders from your project folder(s) as Glimpse is copied to your bin during debugging.

Can't Access Admin CP on nopCommerce v2.60

I have gone here on CodePlex and downloaded nopCommerce v2.60. I am on a Windows 8 Pro 64x Machine, I have .NET Framework and SQLEXPRESS 2012 installed.
The nopCommerce solution installs perfectly fine, no problem ! All front-end stuff work fine. But when I try and access:
localhost:xxxx/admin
I get the following error:
I have already tried re-installing with fresh database and files, but no success. I don't know how to get it to work. Before this use to work no problems at all!
You need to BUILD the whole solution before running. :)
Ok after an exchange of emails with a friend of mine who is really good at C# and has excellent experience with nopCommerce. He too was able to duplicate the problem on his machine running Win 8 Pro 64x along with VS 2012, like me.
It turned out, for some strange reason, one must build, and re-build the solution a couple of times before running it in VS 2012.
So open up your nopCommerce fresh in VS2012, and before you run it, re-build the solution 2 or 3 times, and then run it.
That was the fix for me. So annoying that I spent so much time stuck with it, but I'm glad it works now.

Installation problems with ASP MVC Release Candidate 1

I've tried installing RC1 must have been 5 times already and always run into the same issue around the "Configuring Templates' step. I've tried everything I can think of but now I have neither RC1 or Beta. Has anyone run into this error? Any suggestions for what I can do?
Screenshot of my problem here (not sure why I can't place it as an image.
(Cross-posted to the ASP.NET forum here but I don't really expect much of useful response there.)
Edit: Here is everything I can think of that I have installed that might possibly be affecting this: Coderush, Refactor Pro!, Source Outliner, TestDriven.Net, MbUnit (installs some templates), Some DevExpress plug-ins (GhostDoc, CR_Classcleaner), F#, Spec #
I have also installed (and uninstalled) ASP.NET MVC Beta
Just happen to run across this... do you have Clone Detective for VS installed? Seems as though some people had trouble installing the MVC Beta with it installed.
http://www.codeplex.com/CloneDetectiveVS/WorkItem/View.aspx?WorkItemId=11549
After the obvious step of removing any older installations of MVC, I've heard the templates can have issues with Visual Studio add-ons. Try removing any add-ons to VS you might have running, then run the installer.
For the record, it was either F# or Spec# that was giving me problems since I don't really use either much I uninstalled both and RC1 went fine.
You don't state explicitly, did you install any other previous versions (such as beta or preview)? You will need to uninstall Beta or Preview x before installing the RC.

Resources