Explore >> Select a destination
|
You are here 
|
adamstorr.co.uk | ||
| | | | |
www.nexsoftsys.com
|
|
| | | | | In this article, let's take a deep dive to Dependency Injection mechanism of .NET Core 3.1 to achieve Inversion of Control (IoC) between classes and their dependencies. | |
| | | | |
nodogmablog.bryanhogan.net
|
|
| | | | | Full source code available here. Did you know that .NET Core 2 can pass in an instance of any type you want to the Startup.cs constructor? Well you can! Here's how. | |
| | | | |
mikemikina.com
|
|
| | | | | Vapor 3 has a very interesting dependency injection framework which will help you manage dependencies and mock them inside your tests. | |
| | | | |
matthiasnoback.nl
|
|
| | | As you may have read on the Symfony blog: as of Symfony 2.4 you can register console commands using the service tag console.command. What is the big deal, you would say. Well, let's discover it now. This is how the documentation tells you to write your console commands: namespace Matthias\ConsoleBundle\Command; use Symfony\Bundle\FrameworkBundle\Command\ContainerAwareCommand; use Symfony\Component\Console\Input\InputInterface; use Symfony\Component\Console\Output\OutputInterface; class MyCommand extends ContainerAwareCommand { protected function configure() { $this->setName('my:action'); } protected function execute(InputInterface $input, OutputInterface $output) { // do something } } How to make sure your command will be noticed? Until Symfony 2.4 there wer... | ||
