User Profile
scoban
MicrosoftJoined 6 years ago
User Widgets
Recent Discussions
Re: Pre Build Action in Windows Application Project
abhisinghal I was not able to reproduce the issue with the provided project. I noticed you have some commented out prebuild events which could be causing it if you are testing with those uncommented. I need a repro so that I can investigate further.3.6KViews0likes0CommentsRe: Pre Build Action in Windows Application Project
abhisinghal I was able to successfully package that app with a more recent version of Visual Studio and even tried with a slightly older version. Try deleting your bin/obj folders (Clean the project). Did you see the error with the sample project as well?3.7KViews0likes3CommentsRe: Pre Build Action in Windows Application Project
abhisinghal What is the scenario you are trying to enable that does not work with normal project references? If you really need this behavior I would suggest using an itemgroup for the files that you want, This is not really recommended as the projects that you reference should be including all the files needed for packaging and they also include additional metadata that we use for other reasons. In other words this could have unintended side effects depending on what you are doing. <ItemGroup> <None Include="SomeDir\*"> <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory> </None> </ItemGroup>3.9KViews0likes8CommentsRe: WPF app that has multiple targets
mylastsong18 You can fix that error by adding this to your .wapproj file: <PropertyGroup> <AssetTargetFallback>$(AssetTargetFallback);netcoreapp3.1;netcoreapp3.0;netcoreapp2.0;net462;net47;net471;net472;net48</AssetTargetFallback> </PropertyGroup> However, this will still not work as you intend. The packaging project was not built with the idea that you could/would build a .msix package for different frameworks, only different platforms (x86/x64/etc...) Just so I can understand what you are trying to do fully, how would you expect a .msix would work with different framework applications in it from a customer perspective?1.4KViews0likes1CommentRe: Pre Build Action in Windows Application Project
abhisinghal This appears to be an ordering issue, you need to move the <PreBuildEvent> propertygroup in the .wapproj below the import for the .targets at the bottom of the file. Out of curiosity, what are you using the copy PreBuildEvent for? The Packaging Project will not pick up the files in the output folder to package unless you have another step to add them to the package, so I am not sure why you would want to copy these files there?4KViews0likes10Comments
Recent Blog Articles
No content to show