Use old DLLs (.NET) in a Windows Store app?

I started work on porting the application that I wrote for deployment to the Windows 8 application store. This requires the application to be written against a subset of the .NET platform. My application follows an architecture where the main functionality is its own dll, and things like accessing the file system are done through IoC. This basically means that the only dependency for the kernel dll is System. Because of this, I thought porting would be a breeze - adjust my IoC values ​​and plug in a GUI, then I will be fine. Only I can’t even refer to my main dll from the store store application (met.ka metro application).

Did I miss something? Do I need to rewrite my main dll only for inclusion in the Windows 8 application store? We are told that if you use good architecture, then porting will be a breeze, and that is what I did. Was that a big lie?

+5
source share
3 answers

Windows ( ) .NET Core Profile. Core . . .NET Framework . , .NET Framework, Windows. , , .NET WinRT.

+4

, . Metro . .Net, (, System.Data, System.IO ). Metro , , ( , , , , ).

, PInvoke "" API Win32.

. API Win32: http://msdn.microsoft.com/en-us/library/windows/apps/hh464945.aspx

. API Win32/COM: http://msdn.microsoft.com/en-us/library/windows/apps/br205762.aspx

, "" , , . , (, , ), , , ( System.Data, , ). , , API, , .

+1

I had the same problem: the project for the Metro application does not load the dll with the .4 framework. I changed the structure from 4 to 3.5 for the dll, and now the Metro project will see them.

0
source

All Articles