Search

Linked files in folders are not output correctly in WPF by StefanOlson

Active

5
0
Sign in
to vote
Type: Bug
ID: 512027
Opened: 11/18/2009 5:12:52 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Often I will link to shared resources such as images and xaml files. Unfortunately, in WPF if I place them below a folder they are not placed with a folder name in the output resources.

This is the WPF version of this Silverlight bug: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=428412

The issue is fixed in Silverlight 4 but not in WPF 4. This absolutely needs to be fixed before WPF ships - it makes single sourcing an absolute nightmare.
Details (expand)

Product Language

English

Version

.NET Framework 4 Beta 2

Operating System

Windows 7

Operating System Language

English

Steps to Reproduce

Create a folder in a solution
Add a xaml file as a linked item below that folder
Reference the xaml file in app.xaml.
Inspect the exe in reflector after it has built.

Actual Results

in the .g.resources, the file will not have a folder name. In the enclosed example see colors.baml.

Expected Results

Should be resources/colors.baml.
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
File Name Submitted By Submitted On File Size  
LinkedFilesBug.zip (restricted) 11/18/2009 -
Sign in to post a comment.
Posted by Geert van Horrik on 6/9/2011 at 3:20 PM
Too bad you don't fix this, since this is really a bug that should be fixed.
Posted by Microsoft on 11/23/2009 at 5:35 PM
Thanks for notifying us of this problem. Unfortunately, we won't be able to address this in .NET 4. In our version 4, linked resources were enabled in WPF applications for everything bug "Pages", but at this point, we won't be able to address that remaining issue in time for .NET 4's release.
Thanks,
WPF Team
Posted by Microsoft on 11/19/2009 at 9:56 PM
Please ignore the previous message. We are routing this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 11/19/2009 at 9:55 PM
Thanks for the feedback, but we only accept feedback in English at this time. We are therefore closing this issue. We would greatly appreciate it if you could submit this issue again in english.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 11/19/2009 at 4:16 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.