just a simple question:
I'm going to use Ninject in my ASP.NET MVC 3 application, but in the Package Manager there seem to be a few options:
Ninject
Ninject.MVC3
Ninject.Web
Among others. Which of these should I install?
See https://github.com/ninject/ninject.web.mvc/wiki/Setting-up-an-MVC3-application
http://www.planetgeek.ch/2011/03/01/ninject-2-2-1-0-and-ninject-mvc3-2-2-1-0-released/
http://www.planetgeek.ch/2011/02/22/ninject-mvc3-and-ninject-web-mvc3-merged-to-one-package/
The last one is a bit outdated in the mean time, but still contains good information. I try to update it during the comming days.
Install Ninject.MVC3. The package will automatically install any dependencies it needs (i.e. Ninject)
Edit:
Looking at Ninject.Web.Mvc.nuspec, it looks like it will install Ninject2.2.0.02.2.1.0
Placed proper version. But again, install it directly so that any dependencies are also automatically installed.
Related
I am having a problem while trying to use two wonderful packages iron-io/laraworker and laracollective/iron-queue at same project.
The prior package requires version (max) 1.5.3 of iron-io/iron_mq whereas the later one (v5.2) requires that the minimum version of iron-io/iron_mq has to be 2.0.0
So this is an non-compatible situation.
Any help on this will be appreciated.
P.S.: I don't want to write my own worker libraries - I would prefer it as a vendor package - but if nothing else is possible I can work with https://github.com/iron-io/iron_worker_php.
There is no real solution for you: Don't use one of the two packages, and it will work.
Also, you can edit any of these packages and send a pull request to update the dependency on iron-io/iron_mq to match the other package, wait for it to be accepted, merged and published.
That's all you can do if you want to avoid maintaining your own code.
Running a new site on Sitecore 8.1 - installed and setup Glass.Mapper but I cannot use calls such as #RenderImage - it's complaining that i'm missing the reference to Glass.Mapper.Sc.Mvc, which I have already.
The following are the Nuget modules installed for Glass.Mapper:
BoC.Glass.Mapper
BoC.Glass.Mapper.Sc
BoC.Glass.Mapper.Sc.CastleWindsor
Castle Windsor
Castle.Core
Glass.Mapper.Sc
I have it installed on another instance of Sitecore (7.5) - an older version of Glass.Mapper, but I've noticed that the Nuget packages do not exist anymore.
Any ideas?
Thanks!
Dan
BoC.Glass.Mapper is a fork of Glass Mapper, and I believe it has not been updated to V4. Remove it (and any configs that it added or deployed) and start again I say. Just add the Glass.Mapper.Sc nuget package will add in the correct dependencies and is compatible with Sitecore 8.1.
Just to be doubly sure, this is the correct version: https://www.nuget.org/packages/Glass.Mapper.Sc/
Make sure you have Sitecore.Kernel and System.Web.Mvc referenced in your project since there is a post-install step in the nuget package that adds the correct versions of Glass dlls to your project.
To make things simpler V4 uses a Powershell script to decided which
references to add to your project, it checks both the Sitecore.Kernel
version and the System.Web.Mvc version and then installs the
appropriate Glass.Mapper.Sc and Glass.Mapper.Sc.Mvc assembly.
With regards to #RenderImage, either inherit your view from GlassView<> or better to use the extension methods, e.g. #Html.Glass().RenderImage().
More info here: http://glass.lu/Blog/GlassV4
I am working on a CakePHP 3.0 project which I want to update to 3.1-RC1. When I try do so I get an error:
Problem 1
- akkaweb/cakephp-facebook dev-master requires cakephp/cakephp 3.0.x-dev -> satisfiable by cakephp/cakephp[3.0.x-dev].
Now this plugin in question hasn't been updated in 6 months and I suspect it might work OK in CakePHP 3.1, so I would like to try it out.
How do I tell Composer to ignore this particular version incompatibility and proceed to update my CakePHP package?
I am aware of version aliases, but I only want the exception to be for the plugin in question, and not for everything else.
You should be frightened when you want to use a software that isn't maintained, hasn't released any tagged versions, and depends on developer branch versions of other important software. I wouldn't use this package at all. It will harm you in the long term, even if you made Composer install it.
If the current author does not respond to your contact attempts, you should be able to fork the project (in compliance with the license it gave you) and start maintaining the package by fixing the problems you have. Because that's what you'd have to do anyways when using unmaintained software. It will allow you to use this package in a much cleaner way, instead of coming up with a dirty Composer hack to make it install.
I have an Ember-CLI application that is very form heavy.
I started using Ember Forms to help with layout and templating, which is nice and seems to be working fine.
Apparently for validation, it requires Dockyard's Ember-Validation as well... This particular dependency seems to be installed differently and I am lost as how to do this.
I am used to using something simple like bower install ... and then just adding the dependency in brocfile, but in this case, Dockyard provides a huge list of builds to choose from and I have no idea which one to use?
Does anyone have experience installing ember-validation in an ember-cli project and getting to play nicely with ember-forms? Or perhaps it is actually more simple than I think, and I am just getting thrown off by all the builds to choose from?
To install it you can add manually the url to the build in bower.json
"ember-validations": "http://builds.dockyard.com.s3.amazonaws.com/ember-validations/ember-validations-latest.js",
And after that run bower install it should work fine.
Hope it helps.
This used to be trivial via Nuget but now, I can only find 5.0 in Nuget. How can I specifically install version 4.2? We are trying to upgrade from 4.0 to 4.2 but aren't ready for a major upgrade to 5.0 at this time. This is one of those problems that comes up when they decide to not release MSIs (or at least .ZIPs with DLLs in them, which really is all I need here).
Thanks!
NOTE: This is NOT a duplicate of this question. The difference is that I can't find 4.2 in Nuget anymore. At the time of that question, it was easy/obvious to find.
As you pointed out, you can install an older package by adding -Version <version you want> to the the Install-Package command. If you take a look at the NuGet gallery; when you select a package, scroll to the bottom, you will find the Version History. Here you can select the version you want:
Clicking one of the versions will show you the package details along with the command to install the selected version.
I think I figured it out. Check out this page. At the bottom, it lists the older versions of EntityFramewor and, when you click on it, it takes you to the details of that specific version, including the Nuget command to install it. For example, Entity Framework 4.2.0.0 can be installed via:
PM> Install-Package EntityFramework -Version 4.2.0.0
I've not actually done this yet, but I think this is exactly what I was looking for.