visual studio 2015 - VS Tools for Universal Windows Apps 1.1 can't create app package anymore -

-

i upgraded vs20154 visual studio tools universal windows apps. local build works fine in debugg configuration. when try create app package error:

severity code description project file line

manifest references file 'moneymanager.windows.dll' not part of payload.   moneymanager.windows    c:\users\ninop\documents\github\moneymanager\src\moneymanager.windows\package.appxmanifest

does anyhoner have idea how fix that?

thanks npadrutt

it appears there answer on msdn forums:

to workaround issue, add below itemgroup in project file , regenerate package.

<itemgroup> <appxsystembinary include="<assembly mentioned in error>" /> </itemgroup>

for example, if assembly name app1.dll, include:

<itemgroup> <appxsystembinary include="app1.dll" /> </itemgroup>

from: https://social.msdn.microsoft.com/forums/en-us/73f2d56d-9e8e-4b57-bcfa-0a972dfd75d7/update-11-generating-store-associated-package-fails-for-a-uwp-application-with-a-winrt-component?forum=win10sdktoolsissues


Comments

Post a Comment

Popular posts from this blog

java - Date formats difference between yyyy-MM-dd'T'HH:mm:ss and yyyy-MM-dd'T'HH:mm:ssXXX -

-
i trying parse date 2014-12-03t10:05:59.5646+08:00 using these 2 formats: yyyy-mm-dd't'hh:mm:ss yyyy-mm-dd't'hh:mm:ssxxx when parse using yyyy-mm-dd't'hh:mm:ss works fine, when parse yyyy-mm-dd't'hh:mm:ssxxx parseexception thrown. which correct format parse date , difference between these 2 formats? note : cannot use joda :( those valid formats: yyyy-mm-dd't'hh:mm:ss.sssz >>> e.g.: 2001-07-04t12:08:56.235-0700 yyyy-mm-dd't'hh:mm:ss.sssxxx >>> e.g.: 2001-07-04t12:08:56.235-07:00 edit: btw, "x" refer (iso 8601 time zone)
Read more

c# - Get rid of xmlns attribute when adding node to existing xml -

-
i have xml-file: <ns2:root xmlns:ns2="namespace"> <ns2:a> <ns2:b>some content</b> <ns2:c>some content</c> <ns2:d>some content</d> </a> </root> i need add new node in specific place, code is: var doc = xdocument.load(file); xnamespace ns2 = "namespace"; doc.element(ns2 + "root").element(ns2 + "a").element(ns2 + "c").addafterself( new xelement(ns2+"new", new xelement("new1", new xelement("new2","some content"), new xelement("new3", "some content")))); the output is: <ns2:root xmlns:ns2="namespace"> <ns2:a> <ns2:b>some content</b> <ns2:c>some content</c> <ns2:new> <new1 xmlns=""> <new2>some content</new2> ...
Read more