sharepointlead.blogspot.com

rubenherman.be

Sitemap – Ruben Herman

http://www.rubenherman.be/sitemap

Skip to main content. Using EntityFramework in SharePoint. Dependency Injection in SharePoint 2013. Using EntityFramework in SharePoint. IoC Container in SharePoint 2013 Service. Dependency Injection in SharePoint 2013. Using EntityFramework in SharePoint. IoC Container in SharePoint 2013 Service. On Using EntityFramework in SharePoint. On Using EntityFramework in SharePoint. On IoC Container in SharePoint 2013 Service. On IoC Container in SharePoint 2013 Service. Sparkling Theme by Colorlib.

rubenherman.be

SharePoint 2010 – Ruben Herman

http://www.rubenherman.be/category/sharepoint/sp2010

Skip to main content. When adding a new NuGet package to the Package folder in a SharePoint project, we often get this error, since not all packages are strongly named:. Error occurred in deployment step ‘Add Solution’: This solution contains one or more assemblies targeted for the global assembly cache. You should use a strong name for any assembly that will be in the global assembly cache. Dependency Injection in SharePoint 2013. Using EntityFramework in SharePoint. Sparkling Theme by Colorlib.

rubenherman.be

Dependency Injection in SharePoint 2013 – Ruben Herman

http://www.rubenherman.be/dependency-injection-in-sharepoint-2013

Skip to main content. Dependency Injection in SharePoint 2013. If someone would ask me a while ago when I use property injection, I would definitely say NEVER. But then ASP.NET WebForms/SharePoint happened… I usually prefer using constructor injection, but in this case, this doesn’t seem possible. Constructor injection vs property injection. Public class Test : Page { [Import] public ILogger Logger { get; set; } protected void Page Load(object sender, EventArgs e) { Logger.Info("Works! In the presentatio...

rubenherman.be

About me – Ruben Herman

http://www.rubenherman.be/about-me

Skip to main content. This list does not include all known languages, but most commonly used:. This list does not include all known frameworks, but most commonly used:. This list does not include all known tools, but most commonly used:. Software : Must-Have Skills for Software Engineers –. Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives –. Head First Object-Oriented Analysis and Design: A Brain Friendly Guide to OOA&D –. Head First Design Patterns –.

rubenherman.be

Using EntityFramework in SharePoint – Ruben Herman

http://www.rubenherman.be/using-ef-in-sp

Skip to main content. Using EntityFramework in SharePoint. When adding the EntityFramework package from NuGet into a SharePoint project with the command:. We got to make sure some things are configured into SharePoint. You’ll notice that adding the package creates a new App.config file. The XML in this file should be added to the web.config file from SharePoint. But to make sure we safely edit the config, we create an eventreceiver and add the necessary nodes there. EntityFramework defaultConnectionFacto...

rubenherman.be

SharePoint 2013 – Ruben Herman

http://www.rubenherman.be/category/sharepoint/sp2013

Skip to main content. Dependency Injection in SharePoint 2013. If someone would ask me a while ago when I use property injection, I would definitely say NEVER. But then ASP.NET WebForms/SharePoint happened… I usually prefer using constructor injection, but in this case, this doesn’t seem possible. Constructor injection vs property injection. Public class Test : Page { [Import] public ILogger Logger { get; set; } protected void Page Load(object sender, EventArgs e) { Logger.Info("Works! Error occurred in ...

rubenherman.be

Ruben Herman – Ruben Herman

http://www.rubenherman.be/author/ruben-herman

Skip to main content. Dependency Injection in SharePoint 2013. If someone would ask me a while ago when I use property injection, I would definitely say NEVER. But then ASP.NET WebForms/SharePoint happened… I usually prefer using constructor injection, but in this case, this doesn’t seem possible. Constructor injection vs property injection. Public class Test : Page { [Import] public ILogger Logger { get; set; } protected void Page Load(object sender, EventArgs e) { Logger.Info("Works! Error occurred in ...

rubenherman.be

IoC Container in SharePoint 2013 Service – Ruben Herman

http://www.rubenherman.be/ioc-sp2013

Skip to main content. IoC Container in SharePoint 2013 Service. Since quite some time I started learning about Dependency Injection and IoC Containers. When I couldn’t find any solutions for SharePoint, I first thought it was impossible to do, especially constructor injection. But when I had a closer look, I started to imagine a solution for this particular problem and after a while I managed to get it working. So with no further ado, I present you my fix:. Packages SimpleInjector.Integration.Wcf...After...

rubenherman.be

SharePoint 2016 – Ruben Herman

http://www.rubenherman.be/category/sharepoint/sp2016

Skip to main content. When adding a new NuGet package to the Package folder in a SharePoint project, we often get this error, since not all packages are strongly named:. Error occurred in deployment step ‘Add Solution’: This solution contains one or more assemblies targeted for the global assembly cache. You should use a strong name for any assembly that will be in the global assembly cache. Dependency Injection in SharePoint 2013. Using EntityFramework in SharePoint. Sparkling Theme by Colorlib.

rubenherman.be

SharePoint – Ruben Herman

http://www.rubenherman.be/category/sharepoint

Skip to main content. Dependency Injection in SharePoint 2013. If someone would ask me a while ago when I use property injection, I would definitely say NEVER. But then ASP.NET WebForms/SharePoint happened… I usually prefer using constructor injection, but in this case, this doesn’t seem possible. Constructor injection vs property injection. Public class Test : Page { [Import] public ILogger Logger { get; set; } protected void Page Load(object sender, EventArgs e) { Logger.Info("Works! Error occurred in ...