wondering where to get started

%3CLINGO-SUB%20id%3D%22lingo-sub-2220261%22%20slang%3D%22en-US%22%3Ewondering%20where%20to%20get%20started%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2220261%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20recently%20started%20a%20new%20job%20where%20i%20have%20the%20responsibility%20to%20migrate%20all%20our%20applications%20to%20.NET%205.%20I%20am%20starting%20with%20a%20small%20application%20that%3CSPAN%3E%26nbsp%3Bis%20a%20combination%20of%20C%23%2C%20Managed%20C%2B%2B%20and%20Native%20C%2B%2B%20projects.%20One%20of%20these%20projects%20is%20a%20dll%20project%20that%20during%20the%20release%20build%20gets%20encrypted%20as%20part%20of%20a%20post%20build%20event.%20This%20application%20has%20been%20successfully%20migrated%20.NET%205.%20Now%20i%20need%20to%20fix%20the%20existing%20installer%20and%20make%20it%20work%20with%20the%20new%20changes.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20currently%20create%20the%20installer%20by%20using%20the%20VS%20Installer%20Project.%26nbsp%3BThe%20problem%20with%20this%20is%20that%20.NET%205%20now%20has%20to%20be%20a%20Launch%20Condition%2FDependency.%20The%20launch%20conditions%20only%20goes%20up%20to%20.NET%20Framework%204.8.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20has%20me%20looking%20at%20the%20MSIX%20setup.%20the%20problem%20i%20am%20running%20into%20is%20that%20MSIX%20seems%20to%20rely%20on%20being%20able%20to%20read%20the%20dependencies%20of%20the%20projects%20to%20decide%20which%20files%20to%20include.%20This%20turns%20out%20to%20be%20a%20problem%20with%20the%20encrypted%20dll%20because%20it%20is%20not%20seen%20as%20a%20dependency.%20In%20the%20VS%20installer%20projects%20we%20could%20explicitly%20state%20that%20that%20file%20needs%20to%20be%20included.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAny%20help%20or%20advice%20would%20be%20appreciated.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273009%22%20slang%3D%22en-US%22%3ERe%3A%20wondering%20where%20to%20get%20started%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273009%22%20slang%3D%22en-US%22%3EHi!%20I%20would%20start%20off%20with%20looking%20at%20our%20documentation%20with%20creating%20an%20MSIX%20if%20you%20have%20the%20source%20code%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fdesktop%2Fsource-code-overview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fdesktop%2Fsource-code-overview%3C%2FA%3E%20%3CBR%20%2F%3EIn%20particular%2C%20look%20at%20the%20following%20documentation%20to%20package%20apps%20in%20VS%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpackage%2Fpackaging-uwp-apps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpackage%2Fpackaging-uwp-apps%3C%2FA%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

I have recently started a new job where i have the responsibility to migrate all our applications to .NET 5. I am starting with a small application that is a combination of C#, Managed C++ and Native C++ projects. One of these projects is a dll project that during the release build gets encrypted as part of a post build event. This application has been successfully migrated .NET 5. Now i need to fix the existing installer and make it work with the new changes.

We currently create the installer by using the VS Installer Project. The problem with this is that .NET 5 now has to be a Launch Condition/Dependency. The launch conditions only goes up to .NET Framework 4.8.

This has me looking at the MSIX setup. the problem i am running into is that MSIX seems to rely on being able to read the dependencies of the projects to decide which files to include. This turns out to be a problem with the encrypted dll because it is not seen as a dependency. In the VS installer projects we could explicitly state that that file needs to be included.

 

Any help or advice would be appreciated.

1 Reply
Hi! I would start off with looking at our documentation with creating an MSIX if you have the source code: https://docs.microsoft.com/en-us/windows/msix/desktop/source-code-overview
In particular, look at the following documentation to package apps in VS https://docs.microsoft.com/en-us/windows/msix/package/packaging-uwp-apps