Now, my solution is being kept from building because of warnings !

[Junior]

Some weeks ago, my application was running okay even though the above
warnings were already being showed. Now, it is refusing to build because of
them. It's a C# project that runs along with a couple of other VB projects in
the same solution. Have I touched the wrong buttons and rendered the solution
impossible to execute ? Where can I configure that in Visual Studio .NET 2003
?

C:\SC\CEJef\Jef.cs(145): Field 'CEJef.Jef.RECT.bottom' is never assigned to,
and will always have its default value 0

C:\SC\CEJef\Jef.cs(133): Field 'CEJef.Jef.SIPINFO.fdwFlags' is never
assigned to, and will always have its default value 0

Thanks a lot.

Jr

[Oliver Sturm]

Junior wrote:

Some weeks ago, my application was running okay even though the above
warnings were already being showed. Now, it is refusing to build because of
them. It's a C# project that runs along with a couple of other VB projects
in
the same solution. Have I touched the wrong buttons and rendered the
solution
impossible to execute ? Where can I configure that in Visual Studio .NET
2003
?

C:\SC\CEJef\Jef.cs(145): Field 'CEJef.Jef.RECT.bottom' is never assigned
to,
and will always have its default value 0

C:\SC\CEJef\Jef.cs(133): Field 'CEJef.Jef.SIPINFO.fdwFlags' is never
assigned to, and will always have its default value 0

If you are absolutely sure there's no error message in the list somewhere,
I can only guess that you have set the option "Treat warnings as errors"
to True, which is on the Build tab of the project properties dialog.
Normally, a bunch of warnings shouldn't stop you from compiling and
running your application.

That said, these warnings are there for a reason. You should really go
over them, try to understand what they mean and make changes accordingly.
As a side effect, it'll be much easier to spot those important messages in
between all the others ;-)

Oliver Sturm
--
Expert programming and consulting services available
See http://www.sturmnet.org (try /blog as well)

[Junior]

Oliver, thanks for the hint on "treat warnings as errors", and also for the
mature suggestions on addressing the warnings as problems to be solved, not
ignored.

I bookmarked your homepage, and will resort to you in a more professional,
paid way it things get nasty around here.

Thank you, Jr.

"Oliver Sturm" wrote:

Junior wrote:

Some weeks ago, my application was running okay even though the above
warnings were already being showed. Now, it is refusing to build because of
them. It's a C# project that runs along with a couple of other VB projects
in
the same solution. Have I touched the wrong buttons and rendered the
solution
impossible to execute ? Where can I configure that in Visual Studio .NET
2003
?

C:\SC\CEJef\Jef.cs(145): Field 'CEJef.Jef.RECT.bottom' is never assigned
to,
and will always have its default value 0

C:\SC\CEJef\Jef.cs(133): Field 'CEJef.Jef.SIPINFO.fdwFlags' is never
assigned to, and will always have its default value 0

If you are absolutely sure there's no error message in the list somewhere,
I can only guess that you have set the option "Treat warnings as errors"
to True, which is on the Build tab of the project properties dialog.
Normally, a bunch of warnings shouldn't stop you from compiling and
running your application.

That said, these warnings are there for a reason. You should really go
over them, try to understand what they mean and make changes accordingly.
As a side effect, it'll be much easier to spot those important messages in
between all the others ;-)

Oliver Sturm
--
Expert programming and consulting services available
See http://www.sturmnet.org (try /blog as well)