-
-
Notifications
You must be signed in to change notification settings - Fork 843
Is it possible to install Autofac 4.0 for UAP? #699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
http://stackoverflow.com/questions/33855314/how-can-i-update-one-specific-dotnet-assembly-in-universal-windows-platform-app/33902742#33902742 - this can help a bit during resolving dependencies conflict between UAP and Autofac |
If i add beta runtime dependency i get following: All packages are compatible with UAP,Version=v10.0. |
Any change in the situation with Visual Studio 2015 Update 1? |
Upd1 didn't change anything. But i've found a workaround.
|
Actually Autofac shouldn't be referencing those new package versions. System.Linq.Expressions 4.0.11-beta-23516 has no API changes over System.Linq.Expressions 4.0.10. Why reference the latest version? |
Given we've got a bunch of package compatibility stuff we're already fighting through with the I'll leave this open to ensure we remember to test specifically on UAP, but it may be worth following that issue since we'll probably update things more often over there. |
I'm also getting this.
Which is a problem because I'd like to update to 4.0 to fix CA errors #663 |
@JamesNK can you share your project.lock.json? It seems like the runtime-linkage isn't happening. System.Linq.Expressions AOT implementation exists in runtime.aot.System.Linq.Expressions. So long as our runtime ID graph and lineup are part of your package closure (Microsoft.NETCore.Platforms) it should bring in the aot implementation. |
I rolled back the {
"dependencies": {
"Autofac": "4.0.0-rc2-185",
"Microsoft.NETCore.Runtime": "1.0.1-beta-23516",
"Microsoft.NETCore.UniversalWindowsPlatform": "5.0.0",
"System.Collections": "4.0.11-beta-23516"
},
"frameworks": {
"uap10.0": {}
},
"runtimes": {
"win10-arm": {},
"win10-arm-aot": {},
"win10-x86": {},
"win10-x86-aot": {},
"win10-x64": {},
"win10-x64-aot": {}
}
} |
This project I'm using Autofac with has a lot of developers and I don't want to add non-standard feeds into the mix. I'll wait until it is on nuget.org |
Is it possible for you to try it just temporarily so I can verify it's not "works on my machine?" If it works for you, I'll close the issue as fixed. |
It compiles. Ironically Code Analysis doesn't work anymore which is the reason I wanted to upgrade in the first place.
|
Thanks for checking it out. I think I'll call this closed for now, but if you find this doesn't go away after all the tooling catches up to the name changes and everything else, we can revisit. |
Default project.json looks like that:
During installation of package via nuget i see many errors like this:
The text was updated successfully, but these errors were encountered: