Depends on what you're looking for. The issue isn't really "importing" the code references as much as it is a scoping issue. That is, imports are largely used t

Depends on what you're looking for. The issue isn't really "importing" the code references as much as it is a scoping issue. That is, imports are largely used to define scope for the file and mostly for the programmers benefit (so you're typing, say, Button.DoSomething instead of System.Windows.Controls.Interactive.Button.DoSomething). That and the odd namespace clash that a compiler can't really resolve, but that is more due to implementation and system issues, not programming proper.