Which MVVMCross Package contains the WindowsStore namespace - nuget

After updating an MVVMCross project from 3.1.1 to 3.2.1, I found that I was getting errors resolving the references to MvxStorePage (Cirrious.MvvmCross.WindowsStore.Views).
I've had a look inside the MVVMCross project, and it looks like WindowsStore should be inside Cirrious.MvvmCross.WindowsStore.dll. However, I can't seem to determine which NuGet package this is. I've tried looking in the NuGet Package Explorer, but can't seem to determine where it is.
I'm currently referencing:
MMVMCross
MMVMCross - MVVMCrossCore
MMVMCross - MVVMCrossCore - Portable Support
MVVMCross - Hot Tuna Libraries
MVVMCross - Hot Tuna Starter Pack
+ A bunch of plug-ins
So, my question is twofold: which package is this located in and, as a wider question, how can I determine myself which package it's in?

The packages are defined in nuspec files in https://github.com/MvvmCross/MvvmCross/tree/3.2/nuspec
You can see which ones reference Cirrious.MvvmCross.WindowsStore.dll using search - e.g. GitHub search https://github.com/MvvmCross/MvvmCross/search?utf8=%E2%9C%93&q=Cirrious.MvvmCross.WindowsStore.dll&type=Code or download the files and use grep or Find in Files locally

Related

How to download Unity dots (entity package) with unity 2020.3 LTS?

I decided to try out the new unity dots system, or, the new entities package (as well as the hybrid renderer), but I can't find the package in the package manager with preview packages enabled. After looking it up, I could not find any resources, other than one that told me that they moved some of the preview packages out of the package manager, and somewhere else. Does anyone have any idea where it could be?
This is what it looks like on my screen by the way:
From Entity Component System - DOTS Project Setup
Starting with Unity 2020.1, the DOTS packages are not listed in the package manager, even when preview packages are enabled. There are two alternative options to install those packages:
You can use "Add package from git URL..." under the + menu at the top left of the package manager to add packages either by name (such as com.unity.entities), or by git URL (but this option isn't available for DOTS packages). Note that it might take a few moments before the package starts installing.
Alternatively, you can add DOTS packages by directly editing the Packages\manifest.json file in your project. This file requires not only the package name but also a version which can be found by looking at the documentation of each package (such as "com.unity.entities" : "x.x.x-preview.x").
For example currently it would be com.unity.entities" : "0.17.0-preview.41"
And
Follow the link for more information about installing hidden packages.
Maybe also interesting for you:
The recommended set of core packages to be added to a DOTS project is:
com.unity.entities
com.unity.rendering.hybrid
com.unity.dots.editor

What are the available dot net core dependencies?

I recently started experimenting with dot net core , and one of my major problems was restoring the dependencies. I went into the the project.json file and added some dependencies , the name was correct but the version was just trial and error until i reached the recent version. I couldn't seem to find any documentation online either , can anyone help me find or show me where i can find a proper list of all the dot net core dependencies and their latest version ?
I have used core to great success. The package manager in VS2015 and 2017 does a great job of resolving both the version you are using and other available versions. If you are working directly with project.json ( not available in VS2017, dependencies have been moved back to the project file ), it will only tell you what packages are available via your user cache. ( found in C:\Users\YourUserNameHere.nuget\packages for both vs2015 and 2017 ) by typing the package name and then letting intellisense do it's thing.
Of course once you do a get of a package it is then available from your cache.

install titanium module from github

i'm having some issues getting modules to work on my app - I keep on getting told that the requested module cannot be found.
It is entirely possible that i'm not installing the modules correctly - so, for the purposes of this question:
Once i've downloaded the zip file from git hub using the green "download" button, what do i do to import the module into my project? Not how do i tell tiapp.xml to use the module - just what do i do to install it?
Can you please run through using the facebook module found at https://github.com/appcelerator-modules/ti.facebook
thanks!
Inside the zip file of the download you'll see there is a folder called modules. This is the same folder that is in your root of the project.
So, an iOS module should be installed in the /modules/iphone folder. Once added, you can add Facebook to your app like this:
<module platform="iphone">facebook</module>
If you want to specify a version you can do so like this:
<module platform="iphone" version="1.1.0>facebook</module>
note: I made up the version number
You can also add it through the tiapp editor in Appcelerator studio, although it doesn't always seem to find the module. This might be a bug in studio though, usually it works great.
HMMMM
Two main issues here, one directly relating, the other less so.
Issue 1
The link i gave to get the codebase from github is wrong - well, it gets the codebase, but not in a form that can be used as a module. It is, in fact, the uncompiled version.
Versions for download can be found here.
So that takes care of issue one, what about
Issue 2
The latest version for use is a bit broken. Seems someone (from the appcelerator team???) decided to make the latest 6.0.1 release have a minsdk of the (at this time) as-yet-unreleased version 6.0.0, and sets the apiversion to 3.
This breaks the current release of 5.5.1, so for anyone reading this prior to 6.0.0 for appcelerator, you will want to use this release version.

LocalPackageRepository returns IsLatestVersion=true for all packages

I've created a folder on my C:\packages. Inside I've created two packages with identical Ids but have different versions. I the use Nuget.Core to create a LocalPackageRepository pointing to this directory.
When I query for the packages using respository.FindPackages("myId")both packages are correctly returned by the service. However, the IsLatestVersion is true for both packages, even though their versions are clearly different.
Things I've tried:
I know these packages dicovered as OptimizedZipPackages looking through the source here, I cant find anything relevant to suggest an issue with the implementation.
I added the local repository to my Visual Studio NuGet feed manager. When I query that service, the latest version is shown.
Something seems to be wrong with how I've either created the packages, instantiated the repository, or its a bug in the library.
Using NuGet Core v2.8.60318.667
Looking at the source code the LocalPackage always returns true for IsLatestVersion if the NuGet package is not a pre-release.
In Visual Studio what happens is that the list of packages is further filtered by removing all but the latest version in the list so you only ever see the latest version. One way to do this is to use extension methods included in NuGet:
packages.DistinctLast<IPackage>(PackageEqualityComparer.Id);
The DistinctLast method assumes that the same NuGet package id will appear together in the list otherwise it will not filter them correctly.
I believe you could also use the AsCollapsed extension method which is similar to the above. It basically does:
packages.DistinctLast<IPackage>(PackageEqualityComparer.Id, PackageEqualityComparer.Version);

Autofac AggregateService exists in NuGet?

I found Autofac AggregateService awesome but what is the right way to include it in my project: clone it from code.google.com or use NuGet?
I got used to use NuGet but I can't find nothing about AggegateService there. Any help?
It seems that AggregateService and the other Extras are currently "in limbo". There's been a recent change in that the contributions are now being made part of the same solution as Autofac core, while they were previously a separate solution. From the current build file you can see that extras will be made available as a separate Autofac.Extras package and a separate download from the Autofac page.
Meanwhile, you can use AutofacContrib 2.6.1 or to grab the source and compile a dll yourself.
Btw, thanks for finding AggregateService awesome ;)
Update: actually, reading the build file properly (and looking at the current source structure), the Extras parts will be distributed as individual packages. So expect to find Autofac.Extras.AggregateService on Nuget in the future.