Note that there are some explanatory texts on larger screens.

plurals
  1. PONo definition found for user control member in compile time
    primarykey
    data
    text
    <p>I've run into the following problem:</p> <p>I've got a user control, on which I'v got a chart component developed by me. I'm trying to use the user control in the main application, and reach the chart component member from the main app's code something like this:</p> <pre><code>((VibraLysisUserControls.UC_SensorMonitor)(docContent.Content)).TimeDomainGraph </code></pre> <p>where TimeDomainGraph is the copmonent which resides in separate the dll in the project. The interesting point comes here: When I put the above line into the code behind I've got the following error message in compile time:</p> <blockquote> <p>'VibraLysisUserControls.UC_SensorMonitor' does not contain a definition for 'TimeDomainGraph' and no extension method 'TimeDomainGraph' accepting a first argument of type 'VibraLysisUserControls.UC_SensorMonitor' could be found (are you missing a using directive or an assembly reference?)</p> </blockquote> <p>If I comment out that line and go to debug the application, I can reach that member in the QuickWatch window when I stop the app at the point where I would like to use this. In fact, I just copied the code from the QuickWatch window, where it works perfectly.</p> <p>Anybody has some idea, what the hell is going on here? Why I can't reach a property in the code, which works just perfectly in the QuickWath window during debugging?</p> <p><strong>Update:</strong></p> <p>The problem is solved. I found out with some help. It was a visibility problem in XAML. Thanks for your help.</p> <p>Br, Csaba</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload