How do I pass an object from one class to another

Question

0.00/5 (No votes)

See more:

Hello,
I am new to C#. I have an application which calls a DataBaseIO class method to read through an SQL database table. This method creates a new instance of a User object and populates the instance with data read from the input table. In debug I can see that the instance is updated with the correct data.

However when control returns from this DataBaseIO method to the calling method ,the object is null. The calling method is in source Transaction.cs and the object is created in DataBaseIO.cs. How can I pass the object back to the calling method in Transaction.cs ?

regards
Pat

Posted 19-Oct-14 10:22am

PClarkeirl

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

BillWoodruff · Answer 1 · 2014-10-19T10:36:00

Make the return value of the method in the DataBaseIO class return the User Object it creates to the call-site of the method in the Transaction class.

If you can call method in DataBaseIO, as you indicate, that means, to me, that your Transaction class has a valid reference to it.

Or, if you don't wish to expose the "whole" User Type object, you could create accessor methods in the DataBaseIO class that selectively exposed what you wished to expose in the User Type object.