Reply to thread

Message

<blockquote data-quote="MJGraf" data-source="post: 1151146" data-attributes="member: 17886">You hit the nail - time is currently the issue.But I will certainly try to do this. I'm just still in the process of learning, because there are some things very different for xproj projects.What I e.g. didn't understand in the beginning is that NET451 is a completely different profile from DNX451. Both are targeting .Net 4.5.1. But NET451 is what Dawid Fowler in the linked thread calls &quot;vanilla .net&quot;, whereas DNX451 is the xproj version of that, which means it uses the &quot;Dot Net eXecution environment&quot; to get access to .net 4.5.1.Then for xproj projects you cannot create exe files anymore. There are only DLLs. And to start them you need DNX.exe - which is the DNX runtime. Once you realize that, this makes a lot of sense. Because on Linux or Apple, the DNX.exe is obviously different, but the DLL generated from your project remains the same. That way, the binaries generated from your project are platform independent. Of course this doesn't really make sense when you only target DNX451, because .Net 4.5.1 is not available for Linux or Apple. But they obviously didn't make a difference between projects targeting DNX451 and DNXCORE (because one project can target both). That seems to be the reason for this.And when you use DNX, there are a lot of additional goodies, for which, however, I'm not sure, yet, whether we shall use them. There is e.g. a built-in dependency injection system. It uses a very nice abstraction, for which they deliver a very nice and simple implementation. But you can also exchange this for e.g. NInject. In the long run, this could replace our ServiceRegistration (so that we could finally drop the ServiceLocator pattern, which would make writing UnitTests much easier).Well, as you see, there is a lot to find out <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="MJGraf, post: 1151146, member: 17886"] You hit the nail - time is currently the issue. But I will certainly try to do this. I'm just still in the process of learning, because there are some things very different for xproj projects. What I e.g. didn't understand in the beginning is that NET451 is a completely different profile from DNX451. Both are targeting .Net 4.5.1. But NET451 is what Dawid Fowler in the linked thread calls "vanilla .net", whereas DNX451 is the xproj version of that, which means it uses the "Dot Net eXecution environment" to get access to .net 4.5.1. Then for xproj projects you cannot create exe files anymore. There are only DLLs. And to start them you need DNX.exe - which is the DNX runtime. Once you realize that, this makes a lot of sense. Because on Linux or Apple, the DNX.exe is obviously different, but the DLL generated from your project remains the same. That way, the binaries generated from your project are platform independent. Of course this doesn't really make sense when you only target DNX451, because .Net 4.5.1 is not available for Linux or Apple. But they obviously didn't make a difference between projects targeting DNX451 and DNXCORE (because one project can target both). That seems to be the reason for this. And when you use DNX, there are a lot of additional goodies, for which, however, I'm not sure, yet, whether we shall use them. There is e.g. a built-in dependency injection system. It uses a very nice abstraction, for which they deliver a very nice and simple implementation. But you can also exchange this for e.g. NInject. In the long run, this could replace our ServiceRegistration (so that we could finally drop the ServiceLocator pattern, which would make writing UnitTests much easier). Well, as you see, there is a lot to find out :) [/QUOTE]

Verification