AutoMapperAssist
AutoMapperAssist copied to clipboard
darrencauthon
Nuget problems
Current version of AutoMapperAssist on Nuget requires AutoMapper >=v2.0 - but fails to run with AutoMapper v3.0 (the current version). Also, AutoMapperAssist can no longer be installed with the new version of Nuget (that ships with VS2012.4 RC2) - installation fails with: Install failed. Rolling back... Authors is required.
Sorry it was a late night and I might have been a bit curt. Should have added that AutoMapperAssist is really lekker to work with and is how AutoMapper should have worked in the first place! Thanks.
Ha, it's no problem.
I took a look last night, and there are two problems here:
1.) The >= 2.0.0 is defined as 2.0 => 2.9.9.9 (or anything less than 3). So in order to get support for 3.0, I'll have to upgrade and resolve any differences. I'll be very disappointed if it's difficult to upgrade, as I don't understand how much change could be done to a library that should be doing one simple thing.
2.) The Nuget package was created back when Nuget was very new, and Nuget apparently does not support it any longer. I'd say that's a problem with Nuget as it's still valid, and enforcing new constraints on existing packages is just going to produce dumb error messages. Like this one... I don't have an <Authors> xml block because that block wasn't required (or even used?) two years ago.
I'm going to get this upgraded as soon as possible. I think getting it done by the end of the week won't be a problem.
I don't think you'll have a problem upgrading to support 3.0 - I got my app working by pulling down your project source, adding it to my solution, and simply updating your ref to the v3 AutoMapper. Runs without a hitch though I should add that I'm currently only using the following of your methods: LoadIntoInstance(), CreateInstance() and CreateSet().
Yes it does seem odd that the Nuget upgrade will break existing, good packages. I hope for your sake that making your package compliant with the new version doesn't break compatibility with the old.
Coincidentally, I have hopped back into my .Net OSS stuff the past couple weeks. Most of my Nuget packages are old, and my plan was to release new major versions of each under the latest Nuget version. Changing the major number will keep it from breaking old references, while letting new install works with the latest. Fingers crossed...
Hitting some issue here:
/Users/darrencauthon/Desktop/AutoMapperAssist/src/AutoMapperAssist/ConfigurationHelpers.cs(33,33): Error CS0012: The type System.Func1<System.Collections.Generic.IEnumerable<AutoMapper.IObjectMapper>>' is defined in an assembly that is not referenced. Consider adding a reference to assembly `System.Core, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' (CS0012) (AutoMapperAssist)
I get this error whenever I access "MapperRegistry.AllMappers". I have System.Core 4.0 referenced, but I don't understand why this would give me a build error.
It might be some issue with Mono and/or Xamarin, which I'm now using to do this work.
I tried refreshing the existing AutoMapperAssist package, though... is that any better?
Other people are having the same issue with 3.0 that I am. Ticket here:
https://github.com/AutoMapper/AutoMapper/issues/383