Replies: 1 comment
-
| 
 Hopefully #6561 is gonna make it soon to get rid of this ugly attribute. IntelliSense usually works fine but it takes a configuration swap and re-open the file, or if the file is shared in multiple assemblies, just swap to one and then it catches up. | 
Beta Was this translation helpful? Give feedback.
                  
                    0 replies
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
-
I'm getting many Visual Studio errors when working with the WPF repo. Many of the errors are simple namespace-related issues.
For example, if I open the file
src\PresentationCore\System\Windows\Media\textformatting\TextLineBreak.cs:Upon investigation, the
SecurityCriticalDataForSet<T>is implemented in theMs.Internalnamespace, and navigating tosrc\Shared\MS\Internal\SecurityCriticalDataForSet.csshows that the type definition isinternal struct SecurityCriticalDataForSet<T>.Note that within
TextLineBreak.csI can see Visual Studio warning me of an unused using statementusing Ms.Internal. The types within Ms.Internal are not being exposed correctly as they are internal.grepping the entire repository shows that
InternalsVisibleTotext is not present anywhere in the repo (I assume WPF predates the invention of this attribute).Therefore some other mechanism is exposing internal types to external assemblies.I believe it is the
FriendAccessAllowedAttribute. There must be something missing in my cloned repository that is not resolving correctly.Can anyone help explain what I need to do to have the internals exposed to friend assemblies correctly.
Beta Was this translation helpful? Give feedback.
All reactions