![]() ![]() This would work for satellite assemblies, and any other logic that expects files next to the assemblies. ![]() We could define the output directory for CopyToOutputDirectory to be where the managed assemblies are located. The other solutions will at least work sometimes. The downside is of course that nothing that currently uses CopyToOutputDirectory will work. Document the alternatives, in particular how to specify where in the app bundle the files should go.Detect any files with CopyToOutputDirectory set and give a warning (telling the developer it won't work, and suggest to use another alternative).This would be to only put Content and BundleResource files in the app bundle: dll files either (when they come from items with CopyToOutputDirectory set), and then require some other mechanism (such as using Content or BundleResource items instead). I'm not sure I agree, I lean towards changing our current logic to not copy. ![]() dll files are special cased already it makes sense not to lose their path which is what my fix does. dll extension but they don't have DestinationSubDirectory property (unless it's somehow magically computed?), only TargetPath and RelativePath. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |