Eliminating error messages for "something isn't getting used

My son and I are maintaining and growing a 600,000 line VB6 program that we are converting to C#. We’re using a good (We like it.), professionally available program that is a HUGE help on getting the code organized and working. It’s also a great validation on what we are learning from your class. I’m starting to believe, “We can do this!”

My question is: We have about 3,000+ variables with 2 or 3 different levels of scope; and about another 3,000 more from files (their fields) that have the highest levels of scope. I like “libraries” of the most commonly used, as well as libraries of the more organized inclusion in their levels of scope based primarily on the parent files.

Now that’s what works in VB6. How can I do that without getting vast counts of error messages because “something isn’t getting used?” I do “SetStructure” when I instantiate the files; I do set the fields sizes of strings (strTmp = “00/00/00” or PumpkinDessert = “__” // we do almost everything as strings)

Thanks for reading through and responding, Rick C.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Tejas Trivedi9y ago
Hello Eric,

If i understood your question correctly, you are talking about the compiler warinings/complain when you have un-used variables in your code base.

There is way to disable compiler warnings while working on large code base which in turn gives you some time to correct your code properly without disturbing your productivity.

#pragma directives can help here to disable the compiler warnings. Below is Microsoft article which helps you investigate further on this direction.

https://msdn.microsoft.com/en-us/library/2c8f766e.aspx

Hope, this will help you out. Feel free to write if you need more information.

Please don't forget to mark as answer if this helps.
0