
Research
/Security News
60 Malicious Ruby Gems Used in Targeted Credential Theft Campaign
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
MvcSiteMapProvider.MVC5.DI.Ninject.Modules
Advanced tools
Dependency injection modules for Ninject that can be used to integrate MvcSiteMapProvider into an existing dependency injection setup. You may customize this configuration to allow for replacement of virtually any part of MvcSiteMapProvider by implementing one of its interfaces and injecting an instance of your implementation. This package requires manual configuration to integrate with Ninject, but is the least invasive option that won't bypass any existing DI bootstrapping code.
To add MvcSiteMapProvider to your DI configuration, add the following code to your composition root.
// Create the DI container (typically part of your DI setup already)
var container = new StandardKernel();
// Setup configuration of DI (required)
container.Load(new MvcSiteMapProviderModule());
// Setup global sitemap loader (required)
MvcSiteMapProvider.SiteMaps.Loader = container.Get<ISiteMapLoader>();
// Check all configured .sitemap files to ensure they follow the XSD for MvcSiteMapProvider (optional)
var validator = container.Get<ISiteMapXmlValidator>();
validator.ValidateXml(HostingEnvironment.MapPath("~/Mvc.sitemap"));
// Register the Sitemaps routes for search engines (optional)
XmlSiteMapController.RegisterRoutes(RouteTable.Routes);
For more help consult the Ninject documentation at https://github.com/ninject/ninject/wiki/Modules-and-the-Kernel
Making MvcSiteMapProvider depend on DI is a bit of a double-edged sword. While this makes MvcSiteMapProvider extremely easy to extend, it is possible that new features added to MvcSiteMapProvider will cause your existing DI configuration to break when doing an upgrade.
Unfortunately, NuGet doesn't have a way to automatically merge changes into your DI modules - if you have changed your configuration in any way, the module will be skipped when you upgrade. But then, the purpose of giving you this code is so you can change it. For this reason, when you upgrade your MvcSiteMapProvider version, you should also compare your DI module to the corresponding module in the master branch to see if there are any changes that need to be made to your configuration. The best way to do this is to use some kind of diff tool (such as Beyond Compare) to highlight the differences and assist with bringing the changes into your configuration without overwriting your customizations.
Note that you don't need to merge in #if, #else, and #endif blocks inside of the module, but only the code between them that applies to your specific .NET and/or MVC version.
The latest module for Ninject is located at the following location:
FAQs
Dependency injection modules for Ninject that can be used to integrate MvcSiteMapProvider into an existing dependency injection setup. You may customize this configuration to allow for replacement of virtually any part of MvcSiteMapProvider by implementing one of its interfaces and injecting an instance of your implementation. This package requires manual configuration to integrate with Ninject, but is the least invasive option that won't bypass any existing DI bootstrapping code.
We found that mvcsitemapprovider.mvc5.di.ninject.modules demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.
Research
/Security News
Two npm packages masquerading as WhatsApp developer libraries include a kill switch that deletes all files if the phone number isn’t whitelisted.