Re: Code Standard 2.0 new objects outside of Try Block
- From: "Siva M" <shiva_sm@xxxxxxxxxxxxxxxxx>
- Date: Wed, 9 Aug 2006 20:31:56 +0530
Gabe,
Just assign null to the variables - this should stop those warnings. You
don't necessarily have to instantiate the objects.
"gabe" <gabedog@xxxxxxxxx> wrote in message
news:1155134537.290769.36560@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have question about code standards in VS 2005
I have been declaring objects before a try block in case I would ever
want to refer to them in 'Catch' block. When I converted my apps to 2.0
I get warnings that objects have been declared, but not initialized.
I've hesitated to actually 'New' an object outside of a try in the
event of an exception occurring. For example, if I new up a Connection
object with a connection string with an incorrect syntax it will throw
an InvalidArgument exception.
What's a best practice for this?
(I don't use Try Blocks in every method, but when I do, I want to make
sure that things are being trapped)
Thanks,
Gabe
.
- Follow-Ups:
- Re: Code Standard 2.0 new objects outside of Try Block
- From: Kevin Spencer
- Re: Code Standard 2.0 new objects outside of Try Block
- References:
- Prev by Date: Re: VB only in help topics
- Next by Date: Re: Code Standard 2.0 new objects outside of Try Block
- Previous by thread: Code Standard 2.0 new objects outside of Try Block
- Next by thread: Re: Code Standard 2.0 new objects outside of Try Block
- Index(es):
Relevant Pages
|