Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Object reference not set to an instance of an object
Message
From
01/03/2010 18:51:08
Timothy Bryan
Sharpline Consultants
Conroe, Texas, United States
 
 
To
01/03/2010 18:25:32
General information
Forum:
ASP.NET
Category:
The Mere Mortals .NET Framework
Miscellaneous
Thread ID:
01450438
Message ID:
01451865
Views:
36
>Hi Frank,
>
>For us lurkers could you explain what sort of a comment in the app.config file can cause such a problem?
>
>Sam
>
>>>>hmm, I am running the latest version and I don't have that issue. I would look deeper to find what is causing it but I can't duplicate it.
>>>
>>>I'm sure it's something little.. but I'll go loco trying to figure it out.
>>
>>Hey Daniel,
>>
>>I got a solution from Josh at Oak Leaf. I had a comment in my app.config in the < databases > area which seems to break the code in the builder. Removing the comment fixed the problem!

Apparently any comment that falls between the Database key components. It must be something to do with the parser stuff that it had an issue with a comment in there. No big deal, just don't put comments between the two keys. Before or after apparently don't matter as I have them with no issues.
<add key="MSAMain\Connection" value=....
<add key="MSAMain\DataAccessClass" ...
Tim
Timothy Bryan
Previous
Reply
Map
View

Click here to load this message in the networking platform