Fixing “Could not load assembly Xamarin.Android.Support.Fragment” after upgrading to Xamarin.Forms 3.0 in Visual Studio 2017

While working on upgrading an existing project from Xamarin.Forms 2.3 to Xamarin.Forms 3.0 the following, incredibly baffling, error was thrown during the build phase: Exception while loading assemblies: System.IO.FileNotFoundException: Could not load assembly 'Xamarin.Android.Support.Fragment, Version=1.0.0.0, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile? File name: 'Xamarin.Android.Support.Fragment.dll'   at Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.Resolve(AssemblyNameReference reference, ReaderParameters parameters)  … Continue reading Fixing “Could not load assembly Xamarin.Android.Support.Fragment” after upgrading to Xamarin.Forms 3.0 in Visual Studio 2017

Advertisements

Bushfire Nearby

It's scary to see this just over the hill. Definitely not how we expected the day to go. For my visitors from overseas, Australia is always on fire. Usually the fires rage out in the bush rather than at our doorstep, but every now and then you need to be prepared to act quickly and … Continue reading Bushfire Nearby

.net core 2.0 MVC reference

Personal reference post https://github.com/davehax/NetCore2_MultiStageForm All "dotnet xxx" commands need to be run from the command line in the Project Directory Database-First approach - packages required to scaffold the database into Model classes and then generate Controllers & Views. <ItemGroup> <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.0" /> <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.0.3" /> <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Utils" Version="2.0.3" /> </ItemGroup> <ItemGroup> <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="2.0.3" … Continue reading .net core 2.0 MVC reference

Solution to error – Package ‘Microsoft.VisualStudio.Web.CodeGeneration.Tools’ has a package type ‘DotnetCliTool’ that is not supported by project

To restore the package successfully you must open up Terminal/Command Prompt/Bash and cd into your Project directory (not the Solution directory). Here you can run the command "dotnet restore". Once this command completes running, you can now execute the following command to verify that the Entity Framework CLI tool has been installed. "dotnet ef -h" Now you can go ahead and run your scaffold command!

Fix React Native issue Remote Debugger Unavailable

React is awesome. React Native sounds just as awesome as I can take my React skills to the Mobile landscape! While creating a project using create-react-native-app I couldn't figure out how to enable Remote Debugging. If you're like me then search no further. In your project, under the .expo folder, open settings.json and set the dev prop to true. If this … Continue reading Fix React Native issue Remote Debugger Unavailable

Adding a ServiceWorker to a Webpack project to enable Offline Caching

Things move so fast in the JavaScript world so please make sure this article is relevant to you. It's currently March 2018 I'm using WebPack 4.2.0 I used offline-plugin to accomplish adding a ServiceWorker to my JavaScript app that uses Webpack as a build tool. The README on the offline-plugin repository page has excellent instructions for setting up this Webpack … Continue reading Adding a ServiceWorker to a Webpack project to enable Offline Caching