Posts
1145
Comments
890
Trackbacks
1
November 2016 Blog Posts
Repairing Xamarin after uninstalling Visual Studio 2017 RC

In a previous post I mentioned that uninstalling Visual Studio 2017 RC broke any existing Xamarin projects, removed the templates, etc. and that I hadn’t figured out how to fix it.

Here’s how you fix it:

Go the Xamarin web site and go to the download page.  Annoyingly enter in your contact information for the 17th time, and then where it asks you if you already have Visual Studio installed, select ‘no’.  Download the file, execute it, and it will reset things (it doesn’t actually appear to download anything that I could tell, but it’s hard to tell). 

When you then load a Xamarin project, it will tell you an update is available, etc.  You should be good to go.

posted @ Tuesday, November 29, 2016 10:03 AM | Feedback (0)
Uninstalling Visual Studio 2017 RC appears to have broken Xamarin

In a previous post, I mentioned some difficulties with the latest Visual Studio 2017 RC, and how uninstalling it, plus installing the latest Typescript release, appeared to have minimized the damage.

Unfortunately, I apparently have spoken too soon, as I discovered today that an Android app project is broken, showing the project as being incompatible, and there are no longer any Xamarin project templates to be had.  Even worse, there doesn’t appear to be a ‘repair’ option, so I’ve yet to figure out how to fix Xamarin.

Again, my fault for blanket installing without testing, but still very annoying.

posted @ Friday, November 25, 2016 9:56 PM | Feedback (0)
Scaffold-DbContext doesn’t appear to work with EF Core 1.1

Are you surprised?  Me either.

Given this NuGet Package Console command:

Scaffold-DbContext -Connection "data source=MyServer;initial catalog=MyDb;integrated security=True" -Provider "Microsoft.EntityFrameworkCore.SqlServer"

where I’ve obviously replace my actual server name and database name, one gets this error:

Could not load file or assembly 'System.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

Well, that’s because EF Core 1.1 along with the SqlServer package requires SqlClient version 4.3.0

Fantastic.

posted @ Friday, November 25, 2016 11:42 AM | Feedback (0)
Be wary of Visual Studio 2017 RC

I made the mistake of installing this on multiple machines instead of my usual “install on one and check it out fairly thoroughly” routine.  I guess I had been lulled into somewhat of a sense of security with the beta/RC process for Visual Studio 2015, in that I didn’t think that installing 17 RC would break important parts of 15 functionality.

To wit, simply installing 17 RC would break some .NET Core web apps inside Visual Studio 2015, even if I didn’t try to open/upgrade them in the new software.

Various errors included:

  • the following error occurred attempting to run the project model server process (1.0.0-preview3-004056), unable to start process.
  • tsc.exe exited with code 1
  • project file could not be found

And remember, this is trying to run in old software, not the new software.

Luckily, simply uninstalling Microsoft Visual Studio 2017 through Control Panel’s Program and Features, and then installing the newest Typescript exe from here fixed the issue, instead of requiring me to repave multiple machines and weeping copiously.

YMMV.

posted @ Sunday, November 20, 2016 7:24 PM | Feedback (0)