Is anyone aware of or written a SimpleInjector flavour of IContainerConfiguration for the Enterprise Library 5. I've found one for Castle and Autofac and started to write my own but I admit I'm struggling.
For reference: The Castle and autofac flavour
Related
Is Windows Community Toolkit IoC anyhow capable to receive pre-configured modules by NInject, for example ?
DryIoC is having modules on its roadmap so maybe that will become also neat so that we can deploy the dependency configurations to the Unit Tests.
Anyhow possible to achieve this with the Community Toolkit IoC or is there an existing plan on any1's desk ?
I'm using Wix 3.8 for building my installer files. For my boostrapper bundle I want to build my own gui with the ManagedBootstrapperApplicationHost. I found an example at: Custom WiX Managed Bootstrapper Application
This application is using MvvM Light. How can I use Caliburn Micro and Mef instead? I have tried to build up the standard mef bootstrapper and call:
new AppBootstrapper();
in my overridden Run method. But I get a NullReference exception here. How can I manually call the Caliburn Micro Bootstrapper from code?
Regards Markus
I'm trying to create a Breeze Web API controller and I'm wondering if it is possible with the default MVC/Web API project template that comes with Visual Studio 2013. Updating everything through the Nuget packet manager installs Entity Framework 6.0.1. Attempting to installing Breeze after that results in an error as it attempts to install EF 5 as a dependency, which is not possible given the fact that other parts of the template depend on EF6.
Do we have to wait for a new version of Breeze that works with EF6?
Edit: I want to do this the "breeze way" using [BreezeController] and Odata.
I just wanted to add that even without EF6.1, the MVC 5 updates released today with VS2013 also break breeze. It's hard to separate the pieces to determine which new piece is responsible. It could be MVC or the new odata. In any case, we anxiously anticipate the new version.
Updated 10/29/13
As of now, Breeze 1.4.5 has support for Microsoft's ASP.NET WebApi 2 and Entity Framework 6. Please see http://www.breezejs.com/documentation/download.
Older post:
We don't yet support EF6 but it is coming ... soon...
There is a new package called Breeze.WebApi2 that is compatible with Web API2 and EntityFramework 6. It makes some of the existing Breeze packages obsolete. See http://www.breezejs.com/documentation/start-nuget for details.
In the book MCTS Self-Paced Training Kit (Exam 70-502): Microsoft® .NET Framework 3.5 Windows® Presentation Foundation there is a topic about XBAP deployment using ClickOnce. I’ve discussed with some colleagues and all said that it doesn’t make any sense. So why is in the book XBAP deployment with ClickOnce covered? I think there must be a basic reason but honestly I don’t get it. What do you trink?
I have inherited an application that is running on JBoss 2.4.3 (which I believe is EJB spec 2.0 compatible), and I'm running into quite a few issues (like being able to use modern log4j "Logger" apis [JBoss 2.4 specific issues pushing me to upgrade]).
I understand that I should be able to use a EJB 2.1 container (Jboss 4) without issue, but should I expect to be able to go further?
What are the backwards compatibility requirements for EJB?
Are they meant to be backwards compatible through major versions?
Do application vendors make them fully backwards compatible?
What modifications are necessary to make an older application conform? (small or large? application configuration or re-compilation? etc)
log4j and EJB 2.0 are not related. If you have problems with log4j, then most likely it is a class path issue and not EJB 2.0 compatbility issue. Probably your old application assumes that log4j is somewhere on system class path.
http://what-when-how.com/enterprise-javabeans-3/backward-compatibility-and-interoperability-with-ejb-2/ states that
The EJB 3 specification requires that all complying containers support EJB 2
Which is a good sign. It goes on further to talk about mixing EJB 2 and 3 functionality. So there may be some exceptions, but it really shouldn't be any where near impossible.
Reality may be different; I'll update if I find problems with my jboss upgrade.
See this compatibility report for the EJB library: