Declaring a class for use in multiple code files

Greetings,

I'm using the following code in a separate file to declare a namespace for writing output files:

using System;
using System.IO;

namespace AutoWriteToFile
{
    public class FileWriter
    {
        // Set this to false to stop writing to file
        private static bool _WriteToFile = true;
        private TextWriter tw;

        void WriteToFile(string FileDest, string StrOutput)
        {

            if (_WriteToFile)
            {                

                try
                {
                    // create a writer and open the file
                    tw = new StreamWriter(FileDest);

                    // write a line of text to the file
                    tw.WriteLine(StrOutput);
                }
                catch (Exception ex)
                {
                    ex.Message.ToString();
                }
                finally
                {
                    // close the stream
                    tw.Close();
                }
            }
        }
    }
}

My problem is related to declaring the class in other files.  For instance, if I want to use this routine in Form1 I would declare the namespace:

using ....
using AutoWriteToFile;

... But how should I declare the class in the Form1 class so I can access the WriteToFile() function?

public partial class Form1 : Form
    {

        public FileWriter FW = new FileWriter();   ????????????????
       
        public Form1()
        {
               
                InitializeComponent();
        }

        ...
        ...
        public void FormCreate(object sender, EventArgs e)
        {
            FW. ???????  This is not working

        ...
        ...

Thank you!
John500Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
käµfm³d 👽Connect With a Mentor Commented:
You didn't specify an accessor on the WriteToFile method. This means, in C#, that it defaults to internal, which cannot be accessed outside of the assembly which contains the method definition. If you are still within the same assembly (i.e. same project), then that should be fine. However, if you put this code into its own project which the form project references, then you will need to change your method definition to:

...

public void WriteToFile(string FileDest, string StrOutput)
{
...

Open in new window

0
 
AndyAinscowFreelance programmer / ConsultantCommented:
You almost have it.

namespace AutoWriteToFile
{
    public class FileWriter
    {
      public FileWriter() {};
0
 
John500Author Commented:
Andy,

Thanks for the input.  I tried inserting exactly how you suggested but it won't compile.  What am I missing?  Can you include the rest of my code as it should appear after the:

public FileWriter() {};

Thanks
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
John500Author Commented:
I took out the semicolon and it compiled but within Form1, I don't get access to the function WriteToFile() when I type FW..

This code is being used in VS 2008 and has worked before.  I'm not even sure why the line you mentioned is necessary.  Please advise, thank you !
0
 
John500Author Commented:
Thank you
0
 
AndyAinscowFreelance programmer / ConsultantCommented:
Aha - I thought you had a problem with not being able to instance the class (for some reason I thought it generated a default private constructor hence my suggestion to make a public constructor).


public partial class Form1 : Form
    {

        public FileWriter FW = new FileWriter();   ????????????????
0
 
käµfm³d 👽Commented:
@AndyAinscow

But that declares a publicly-accessible field in Form1. Ordinarily, one wouldn't want to expose a field as public.
0
 
AndyAinscowFreelance programmer / ConsultantCommented:
@kaufmed - I agree with you about coding styles re member variables and accessibility BUT I thought the asker meant he was getting an error at that line (which would result in not being able to use any functions in the class).
0
 
AndyAinscowFreelance programmer / ConsultantCommented:
ps.  I was unavailable from posting my first comment until after the question was closed, I'm just pointing out that the question didn't clearly state where the error was.  I took the row of query signs as a hint to the faulting line.
0
 
käµfm³d 👽Commented:
@AndyAinscow

I didn't realize you were quoting the OP. My mistake : )
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.