Latest MahApps unsupported

[ExVeGi]

Latest MahApps unsupported

[punker76]

@ExVeGi what no do you mean with unsupported? Which version?

[ExVeGi]

The alpha version, it's not a full release, will tinylittlemvvm support it after full release or even while in alpha?

[punker76]

@ExVeGi Which alpha?

[ExVeGi]

@punker76 NuGet unstable version - 1.6.0-alpha0184

[punker76]

@thoemmi It really doesn't work with v1.6 (pre-release), caused by these lines in csproj

    <Reference Include="System.Windows.Interactivity, Version=4.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
      <HintPath>..\packages\MahApps.Metro.1.3.0\lib\net45\System.Windows.Interactivity.dll</HintPath>
      <Private>True</Private>
    </Reference>

This could be solved e.g. with the paket manager which doesn't add the version informations...

    <When Condition="$(TargetFrameworkIdentifier) == '.NETFramework' And $(TargetFrameworkVersion) == 'v4.5'">
      <ItemGroup>
        <Reference Include="MahApps.Metro">
          <HintPath>..\packages\MahApps.Metro\lib\net45\MahApps.Metro.dll</HintPath>
          <Private>True</Private>
          <Paket>True</Paket>
        </Reference>
      </ItemGroup>
    </When>

[ExVeGi]

@punker76 I've fixed it for myself, thanks.
@thoemmi it would be useful if it was implemented in the nuget package.

[thoemmi]

IIRC another issue is that TinyLittleMvvm is currently built for MahApps.Metro 1.3, which is strong-named, but starting with 1.6 MahApps.Metro isn't strong-named anymore.
Anyway, this week I'm busy, so I hope to address this issue next weekend.
Nevertheless, there will be new release of TinyLittleMvvm once MahApps.Metro 1.6 is released.

[ExVeGi]

Just a reminder, don't forget about Autofac 4.6.2, it is out.

[Kamdzy]

#8 Should do the work

[thoemmi]

I have uploaded a new unstable release, see https://www.nuget.org/packages/TinyLittleMvvm/0.6.0-unstable0003 (it's in NuGet's queue for validation at the moment).

I also used the opportunity for some housekeeping, i.e. I cleaned up the build process and updated the projects to the new csproj SDK format, see 640be8f.

Thanks to @Kamdzy for his contribution!

@ExVeGi Could you please check if the new package works?

[ExVeGi]

Tested, confirmed working. Thank you.