What tools are used on the Microsoft Store to build a msixupload file

%3CLINGO-SUB%20id%3D%22lingo-sub-1993535%22%20slang%3D%22en-US%22%3EWhat%20tools%20are%20used%20on%20the%20Microsoft%20Store%20to%20build%20a%20msixupload%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1993535%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWe%20faced%20an%20issue%20earlier%20this%20year%20when%20we%20uploaded%20a%20msixupload%20package%20to%20the%20Microsoft%20Store.%3CBR%20%2F%3E%3CBR%20%2F%3EOur%20project%20is%20mainly%20a%20Windows%20Desktop%20Application%20Package%20that%20includes%20a%20UWP%20project%20and%20Win32%20project%20that%20runs%20with%20full%20trust%20capabilities.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EThis%20package%20was%20built%20using%20VS2017.%20Then%20when%20we%20ran%20the%20program%20from%20the%20store(we%20did%20the%20submission%20privately)%2C%20we%20got%20the%20following%20exception%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E%22Resolution%20of%20the%20dependency%20failed%2C%20type%20%3D%20%5C%22X.Views.ShellPage%5C%22%2C%20name%20%3D%20%5C%22(none)%5C%22.%0AException%20occurred%20while%3A%20Calling%20constructor%20X.Views.ShellPage().%0AException%20is%3A%20XamlParseException%20-%20The%20text%20associated%20with%20this%20error%20code%20could%20not%20be%20found.%0A%0AFailed%20to%20assign%20to%20property%20'Prism.Windows.Mvvm.ViewModelLocator.AutoWireViewModel'.%20%5BLine%3A%200%20Position%3A%200%5D%0A-----------------------------------------------%0AAt%20the%20time%20of%20the%20exception%2C%20the%20container%20was%3A%0A%0A%20%20Resolving%20X.Views.ShellPage%2C(none)%0A%20%20Calling%20constructor%20X.Views.ShellPage()%0A%20%20%20at%20Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type%2C%20Object%2C%20String%2C%20IEnumerable%601)%20%2B%200x146%0A%20%20%20at%20Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type%2C%20String%2C%20IEnumerable%601)%20%2B%200xf%0A%20%20%20at%20Microsoft.Practices.Unity.UnityContainerExtensions.Resolve%5BT%5D(IUnityContainer%2C%20ResolverOverride%5B%5D)%20%2B%200x31%0A%20%20%20at%20X.App.CreateShell(Frame)%20%2B%200x30%0A%20%20%20at%20Prism.Windows.PrismApplication.%3CINITIALIZESHELL%3Ed__52.MoveNext()%20%2B%200xc4%0A---%20End%20of%20stack%20trace%20from%20previous%20location%20where%20exception%20was%20thrown%20---%0A%20%20%20at%20System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()%20%2B%200x1c%0A%20%20%20at%20System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task)%20%2B%200x60%0A%20%20%20at%20System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task)%20%2B%200x36%0A%20%20%20at%20System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task)%20%2B%200x16%0A%20%20%20at%20System.Runtime.CompilerServices.TaskAwaiter.GetResult()%20%2B%200x9%0A%20%20%20at%20Prism.Windows.PrismApplication.%3CONLAUNCHED%3Ed__53.MoveNext()%20%2B%200x49%0A---%20End%20of%20stack%20trace%20from%20previous%20location%20where%20exception%20was%20thrown%20---%0A%20%20%20at%20System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()%20%2B%200x1c%0A%20%20%20at%20System.Runtime.CompilerServices.AsyncMethodBuilderCore.%26lt%3B%26gt%3Bc.%3CTHROWASYNC%3Eb__7_0(Object)%20%2B%200x19%0A%20%20%20at%20System.Action%601.Invoke(T)%20%2B%200x1e%0A%20%20%20at%20System.Threading.WinRTSynchronizationContext.Invoker.InvokeCore()%20%2B%200x2b%0A%3CUNKNOWN%3EThe%20text%20associated%20with%20this%20error%20code%20could%20not%20be%20found.%0A%0AFailed%20to%20assign%20to%20property%20'Prism.Windows.Mvvm.ViewModelLocator.AutoWireViewModel'.%20%5BLine%3A%200%20Position%3A%200%5D%20%20%20at%20System.Runtime.InteropServices.McgMarshal.ThrowOnExternalCallFailed(Int32%2C%20RuntimeTypeHandle)%20%2B%200x1d%0A%20%20%20at%20__Interop.ComCallHelpers.Call(__ComObject%2C%20RuntimeTypeHandle%2C%20Int32%2C%20Void*%2C%20Void*%2C%20Int32)%20%2B%200x95%0A%20%20%20at%20Windows.UI.Xaml.IApplicationStatics__Impl.Stubs.LoadComponent(__ComObject%2C%20Object%2C%20Uri%2C%20ComponentResourceLocation)%20%2B%200x50%0A%20%20%20at%20X.Views.ShellPage.InitializeComponent()%20%2B%200x4d%0A%20%20%20at%20X.Views.ShellPage..ctor()%20%2B%200x13%0A%20%20%20at%20_%24ILCT%24.%24ILT%24ReflectionDynamicInvoke%24.InvokeRetV(Object%2C%20IntPtr%2C%20InvokeUtils.ArgSetupState%26amp%3B%2C%20Boolean)%20%2B%200x2f%0A%20%20%20at%20System.InvokeUtils.CalliIntrinsics.Call(IntPtr%2C%20Object%2C%20IntPtr%2C%20InvokeUtils.ArgSetupState%26amp%3B%2C%20Boolean)%20%2B%200x2c%0A%20%20%20at%20System.InvokeUtils.CallDynamicInvokeMethod(Object%2C%20IntPtr%2C%20Object%2C%20IntPtr%2C%20IntPtr%2C%20Object%2C%20Object%5B%5D%2C%20BinderBundle%2C%20Boolean%2C%20Boolean%2C%20Boolean)%20%2B%200x119%0A---%20End%20of%20stack%20trace%20from%20previous%20location%20where%20exception%20was%20thrown%20---%0A%20%20%20at%20System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()%20%2B%200x1c%0A%20%20%20at%20System.Linq.Expressions.Interpreter.ExceptionHelpers.UnwrapAndRethrow(TargetInvocationException)%20%2B%200x14%0A%20%20%20at%20System.Linq.Expressions.Interpreter.NewInstruction.Run(InterpretedFrame)%20%2B%200x8b%0A%20%20%20at%20System.Linq.Expressions.Interpreter.Interpreter.Run(InterpretedFrame)%20%2B%200x25%0A%20%20%20at%20System.Linq.Expressions.Interpreter.LightLambda.Run(Object%5B%5D)%20%2B%200x96%0A%20%20%20at%20System.Func%602.Invoke(T)%20%2B%200x23%0A%20%20%20at%20System.Runtime.CompilerServices.ConditionalWeakTable%602.CreateValueCallback.InvokeObjectArrayThunk(TKey)%20%2B%200x44%0A%20%20%20at%20Microsoft.Practices.ObjectBuilder2.DynamicBuildPlanGenerationContext.%26lt%3B%26gt%3Bc__DisplayClass1.%3CGETBUILDMETHOD%3Eb__0(IBuilderContext)%20%2B%200x31%0A%20%20%20at%20System.Diagnostics.DiagnosticSourceEventSource.CallbackObserver%601.OnNext(T)%20%2B%200x1e%0A%20%20%20at%20Microsoft.Practices.ObjectBuilder2.BuildPlanStrategy.PreBuildUp(IBuilderContext)%20%2B%200xd3%0A%20%20%20at%20Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext)%20%2B%200x11b%0A%20%20%20at%20Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type%2C%20Object%2C%20String%2C%20IEnumerable%601)%20%2B%200x109%0A%3CUNKNOWN%3E%22%3C%2FUNKNOWN%3E%3C%2FGETBUILDMETHOD%3E%3C%2FUNKNOWN%3E%3C%2FTHROWASYNC%3E%3C%2FONLAUNCHED%3E%3C%2FINITIALIZESHELL%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20the%20message%20shows%2C%20something%20went%20wrong%20with%20Prism.%20We%20were%20using%20an%20older%20version%20of%20Prism%206.3%20for%20UWP.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EAfter%20building%20the%20package%20with%20VS2019%2C%20we%20were%20able%20to%20run%20the%20application%20with%20no%20issues.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ENo%20we%20are%20looking%20to%20move%20away%20from%20Prism%20to%20have%20something%20more%20sustainable.%20However%2C%20we%20would%20still%20like%20to%20know%20what%20we%20could%20do%20to%20avoid%20future%20situations%20where%20the%20different%20build%20environments%20will%20allow%20our%20app%20to%20run%20or%20not%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EOr%20was%20this%20a%20bug%20in%20VS2017%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EAny%20help%20would%20be%20appreciated%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2076873%22%20slang%3D%22en-US%22%3ERe%3A%20What%20tools%20are%20used%20on%20the%20Microsoft%20Store%20to%20build%20a%20msixupload%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2076873%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F903870%22%20target%3D%22_blank%22%3E%40eliasaj%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBased%20on%20the%20information%20you've%20provided%20the%20issue%20could%20be%20related%20to%20the%20target%20%2F%20min%20version%20is%20for%20the%20project.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-%20Roy%3C%2FP%3E%3C%2FLINGO-BODY%3E
Visitor

Hello,


We faced an issue earlier this year when we uploaded a msixupload package to the Microsoft Store.

Our project is mainly a Windows Desktop Application Package that includes a UWP project and Win32 project that runs with full trust capabilities.

This package was built using VS2017. Then when we ran the program from the store(we did the submission privately), we got the following exception:

"Resolution of the dependency failed, type = \"X.Views.ShellPage\", name = \"(none)\".
Exception occurred while: Calling constructor X.Views.ShellPage().
Exception is: XamlParseException - The text associated with this error code could not be found.

Failed to assign to property 'Prism.Windows.Mvvm.ViewModelLocator.AutoWireViewModel'. [Line: 0 Position: 0]
-----------------------------------------------
At the time of the exception, the container was:

  Resolving X.Views.ShellPage,(none)
  Calling constructor X.Views.ShellPage()
   at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type, Object, String, IEnumerable`1) + 0x146
   at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type, String, IEnumerable`1) + 0xf
   at Microsoft.Practices.Unity.UnityContainerExtensions.Resolve[T](IUnityContainer, ResolverOverride[]) + 0x31
   at X.App.CreateShell(Frame) + 0x30
   at Prism.Windows.PrismApplication.<InitializeShell>d__52.MoveNext() + 0xc4
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x1c
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x60
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x36
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x16
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0x9
   at Prism.Windows.PrismApplication.<OnLaunched>d__53.MoveNext() + 0x49
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x1c
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__7_0(Object) + 0x19
   at System.Action`1.Invoke(T) + 0x1e
   at System.Threading.WinRTSynchronizationContext.Invoker.InvokeCore() + 0x2b
<unknown>The text associated with this error code could not be found.

Failed to assign to property 'Prism.Windows.Mvvm.ViewModelLocator.AutoWireViewModel'. [Line: 0 Position: 0]   at System.Runtime.InteropServices.McgMarshal.ThrowOnExternalCallFailed(Int32, RuntimeTypeHandle) + 0x1d
   at __Interop.ComCallHelpers.Call(__ComObject, RuntimeTypeHandle, Int32, Void*, Void*, Int32) + 0x95
   at Windows.UI.Xaml.IApplicationStatics__Impl.Stubs.LoadComponent(__ComObject, Object, Uri, ComponentResourceLocation) + 0x50
   at X.Views.ShellPage.InitializeComponent() + 0x4d
   at X.Views.ShellPage..ctor() + 0x13
   at _$ILCT$.$ILT$ReflectionDynamicInvoke$.InvokeRetV(Object, IntPtr, InvokeUtils.ArgSetupState&, Boolean) + 0x2f
   at System.InvokeUtils.CalliIntrinsics.Call(IntPtr, Object, IntPtr, InvokeUtils.ArgSetupState&, Boolean) + 0x2c
   at System.InvokeUtils.CallDynamicInvokeMethod(Object, IntPtr, Object, IntPtr, IntPtr, Object, Object[], BinderBundle, Boolean, Boolean, Boolean) + 0x119
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x1c
   at System.Linq.Expressions.Interpreter.ExceptionHelpers.UnwrapAndRethrow(TargetInvocationException) + 0x14
   at System.Linq.Expressions.Interpreter.NewInstruction.Run(InterpretedFrame) + 0x8b
   at System.Linq.Expressions.Interpreter.Interpreter.Run(InterpretedFrame) + 0x25
   at System.Linq.Expressions.Interpreter.LightLambda.Run(Object[]) + 0x96
   at System.Func`2.Invoke(T) + 0x23
   at System.Runtime.CompilerServices.ConditionalWeakTable`2.CreateValueCallback.InvokeObjectArrayThunk(TKey) + 0x44
   at Microsoft.Practices.ObjectBuilder2.DynamicBuildPlanGenerationContext.<>c__DisplayClass1.<GetBuildMethod>b__0(IBuilderContext) + 0x31
   at System.Diagnostics.DiagnosticSourceEventSource.CallbackObserver`1.OnNext(T) + 0x1e
   at Microsoft.Practices.ObjectBuilder2.BuildPlanStrategy.PreBuildUp(IBuilderContext) + 0xd3
   at Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext) + 0x11b
   at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type, Object, String, IEnumerable`1) + 0x109
<unknown>"

 

As the message shows, something went wrong with Prism. We were using an older version of Prism 6.3 for UWP.

After building the package with VS2019, we were able to run the application with no issues.


No we are looking to move away from Prism to have something more sustainable. However, we would still like to know what we could do to avoid future situations where the different build environments will allow our app to run or not?


Or was this a bug in VS2017?


Any help would be appreciated

1 Reply
Microsoft Verified Best Answer

Hi @eliasaj,

 

Based on the information you've provided the issue could be related to the target / min version is for the project.

 

- Roy